tracing: Have show_event_filters/triggers files take trace array ref
- 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 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: tracing: Have show_event_filters/triggers files take trace array ref The newly added files show_event_filters and show_event_triggers that show all filters or triggers that are set within the trace array do not take a reference for the trace array it is showing. Without taking a reference, the trace_array may be freed via "rmdir" while a task is reading one of theses files. Those files iterate all the events within an instance (trace_array) and nothing prevents that instance from being freed while its data is being read. This causes a use-after-free crash. Have the open of both those files take the trace_array reference via the trace_array_get() that prevents the trace_array from being freed while the files are opened.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 729757b96a662d87e334fe8b837707800d8fd551 · fixed in 2ee3f7d43f79efaca0cd84a6798653d9d75ce60b; From 729757b96a662d87e334fe8b837707800d8fd551 · fixed in f4a771cc684c7354b6200147f7252c58d17408ff
- Linux Linux
7.0
- KernelLinux
From 7.0.0 · fixed in 7.2.5