ring-buffer: Stop remote reader update when page swap fails
- 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: ring-buffer: Stop remote reader update when page swap fails The remote swap_reader_page callback can return -EBUSY when the writer moves the head before the remote catches it, particularly during an event storm on a small buffer. __rb_get_reader_page_from_remote() currently warns about that failure but continues with the unchanged reader ID and rearranges the local page list as though the swap succeeded. Handle the callback failure as a recoverable error. Report it with pr_warn_ratelimited() and return NULL. Callers already handle a NULL reader page as a failed attempt. This avoids splicing the same page as both the previous and new reader without flooding the log under contention.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2e67fabd8b77c4f482df9b211bca1b495c6c2c24 · fixed in a14a97048e48471e283d76879b83d2ae323e0722; From 2e67fabd8b77c4f482df9b211bca1b495c6c2c24 · fixed in 5eab74874d11160725c42ab676ba97a797a362eb
- Linux Linux
7.1
- KernelLinux
From 7.1.0 · fixed in 7.2.4