Linux
tracing: Check return value of __register_event() in trace_module_add_events()
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < 3bf965a2827c44f03294107703e7ba53fbd0a69a
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < 9d6d79744f01eacaf3d5522f4fcd59939581abfd
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < 54b7a358f6399c1242d2fb7f4f96085af34baa5e
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < 22f954f7a8afe975e85517aff41b35defe05144b
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < 000765dcdc3edf128990762790543adc4b868f6c
- >= ae63b31e4d0e2ec09c569306ea46f664508ef717, < ac8719969e6c3c54e939834df812bc41f25453cf
Fixed in 3bf965a2827c44f03294107703e7ba53fbd0a69a, 9d6d79744f01eacaf3d5522f4fcd59939581abfd, 54b7a358f6399c1242d2fb7f4f96085af34baa5e, d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5, 22f954f7a8afe975e85517aff41b35defe05144b, cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca, 000765dcdc3edf128990762790543adc4b868f6c, ac8719969e6c3c54e939834df812bc41f25453cf
- 3.10
Fixed in 0, 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8, 7.2
Mitigation
Upgrade Linux to 3bf965a2827c44f03294107703e7ba53fbd0a69a or 9d6d79744f01eacaf3d5522f4fcd59939581abfd or 54b7a358f6399c1242d2fb7f4f96085af34baa5e or d61ee2a27dfd5eb43ddc18af40168f5b9eb1cea5 or 22f954f7a8afe975e85517aff41b35defe05144b or cbb5ed3be9cae70e1c12b1991009b4e12bf4a4ca or 000765dcdc3edf128990762790543adc4b868f6c or ac8719969e6c3c54e939834df812bc41f25453cf or later.
Upgrade Linux to 0 or 5.10.265 or 5.15.216 or 6.1.183 or 6.6.151 or 6.12.103 or 6.18.44 or 7.1.8 or 7.2 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.