coresight: ETR: Fix ETR buffer use-after-free issue
- 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, 6.6.160, 6.12.114, 6.17.13, 6.18.2
- 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: coresight: ETR: Fix ETR buffer use-after-free issue When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed and enabled again, currently sysfs_buf will point to the newly allocated memory(buf_new) and free the old memory(buf_old). But the etr_buf that is being used by the ETR remains pointed to buf_old, not updated to buf_new. In this case, it will result in a memory use-after-free issue. Fix this by checking ETR's mode before updating and releasing buf_old, if the mode is CS_MODE_SYSFS, then skip updating and releasing it.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bd2767ec3df2775bc336f441f9068a989ccb919d · fixed in 5d5d130835b417c7bfd6c942f0149e34397d4463; From bd2767ec3df2775bc336f441f9068a989ccb919d · fixed in 4e83434247ff8005a0b9a1ee997864abf8f259ec; From bd2767ec3df2775bc336f441f9068a989ccb919d · fixed in 70acbc9c77686b7a521af6d7a543dcd9c324cf07; From bd2767ec3df2775bc336f441f9068a989ccb919d · fixed in cda077a19f5c8d6ec61e5b97deca203d95e3a422; From bd2767ec3df2775bc336f441f9068a989ccb919d · fixed in 35501ac3c7d40a7bb9568c2f89d6b56beaf9bed3; From 6.5.8 · fixed in 6.6
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.17.13; From 6.18.0 · fixed in 6.18.2