ring-buffer: Check resize_disabled before publishing the new subbuf order
Published Sep 25, 2026
No CVSS score
EPSS 0.20%
Description
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 products
-
Affected
- ≥ , <
- ≥ , <
- ≥ , <
- ≥ , <
-
Affected
- 6.10
Unaffected
- ≥ 0, < 6.10
- ≥ 6.12.111, ≤ 6.12.*
- ≥ 6.18.53, ≤ 6.18.*
- ≥ 7.2.7, ≤ 7.2.*
- 7.3-rc3
Default status is the baseline for the product. Each version can override it (patched versions can be marked unaffected).
No data.
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
No CWE recorded.
References (5)
- https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-86748 Advisory
- https://git.kernel.org/stable/c/32bf47db9237c5b8b6f6aaa5356bb4c79d241f76
- https://git.kernel.org/stable/c/9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06
- https://git.kernel.org/stable/c/d860c67c051685abb0460b593b193f0f45f4fa92
- https://git.kernel.org/stable/c/f2099644e1b2a2c0805c5240d63ab0522d9d0174
Change history (0)
No recorded changes yet.
CVE.org / MITRE
CISA Vulnrichment
No data
Red Hat
No data
GitHub
No data