Use-after-free vulnerability in iommu/arm-smmu-v3-sva

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002691: iommu/arm-smmu-v3-sva: Fix mm use-after-free. Affects Kernel versions >= 32784a9562fb0518b12e9797ee2aec52214adf6f, < 9aa215450888cf29af0c479e14a712dc6b0c506c. 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 Your last release was probably never penetration tested 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/arm-smmu-v3-sva is a component of the Linux Kernel that provides support for the ARM System MMU Version 3 (SMMUv3) Secure Virtual Addressing (SVA) feature. This feature allows for secure and efficient virtual address translation for devices connected to the ARM SMMU. The vulnerability in this component can lead to a use-after-free condition, potentially allowing an attacker to execute arbitrary code or cause a denial-of-service.

Vulnerability Detail

The use-after-free vulnerability in iommu/arm-smmu-v3-sva arises from a programming error that results in incorrect handling of memory management (mm) objects. This can lead to a situation where a memory region is accessed after it has been freed, potentially causing memory corruption or other unexpected behavior. An attacker may be able to exploit this vulnerability to gain unauthorized access, escalate privileges, or disrupt the normal operation of the system. The vulnerability was introduced in Linux Kernel version v5.11 and has been fixed in version v5.18.3.

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 known workaround for this vulnerability. It is recommended to apply the fix mentioned above as soon as possible.

Conclusion

The use-after-free vulnerability in iommu/arm-smmu-v3-sva can have serious security implications, potentially allowing an attacker to execute arbitrary code or cause a denial-of-service. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use-after-free vulnerability in iommu/arm-smmu-v3-sva can potentially allow an attacker to execute arbitrary code or cause a denial-of-service. This can lead to unauthorized access, privilege escalation, or disruption of system operation.

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

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

Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is recommended to update the Linux Kernel to the fixed version to prevent potential remote exploitation.

To exploit this vulnerability, an attacker would need to have the ability to execute arbitrary code on the target system. This could be achieved through various means, such as gaining unauthorized access or exploiting other vulnerabilities.

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