Linux: Out-of-bounds Read
CVE-2026-64299 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 265f3a690f6c7d69ef7d2ca50b04b4853a211df3, ee5b8888d3248618251fb69a2fad92afcb81557e, 56d4c9ab84714eebb285a2fee68aaedf81e3ef15 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.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 265f3a690f6c7d69ef7d2ca50b04b4853a211df3 or ee5b8888d3248618251fb69a2fad92afcb81557e or 56d4c9ab84714eebb285a2fee68aaedf81e3ef15 or 35ae19764eabfe9c29029d3b5713c86e6855acdf, whichever matches your release line, or a later version.
- Update Linux Kernel to 5.10.261 or 5.15.212 or 6.1.178 or 6.6.145, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, 265f3a690f6c7d69ef7d2ca50b04b4853a211df3; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, ee5b8888d3248618251fb69a2fad92afcb81557e; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, 56d4c9ab84714eebb285a2fee68aaedf81e3ef15; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, 35ae19764eabfe9c29029d3b5713c86e6855acdf; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, ebb55902856973906c8bb339a3a34824ed4a5086; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, 2dad64a97e1df47f5d9ccb17fa319aa348617226; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, e5d5f3bd053a5f14787526c9f0f55ef900d43ac6; 60f1d5e3bac44b598f67d36062da96c095d2b700 up to, but not including, 0a6070839b1ef276d5b05bedfb787743e140fb17; and 1 more ranges | 265f3a690f6c7d69ef7d2ca50b04b4853a211df3, ee5b8888d3248618251fb69a2fad92afcb81557e, 56d4c9ab84714eebb285a2fee68aaedf81e3ef15, 35ae19764eabfe9c29029d3b5713c86e6855acdf, ebb55902856973906c8bb339a3a34824ed4a5086, 2dad64a97e1df47f5d9ccb17fa319aa348617226 |
| Linux | Linux Kernel | 4.10 up to, but not including, 5.10.261; 5.11 up to, but not including, 5.15.212; 5.16 up to, but not including, 6.1.178; 6.2 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.2 | 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39 |
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 CNA.
Official description
In the Linux kernel, the following vulnerability has been resolved: tracing: Prevent out-of-bounds read in glob matching String event fields are not necessarily NUL-terminated, so the filter predicate functions (filter_pred_string(), filter_pred_strloc() and filter_pred_strrelloc()) pass the field length to the regex match callbacks, and the length-aware matchers honour it. regex_match_glob() was the exception: it ignored the length and called glob_match(), which scans the string until it hits a NUL byte. Some string fields are not NUL-terminated. One example is the dynamic char array of the xfs_* namespace tracepoints, which is copied without a trailing NUL. For such a field, glob matching reads past the end of the event field, causing a KASAN slab-out-of-bounds read in glob_match(), reached via regex_match_glob() and filter_match_preds() from the xfs_lookup tracepoint. Add a length-bounded glob_match_len() and use it from regex_match_glob() so glob matching always stops at the field boundary. The matching loop is factored into a shared helper so glob_match() keeps its behaviour.
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.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/0a6070839b1ef276d5b05bedfb787743e140fb17
- git.kernel.org/stable/c/265f3a690f6c7d69ef7d2ca50b04b4853a211df3
- git.kernel.org/stable/c/2dad64a97e1df47f5d9ccb17fa319aa348617226
- git.kernel.org/stable/c/35ae19764eabfe9c29029d3b5713c86e6855acdf
- git.kernel.org/stable/c/56d4c9ab84714eebb285a2fee68aaedf81e3ef15
- git.kernel.org/stable/c/e5d5f3bd053a5f14787526c9f0f55ef900d43ac6
- git.kernel.org/stable/c/ebb55902856973906c8bb339a3a34824ed4a5086
- git.kernel.org/stable/c/ee5b8888d3248618251fb69a2fad92afcb81557e
Recent Out-of-bounds Read vulnerabilities
- 8.4 High severity
- 7.1 High severity
- 7.1 High severity
- 7.7 High severity
- 9.1 Critical severity
- 8.2 High severity
Spotted an error? Tell us.