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-1003318: iommu/arm-smmu-v3-sva: Fix mm use-after-free. Affects Kernel versions >= 32784a9562fb0518b12e9797ee2aec52214adf6f, < fc90f13ea0dcd960e5002d204fa55cec4e0db2fa. 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/arm-smmu-v3-sva is a component of the Linux Kernel that provides support for the System MMU (SMMU) on ARM-based systems. The SMMU is responsible for managing memory access and translation for devices connected to the system. It ensures that each device has access only to the memory regions it is authorized to use. The arm-smmu-v3-sva module specifically handles Shared Virtual Addressing (SVA) for the SMMU. SVA allows devices to access memory using virtual addresses instead of physical addresses, improving performance and security. However, a use-after-free vulnerability has been discovered in this module, which could potentially be exploited by an attacker to gain unauthorized access to sensitive information or execute arbitrary code.

Vulnerability Detail

The use-after-free vulnerability in iommu/arm-smmu-v3-sva occurs when a memory region is freed but still referenced by a pointer. This can lead to a situation where an attacker can manipulate the freed memory region, potentially causing a crash or executing arbitrary code. The vulnerability was introduced in Linux Kernel version v5.11 by commit 32784a9562fb0518b12e9797ee2aec52214adf6f and is fixed in version v5.15.46 by commit fc90f13ea0dcd960e5002d204fa55cec4e0db2fa. It is important to update to the fixed version to mitigate the risk of exploitation.

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 →

Conclusion

The use-after-free vulnerability in iommu/arm-smmu-v3-sva can be mitigated by updating the Linux Kernel to version v5.15.46 or later. It is important to apply this update to protect against potential exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

iommu/arm-smmu-v3-sva is a component of the Linux Kernel that provides support for the System MMU (SMMU) on ARM-based systems. It handles Shared Virtual Addressing (SVA) for the SMMU, allowing devices to access memory using virtual addresses.

A use-after-free vulnerability occurs when a program continues to use a memory region after it has been freed. This can lead to memory corruption and potentially allow an attacker to execute arbitrary code or gain unauthorized access to sensitive information.

An attacker can exploit this vulnerability by manipulating the freed memory region, potentially causing a crash or executing arbitrary code. This can be done by carefully crafting input or triggering specific conditions in the affected software.

No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel to mitigate the risk of exploitation.

More information about the fix for this vulnerability can be found in the commit with the ID fc90f13ea0dcd960e5002d204fa55cec4e0db2fa in the official Linux Kernel repository.

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