Vulnerability in Kernel: iommu/arm-smmu-v3

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1003227: iommu/arm-smmu-v3: check return value after calling platform_get_resource(). Affects Kernel versions < fb0f1c5eb8d60b3e018ba7c87da249b52674ebe6. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The iommu/arm-smmu-v3 module within the Kernel is responsible for handling input-output memory management unit (IOMMU) operations on ARM-based systems. It provides hardware support for virtualizing memory access and improves security by isolating device memory from the rest of the system. However, a vulnerability has been identified in this module that could potentially be exploited by attackers.

Vulnerability Detail

The vulnerability in iommu/arm-smmu-v3 arises due to a failure to check the return value after calling platform_get_resource(). This oversight could lead to various security issues, although the exact impact and attack vectors have not been proven yet. The vulnerability has been assigned the ID GSD-2022-1003227 and is fixed in Linux Kernel version v5.15.47 by commit fb0f1c5eb8d60b3e018ba7c87da249b52674ebe6. It is crucial to update to this version or a later one to mitigate the vulnerability.

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

No specific workaround has been mentioned for this vulnerability. It is essential to update the Kernel to the fixed version as soon as possible.

Conclusion

The vulnerability in iommu/arm-smmu-v3 module of the Kernel poses a potential risk to the security and stability of the system. It is crucial to update the Kernel to version v5.15.47 or a newer release to mitigate this vulnerability. Regularly applying security patches and updates is essential to ensure the ongoing protection of the system. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The exact impact of this vulnerability is not yet proven. However, it could potentially be exploited by attackers to compromise the security and stability of the system.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.

At the time of this report, no known exploit for this vulnerability has been disclosed. However, it is crucial to update the Kernel to the fixed version to mitigate any potential risks.

The primary solution is to update the Kernel to the fixed version. However, if updating is not immediately feasible, it is recommended to implement additional security measures, such as network segmentation, access controls, and intrusion detection systems, to minimize the risk of exploitation.

For more detailed information about this vulnerability, including technical details and the fix commit, you can refer to the source link provided in the database_specific section of the vulnerability details.

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