CyberSecBulletin
CVE-2026-64407NVD status: Analyzed

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2026-64407 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 21e60eb4d95854196e7c0e77383f35e7ac95df61, 441088792ffec3ca01f4efe2934060570eb11eb8, 2a68a773089204af1c8581dc79668b775418c5ee 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 21e60eb4d95854196e7c0e77383f35e7ac95df61 or 441088792ffec3ca01f4efe2934060570eb11eb8 or 2a68a773089204af1c8581dc79668b775418c5ee or 49bcb39e3a041ce26021f77971eaccb49a275118, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.145 or 6.12.96 or 6.18.39 or 7.1.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux689ca16e523278470c38832a3010645a78c544d8 up to, but not including, 21e60eb4d95854196e7c0e77383f35e7ac95df61; 689ca16e523278470c38832a3010645a78c544d8 up to, but not including, 441088792ffec3ca01f4efe2934060570eb11eb8; 689ca16e523278470c38832a3010645a78c544d8 up to, but not including, 2a68a773089204af1c8581dc79668b775418c5ee; 689ca16e523278470c38832a3010645a78c544d8 up to, but not including, 49bcb39e3a041ce26021f77971eaccb49a275118; 689ca16e523278470c38832a3010645a78c544d8 up to, but not including, badff6c3bed8923a1257a853f137d447976eec30; 6.421e60eb4d95854196e7c0e77383f35e7ac95df61, 441088792ffec3ca01f4efe2934060570eb11eb8, 2a68a773089204af1c8581dc79668b775418c5ee, 49bcb39e3a041ce26021f77971eaccb49a275118, badff6c3bed8923a1257a853f137d447976eec30
LinuxLinux Kernel6.4 up to, but not including, 6.6.145; 6.7 up to, but not including, 6.12.96; 6.13 up to, but not including, 6.18.39; 6.19 up to, but not including, 7.1.4; 7.26.6.145, 6.12.96, 6.18.39, 7.1.4

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: Bluetooth: btnxpuart: Fix out-of-bounds firmware read in nxp_recv_fw_req_v3() During the v3 firmware download the controller sends a v3_data_req with a 32 bit offset and a 16 bit len. nxp_recv_fw_req_v3() checks only the lower bound of the offset and then sends firmware from that offset. nxpdev->fw_dnld_v3_offset = offset - nxpdev->fw_v3_offset_correction; serdev_device_write_buf(nxpdev->serdev, nxpdev->fw->data + nxpdev->fw_dnld_v3_offset, len); Nothing checks that fw_dnld_v3_offset + len stays within nxpdev->fw->size, so a controller that asks for an offset or length past the firmware image makes the driver read past the end of nxpdev->fw->data and send that memory back over UART. nxp_recv_fw_req_v1() already bounds the same write. Add the equivalent check to the v3 path, reject the request when it falls outside the firmware image, and zero len on the error path so the fw_v3_prev_sent bookkeeping at free_skb stays consistent.

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. Record last changed materially (score, affected products, status or references).

References

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.