ftrace: Take trace_array reference before accessing its ftrace_ops
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.52, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: ftrace: Take trace_array reference before accessing its ftrace_ops The trace instance files set_ftrace_filter and set_ftrace_notrace was updated to work with specific trace instances (trace_arrays). The issue is that when these files are opened, there is a small race window where it will use the ftrace_ops from the inode->private pointer to get a reference to the trace_array and then take its reference. The problem is that the ftrace_ops itself could be freed. If the rmdir on the instance happens at the same time the set_ftrace_filter file is opened, the rmdir could have also freed the ftrace_ops and referencing it will cause a use-after-free bug and crash the kernel. Instead, pass in the trace_array as the file private data (NULL for the top level instance), and then pass both the trace_array and the ftrace_ops to the ftrace_regex_open() function. If the trace_array is NULL, then it just uses the ftrace_ops without the need to take its reference (like normal). If the ftrace_ops is NULL, that is only the case for the top level instance and the global_ops can be used. This allows the trace_array to have its reference incremented before touching the ftrace_ops that could also be freed when the instance is.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 591dffdade9f07692a7dd3ed16830ec24e901ece · fixed in 29266da8ee1d9be656b1f22460c49538e1930658; From 591dffdade9f07692a7dd3ed16830ec24e901ece · fixed in 177cd8966325f0ffffa3c9381f9e0422019a3973; From 591dffdade9f07692a7dd3ed16830ec24e901ece · fixed in 83fd7eca5ab0d3ac3f23bff889175d847e21af06; From 591dffdade9f07692a7dd3ed16830ec24e901ece · fixed in cee8f286794df916553d8d445eac5c323ec5b0f8; From 591dffdade9f07692a7dd3ed16830ec24e901ece · fixed in 9100191e5acb2e5ea2313f436667bb5fce129f47
- Linux Linux
3.15
- KernelLinux
From 3.15.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.5