In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Remove latent out-of-bounds access in IOMMU debugfs In… (CVE-2026-64186)
A vulnerability in the Linux kernel's AMD IOMMU debugfs implementation allowed latent out-of-bounds memory access due to improper handling of user-supplied input values. The issue arose because certain offset variables were declared as signed integers but populated from unsigned 32-bit user input, which could lead to negative values and potential out-of-bounds access. The vulnerability has been resolved by changing the input parsing to signed integers and adding explicit checks to prevent negative values.
AI Analysis
Technical Summary
The Linux kernel AMD IOMMU debugfs code used kstrtou32_from_user() to parse user input into int variables dbg_mmio_offset and dbg_cap_offset. This mismatch could cause large unsigned inputs to be interpreted as negative signed integers, potentially leading to out-of-bounds memory access in iommu_mmio_write() and iommu_capability_write(). Prior protections limited input size and checked bounds, but this latent issue was fixed by replacing kstrtou32_from_user() with kstrtos32_from_user() and adding explicit negative value checks to prevent out-of-bounds access.
Potential Impact
If exploited, this vulnerability could allow a user with access to the AMD IOMMU debugfs interface to cause out-of-bounds memory access, which might lead to system instability or information disclosure. However, the implementation was already protected by input size limits and bounds checks, reducing the risk. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability has been resolved in the Linux kernel by updating the input parsing and adding explicit checks to prevent negative offsets. Users should apply the official kernel patches that include this fix. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or distribution security updates for the exact fixed versions and apply them accordingly.
In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Remove latent out-of-bounds access in IOMMU debugfs In… (CVE-2026-64186)
Description
A vulnerability in the Linux kernel's AMD IOMMU debugfs implementation allowed latent out-of-bounds memory access due to improper handling of user-supplied input values. The issue arose because certain offset variables were declared as signed integers but populated from unsigned 32-bit user input, which could lead to negative values and potential out-of-bounds access. The vulnerability has been resolved by changing the input parsing to signed integers and adding explicit checks to prevent negative values.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel AMD IOMMU debugfs code used kstrtou32_from_user() to parse user input into int variables dbg_mmio_offset and dbg_cap_offset. This mismatch could cause large unsigned inputs to be interpreted as negative signed integers, potentially leading to out-of-bounds memory access in iommu_mmio_write() and iommu_capability_write(). Prior protections limited input size and checked bounds, but this latent issue was fixed by replacing kstrtou32_from_user() with kstrtos32_from_user() and adding explicit negative value checks to prevent out-of-bounds access.
Potential Impact
If exploited, this vulnerability could allow a user with access to the AMD IOMMU debugfs interface to cause out-of-bounds memory access, which might lead to system instability or information disclosure. However, the implementation was already protected by input size limits and bounds checks, reducing the risk. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability has been resolved in the Linux kernel by updating the input parsing and adding explicit checks to prevent negative offsets. Users should apply the official kernel patches that include this fix. Since this is a kernel vulnerability, updating to a patched kernel version is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should consult the official Linux kernel advisories or distribution security updates for the exact fixed versions and apply them accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-398p-2vfw-ch77
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64186"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912a891
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:42:51 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.