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

Kernel Updated 02 Oct 2025

Summary

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

GSD-2021-1000570: iommu/vt-d: Fix sysfs leak in alloc_iommu(). Affects Kernel versions >= 39ab9555c24110671f8dc671311a26e5c985b592, < ca466561eef36d1ec657673e3944eb6340bddb5b. 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 iommu/vt-d package is a component of the Linux Kernel that provides support for Input-Output Memory Management Units (IOMMU) and Virtualization Technology for Directed I/O (VT-d). IOMMU is responsible for mapping device memory addresses to physical memory addresses, ensuring secure and efficient data transfers between devices and memory. VT-d enhances virtualization capabilities by allowing direct device access to virtual machines. This vulnerability affects the alloc_iommu() function within the iommu/vt-d package.

Vulnerability Detail

The vulnerability in alloc_iommu() function within the iommu/vt-d package allows for a sysfs leak. This leak can potentially expose sensitive system information to unauthorized users. An attacker could exploit this vulnerability to gather information about the system's IOMMU 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.12.9.

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 Linux Kernel to the latest version will address the issue.

Conclusion

The vulnerability in the iommu/vt-d package's alloc_iommu() function poses a risk of sysfs leak, potentially exposing sensitive system information. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version v5.12.9 or later. Regularly updating the kernel is essential to ensure the application of the latest security patches. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The iommu/vt-d package is a component of the Linux Kernel that provides support for Input-Output Memory Management Units (IOMMU) and Virtualization Technology for Directed I/O (VT-d). It enables secure and efficient data transfers between devices and memory, as well as enhances virtualization capabilities.

This vulnerability allows for a sysfs leak in the alloc_iommu() function within the iommu/vt-d package. It can potentially expose sensitive system information to unauthorized users, which could aid in further attacks.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.12.9 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided.

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

This vulnerability was introduced in version v4.11 of the Linux Kernel and has been fixed in version v5.12.9.

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