Answer in brief
CVE-2026-64299 records a Unknown severity vulnerability in tracing: Prevent out-of-bounds read in glob matching. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-64299 records a Unknown severity vulnerability in tracing: Prevent out-of-bounds read in glob matching. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=60f1d5e3bac44b598f67d36062da96c095d2b700 <265f3a690f6c7d69ef7d2ca50b04b4853a211df3 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <ee5b8888d3248618251fb69a2fad92afcb81557e || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <56d4c9ab84714eebb285a2fee68aaedf81e3ef15 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <35ae19764eabfe9c29029d3b5713c86e6855acdf || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <ebb55902856973906c8bb339a3a34824ed4a5086 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <2dad64a97e1df47f5d9ccb17fa319aa348617226 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <e5d5f3bd053a5f14787526c9f0f55ef900d43ac6 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <0a6070839b1ef276d5b05bedfb787743e140fb17 | 265f3a690f6c7d69ef7d2ca50b04b4853a211df3, ee5b8888d3248618251fb69a2fad92afcb81557e, 56d4c9ab84714eebb285a2fee68aaedf81e3ef15, 35ae19764eabfe9c29029d3b5713c86e6855acdf, ebb55902856973906c8bb339a3a34824ed4a5086, 2dad64a97e1df47f5d9ccb17fa319aa348617226, e5d5f3bd053a5f14787526c9f0f55ef900d43ac6, 0a6070839b1ef276d5b05bedfb787743e140fb17 |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=60f1d5e3bac44b598f67d36062da96c095d2b700 <265f3a690f6c7d69ef7d2ca50b04b4853a211df3 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <ee5b8888d3248618251fb69a2fad92afcb81557e || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <56d4c9ab84714eebb285a2fee68aaedf81e3ef15 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <35ae19764eabfe9c29029d3b5713c86e6855acdf || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <ebb55902856973906c8bb339a3a34824ed4a5086 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <2dad64a97e1df47f5d9ccb17fa319aa348617226 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <e5d5f3bd053a5f14787526c9f0f55ef900d43ac6 || >=60f1d5e3bac44b598f67d36062da96c095d2b700 <0a6070839b1ef276d5b05bedfb787743e140fb17 | 265f3a690f6c7d69ef7d2ca50b04b4853a211df3, ee5b8888d3248618251fb69a2fad92afcb81557e, 56d4c9ab84714eebb285a2fee68aaedf81e3ef15, 35ae19764eabfe9c29029d3b5713c86e6855acdf, ebb55902856973906c8bb339a3a34824ed4a5086, 2dad64a97e1df47f5d9ccb17fa319aa348617226, e5d5f3bd053a5f14787526c9f0f55ef900d43ac6, 0a6070839b1ef276d5b05bedfb787743e140fb17 |
| Linux/Linuxgeneric | 4.10 | Not reported |
Published upstream
Jul 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.