CVE-2026-64299
Last modified
CVE-2026-64299 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.10, < 5.10.261 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.212 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.178 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64299?
How severe is CVE-2026-64299?
How do I fix CVE-2026-64299?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64293In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64294In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64295In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64296In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64297In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64298In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64300In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64301In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64302In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64303In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64304In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64305In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64299?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
