CVE Catalog

CVE-2026-64299

HighCVSS 7.1
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.16%

6th percentile - higher than 6% of all known CVEs

Summary

In the Linux kernel's tracing subsystem, an out-of-bounds read exists in glob matching. The regex_match_glob() function ignores field length and scans until a NUL byte, causing reads beyond buffer boundaries for non-NUL-terminated fields (e.g., dynamic char arrays in xfs tracepoints).

Risk Assessment

Out-of-bounds read can leak sensitive kernel memory data or cause a kernel panic, especially when using filters on string fields.

Recommendation

Update the Linux kernel to a version that includes the fix introducing a length-bounded glob_match_len() function.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS