tracing: Prevent out-of-bounds read in glob matching
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 60f1d5e3bac44b598f67d36062da96c095d2b700 · < 2dad64a97e1df47f5d9ccb17fa319aa348617226| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s tracing glob matcher can read past a string event field that is not NUL-terminated. This occurs when a glob filter matches such a field, including a dynamic character array in xfs_* tracepoints. The input does not specify whether an attacker needs local access, authentication, or user interaction.
Engineers running the Linux kernel should check whether their kernel includes the affected tracing code; affected versions are not specified.