Vulnerability in Kernel package: iommu/vt-d: Fix sysfs leak in alloc_iommu()

Kernel Updated 02 Oct 2025

Summary

04/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000683: iommu/vt-d: Fix sysfs leak in alloc_iommu(). Affects Kernel versions >= 39ab9555c24110671f8dc671311a26e5c985b592, < 22da9f4978381a99f1abaeaf6c9b83be6ab5ddd8. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Kernel package is a critical component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It includes various subsystems, such as memory management, process scheduling, and device drivers. The iommu/vt-d subsystem within the Kernel is responsible for handling input-output memory management unit (IOMMU) operations and virtualization technology for directed I/O (VT-d). These features are crucial for secure and efficient data transfers between devices and memory. However, a vulnerability has been identified in the alloc_iommu() function of the iommu/vt-d subsystem, which can lead to a sysfs leak.

Vulnerability Detail

The vulnerability in the alloc_iommu() function of the iommu/vt-d subsystem allows an attacker to leak sensitive information through the sysfs interface. By exploiting this vulnerability, an attacker may gain unauthorized access to system data or manipulate the IOMMU and VT-d functionalities, potentially leading to privilege escalation, information disclosure, or denial of service. The vulnerability was introduced in version v4.11 of the Linux Kernel and has been fixed in version v4.14.235 by commit 22da9f4978381a99f1abaeaf6c9b83be6ab5ddd8.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, applying the recommended fix by updating the Kernel to the latest version should address the issue.

Conclusion

In conclusion, the Kernel package's iommu/vt-d subsystem is vulnerable to a sysfs leak in the alloc_iommu() function. This vulnerability can be mitigated by updating the Kernel to version v4.14.235 or later. It is essential to regularly update the system with the latest security patches to ensure the overall security and stability of the Linux operating system. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially allow an attacker to leak sensitive information, gain unauthorized access, or manipulate the IOMMU and VT-d functionalities, leading to various security risks such as privilege escalation, information disclosure, or denial of service.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert analyzes your manifest file, such as package-lock.json, to identify and alert in real-time for open-source vulnerabilities in the software.

At the time of this report, there is no known public exploit for this vulnerability. However, it is crucial to apply the recommended fix promptly to mitigate any potential risks.

To exploit this vulnerability, an attacker would need to have local access to a system with the affected Kernel version and the ability to execute malicious code.

The vulnerability was discovered by the Linux Kernel security team during routine code review and analysis.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback