tracing: Fix memory corruption from a "STACKTRACE" histogram key
- 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.53, 7.2.7
- 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: Fix memory corruption from a "STACKTRACE" histogram key "cpu", "CPU", "stacktrace" and "STACKTRACE" are generic fields, defined with an offset and a size of zero so that the filter code can match them by name. parse_field() maps them onto their common_* equivalents for backward compatibility, but unlike the common_* names it hands the placeholder back to the caller instead of NULL. create_hist_field() takes a non-NULL field as a promise that the record carries a stacktrace and picks HIST_FIELD_FN_STACK, so the __data_loc word is read from offset 0, that is from common_type, and its low 16 bits are followed as an offset into the record. What is found there becomes the length of an unbounded memcpy. Pick an event whose id is small enough that the offset stays inside its own record and the length is a kernel text address: cd /sys/kernel/tracing echo 'hist:keys=STACKTRACE' > events/ftrace/print/trigger echo hello > trace_marker Oops: general protection fault, probably for non-canonical address RIP: 0010:rb_next+0x23/0x60 </IRQ> RIP: 0010:memcpy+0xc/0x30 event_hist_trigger+0x2e7/0x12c0 Kernel panic - not syncing: Fatal exception in interrupt Leave the field NULL, which is what the comment above the branch says the code does and what common_stacktrace already does. FILTER_CPU and FILTER_COMM are left alone, their create_hist_field() branches never look at the field.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 4b512860bdbdddcf41467ebd394f27cb8dfb528c · fixed in c94985e4fd77eb8634f44fb42e551563c68c55b3; From 4b512860bdbdddcf41467ebd394f27cb8dfb528c · fixed in b6cc6ec5f032ea6fd5cce94fb83baab4d1c02e33; From 4b512860bdbdddcf41467ebd394f27cb8dfb528c · fixed in 9e026a91fe79966e2baabd4345c6e3a26975c729; From 4b512860bdbdddcf41467ebd394f27cb8dfb528c · fixed in c27f8b68c05808bb4f2bcde0e6d1c954a4b65f8a; From 4b512860bdbdddcf41467ebd394f27cb8dfb528c · fixed in 7f711e62355bb3123a2ca2f97a2facbfebc678c6
- Linux Linux
6.4
- KernelLinux
From 6.4.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7