tracing: Fix retry exhaustion in simple ring buffer reader swap
- 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.4
- 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 retry exhaustion in simple ring buffer reader swap simple_ring_buffer_swap_reader_page() starts with retry set to 8 and post-decrements it only after a failed link replacement. On the final attempt, a successful replacement leaves retry at zero, while a failed replacement leaves it at -1. The current !retry test reverses both outcomes. It returns an error after a successful final replacement, leaving the link update complete but the reader bookkeeping unfinished. After a failed final replacement, it falls through and updates the head and reader pointers as though the replacement succeeded, which can corrupt the ring. Treat only a negative counter as exhaustion and return the documented -EBUSY error.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 34e5b958bdad0f9cf16306368bbc2dc5b2a50143 · fixed in df02489aa3aa1834659f0d20c89f7d212047d268; From 34e5b958bdad0f9cf16306368bbc2dc5b2a50143 · fixed in e0d3aed7b12cf37b74c7cc5265073d0263b49cde
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.4