ring-buffer: Check resize_disabled before publishing the new subbuf order
- 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.12.111, 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: ring-buffer: Check resize_disabled before publishing the new subbuf order ring_buffer_subbuf_order_set() stores the new order and only then walks the CPUs, returning -EBUSY if any of them has resizing disabled. A user mapped buffer has resizing disabled, and __rb_map_vma() reads buffer->subbuf_order without buffer->mutex, so an mmap of an already mapped CPU racing the failing order change sizes the mapping with the new order and inserts pages past the sub-buffer into the VMA. Check the CPUs before storing the new order.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 117c39200d9d760cbd5944bb89efb7b9c51965aa · fixed in f2099644e1b2a2c0805c5240d63ab0522d9d0174; From 117c39200d9d760cbd5944bb89efb7b9c51965aa · fixed in 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06; From 117c39200d9d760cbd5944bb89efb7b9c51965aa · fixed in 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76; From 117c39200d9d760cbd5944bb89efb7b9c51965aa · fixed in d860c67c051685abb0460b593b193f0f45f4fa92
- Linux Linux
6.10
- KernelLinux
From 6.10.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53; From 6.19.0 · fixed in 7.2.7