tracing: Check return value of __register_event() in trace_module_add_events()
- 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 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: tracing: Check return value of __register_event() in trace_module_add_events() trace_module_add_events() ignores the return value of __register_event() and unconditionally calls __add_event_to_tracers() for each event. If __register_event() fails (for example, if event_init() fails), the trace_event_call is not added to ftrace_events list, but __add_event_to_tracers() still creates a trace_event_file pointing to it. If module loading subsequently fails and module memory is freed, tracing state retains a stale trace_event_call pointer in trace_event_file, leading to a use-after-free when tracefs or tracing subsystem operations are later executed. Fix this by checking the return value of __register_event() and only calling __add_event_to_tracers() if event registration succeeded.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in 3bf965a2827c44f03294107703e7ba53fbd0a69a; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in 9d6d79744f01eacaf3d5522f4fcd59939581abfd; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in 54b7a358f6399c1242d2fb7f4f96085af34baa5e; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in 22f954f7a8afe975e85517aff41b35defe05144b; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in 000765dcdc3edf128990762790543adc4b868f6c; From ae63b31e4d0e2ec09c569306ea46f664508ef717 · fixed in ac8719969e6c3c54e939834df812bc41f25453cf
- Linux Linux
3.10
- KernelLinux
From 3.10.0 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.151; From 6.7.0 · fixed in 6.12.103; From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8
References 8
git.kernel.org
- stable/c/3bf965a2827c44f03294107703e7ba53fbd0a69a
- stable/c/9d6d79744f01eacaf3d5522f4fcd59939581abfd
- stable/c/54b7a358f6399c1242d2fb7f4f96085af34baa5e
- stable/c/d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5
- stable/c/22f954f7a8afe975e85517aff41b35defe05144b
- stable/c/cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca
- stable/c/000765dcdc3edf128990762790543adc4b868f6c
- stable/c/ac8719969e6c3c54e939834df812bc41f25453cf