ring-buffer: Check resize_disabled before publishing the new subbuf order
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76, Kernel 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06, Kernel d860c67c051685abb0460b593b193f0f45f4fa92 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.10, >=117c39200d9d760cbd5944bb89efb7b9c51965aa <32bf47db9237c5b8b6f6aaa5356bb4c79d241f76, >=117c39200d9d760cbd5944bb89efb7b9c51965aa <9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06, >=117c39200d9d760cbd5944bb89efb7b9c51965aa <d860c67c051685abb0460b593b193f0f45f4fa92, >=117c39200d9d760cbd5944bb89efb7b9c51965aa <f2099644e1b2a2c0805c5240d63ab0522d9d0174 | 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76, 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06, d860c67c051685abb0460b593b193f0f45f4fa92, f2099644e1b2a2c0805c5240d63ab0522d9d0174 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket