CyberSecBulletin
CVE-2026-64186NVD status: Analyzed

Linux: Out-of-bounds Read

CVE-2026-64186 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 488d2c76bd9f78433a70690d1054bfae3d39a407, 62f9dfbf1aceae88b03c5ca08f7d36e943939dec, 8dfd3d8d74435344ee8dc9237596959c8b2a6cbe as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 488d2c76bd9f78433a70690d1054bfae3d39a407 or 62f9dfbf1aceae88b03c5ca08f7d36e943939dec or 8dfd3d8d74435344ee8dc9237596959c8b2a6cbe, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.18.34 or 7.0.11, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux7a4ee419e8c144b747a8915856e91a034d7c8f34 up to, but not including, 488d2c76bd9f78433a70690d1054bfae3d39a407; 7a4ee419e8c144b747a8915856e91a034d7c8f34 up to, but not including, 62f9dfbf1aceae88b03c5ca08f7d36e943939dec; 7a4ee419e8c144b747a8915856e91a034d7c8f34 up to, but not including, 8dfd3d8d74435344ee8dc9237596959c8b2a6cbe; 6.17488d2c76bd9f78433a70690d1054bfae3d39a407, 62f9dfbf1aceae88b03c5ca08f7d36e943939dec, 8dfd3d8d74435344ee8dc9237596959c8b2a6cbe
LinuxLinux Kernel6.17 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 7.16.18.34, 7.0.11

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Remove latent out-of-bounds access in IOMMU debugfs In iommu_mmio_write() and iommu_capability_write(), the variables dbg_mmio_offset and dbg_cap_offset are declared as int. However, they are populated using kstrtou32_from_user(). If a user provides a sufficiently large value, it can become a negative integer. Prior to this patch, the AMD IOMMU debugfs implementation was already protected by different mechanisms. 1. #define OFS_IN_SZ 8 ensures the user string <= 8 bytes, so e.g. 0xffffffff isn't a valid input. if (cnt > OFS_IN_SZ) return -EINVAL; 2. Implicit type promotion in iommu_mmio_write(), dbg_mmio_offset is int and iommu->mmio_phys_end is u64 if (dbg_mmio_offset > iommu->mmio_phys_end - sizeof(u64)) return -EINVAL; 3. The show handlers would currently catch the negative number and refuse to perform the read. Replace kstrtou32_from_user() with kstrtos32_from_user() to parse the input, and check for negative values to explicitly prevent out-of-bounds memory accesses directly in iommu_mmio_write() and iommu_capability_write().

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

The product reads data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.