CyberSecBulletin
CVE-2026-64097NVD status: Modified

Linux: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-64097 is a high-severity out-of-bounds write vulnerability in Linux, with a CVSS 3.1 base score of 7.8 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 9900f6954be779011e7c2cd42addd87baf028bc5, fb30a3890d62fd50a95aef684faf64a307592e42, 67461e0c15335894cc5d3b84cda823bf8cbdc886 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.13% 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 9900f6954be779011e7c2cd42addd87baf028bc5 or fb30a3890d62fd50a95aef684faf64a307592e42 or 67461e0c15335894cc5d3b84cda823bf8cbdc886 or 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.1.175 or 6.6.142 or 6.12.92 or 6.18.34, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, 9900f6954be779011e7c2cd42addd87baf028bc5; ae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, fb30a3890d62fd50a95aef684faf64a307592e42; ae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, 67461e0c15335894cc5d3b84cda823bf8cbdc886; ae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a; ae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, f2a4827e980ba07de4391fa84d9c39a12726bdd7; ae79c310b1a6f97429a5784b65f125d9cc9c95b1 up to, but not including, 86d2b20644b11d21fe52c596e6e922b4590a3e3f; 4.159900f6954be779011e7c2cd42addd87baf028bc5, fb30a3890d62fd50a95aef684faf64a307592e42, 67461e0c15335894cc5d3b84cda823bf8cbdc886, 7ca695b3122297b06a3ed605bbe1cd32c85d9f5a, f2a4827e980ba07de4391fa84d9c39a12726bdd7, 86d2b20644b11d21fe52c596e6e922b4590a3e3f
LinuxLinux Kernel4.15 up to, but not including, 6.1.175; 6.2 up to, but not including, 6.6.142; 6.7 up to, but not including, 6.12.92; 6.13 up to, but not including, 6.18.34; 6.19 up to, but not including, 7.0.11; 7.16.1.175, 6.6.142, 6.12.92, 6.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
HighData or code can be modified at will.
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:H/A:H. Scored by CNA.

Official description

In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Validate GPIO pin LUT table size before iterating [Why&How] The GPIO pin table parsers in get_gpio_i2c_info() and bios_parser_get_gpio_pin_info() derive an element count from the VBIOS table_header.structuresize field, then iterate over gpio_pin[] entries. However, GET_IMAGE() only validates that the table header itself fits within the BIOS image. If the VBIOS reports a structuresize larger than the actual mapped data, the loop reads past the end of the BIOS image, causing an out-of-bounds read. Fix this by calling bios_get_image() to validate that the full claimed structuresize is accessible within the BIOS image before entering the loop in both functions. (cherry picked from commit ba5e95b43b773ae1bf1f66ee6b31eb774e65afe3)

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

The underlying weakness: Out-of-bounds Write

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

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

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

References

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.