Vulnerability in Kernel: 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-1000613: iommu/vt-d: Fix sysfs leak in alloc_iommu(). Affects Kernel versions >= 39ab9555c24110671f8dc671311a26e5c985b592, < f01134321d04f47c718bb41b799bcdeda27873d2. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a fundamental component of the Linux operating system that provides core functionalities and acts as an interface between the hardware and software layers. It manages system resources, facilitates communication between different software components, and ensures the overall stability and security of the system. 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) functionality. This subsystem enables secure and efficient device access and memory isolation for virtual machines. However, a vulnerability has been identified in the alloc_iommu() function within the iommu/vt-d subsystem.

Vulnerability Detail

The vulnerability in the alloc_iommu() function of the iommu/vt-d subsystem can lead to a sysfs leak. This leak can potentially expose sensitive system information to unauthorized entities. An attacker may exploit this vulnerability to gather information about the system's configuration, potentially aiding in further attacks. The vulnerability was introduced in version v4.11 of the Linux Kernel and has been fixed in version v5.10.42. The fix involves the commit f01134321d04f47c718bb41b799bcdeda27873d2.

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

As this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is advised to update to the fixed version as soon as possible.

Conclusion

In conclusion, the vulnerability in the alloc_iommu() function of the iommu/vt-d subsystem in the Kernel can lead to a sysfs leak, potentially exposing sensitive system information. It is crucial to update the Linux Kernel to version v5.10.42 or later to fix this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

This vulnerability can potentially expose sensitive system information to unauthorized entities, which may aid in further attacks.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any vulnerabilities, including this one, are found.

At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

No, this vulnerability requires local access to the system in order to exploit it.

There may be other vulnerabilities in the Kernel that are unrelated to this specific issue. It is recommended to regularly update the Kernel and stay informed about security advisories to mitigate any potential risks.

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