CVE-2026-64299: In the Linux kernel, the following vulnerability has been resolved: tracing: Prevent out-of-bounds read in glob matching String event fields are not...

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

CVSS 3.1

7.1/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

EPSS Probability

0.16%

5.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

Vendor	Product	Versions
Linux	Linux	>= 60f1d5e3bac44b598f67d36062da96c095d2b700, < 265f3a690f6c7d69ef7d2ca50b04b4853a211df3; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < ee5b8888d3248618251fb69a2fad92afcb81557e; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < 56d4c9ab84714eebb285a2fee68aaedf81e3ef15; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < 35ae19764eabfe9c29029d3b5713c86e6855acdf; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < ebb55902856973906c8bb339a3a34824ed4a5086; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < 2dad64a97e1df47f5d9ccb17fa319aa348617226; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < e5d5f3bd053a5f14787526c9f0f55ef900d43ac6; >= 60f1d5e3bac44b598f67d36062da96c095d2b700, < 0a6070839b1ef276d5b05bedfb787743e140fb17
Linux	Linux	4.10

References

Timeline

Published: Jul 25, 2026
Last Modified: Aug 11, 2026
Status: Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64299?

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.

How severe is CVE-2026-64299?

CVE-2026-64299 has a CVSS score of 7.1/10 (HIGH severity). The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.

How do I fix CVE-2026-64299?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →