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-1000665: iommu/vt-d: Fix sysfs leak in alloc_iommu(). Affects Kernel versions >= 39ab9555c24110671f8dc671311a26e5c985b592, < 2ec5e9bb6b0560c90d315559c28a99723c80b996. 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 functionality and acts as an interface between hardware and software. It includes various subsystems and modules that enable the proper functioning of the system. One of these subsystems is the iommu/vt-d, which is responsible for input-output memory management unit (IOMMU) support for Intel Virtualization Technology for Directed I/O (VT-d). This feature allows for efficient and secure device assignment in virtualized environments. However, a vulnerability has been discovered 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 can gain unauthorized access to system data, potentially leading to further security breaches or information disclosure. The vulnerability was introduced in version v4.11 of the Linux Kernel and has been fixed in version v4.19.193. It is important to note that the impact and attack plausibility of this vulnerability have not been proven yet.

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.

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 potentially lead to unauthorized access and information leakage. It is crucial to update the Linux Kernel package to version v4.19.193 or later to mitigate this vulnerability. If you have any further questions or need assistance, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is the potential leakage of sensitive information through the sysfs interface, which can be exploited by attackers to gain unauthorized access to system data.

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 and the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

As of now, there are no known exploits for this vulnerability. However, it is important to apply the recommended fix as soon as possible to mitigate any potential risks.

The exact attack vector and remote exploitability of this vulnerability have not been proven yet. However, it is always recommended to apply security patches and updates to prevent any potential remote attacks.

For further support on vulnerability remediation and assistance with the Linux Kernel package, you can reach out to info@devnack.com.

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