CVE-2026-74602 ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
A missing initialization in the Linux kernel ring buffer can cause memory corruption during page freeing, potentially leading to crashes or code execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-74602?
CVE-2026-74602 is a memory corruption vulnerability in Linux, published on 22 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
In the Linux kernel, the following vulnerability has been resolved:
ring-buffer: Initialise reader page order in rb_allocate_cpu_buffer()
In rb_allocate_cpu_buffer(), bpage->order was omitted, leaving it as 0. This is an issue for a ring-buffer with subbufs bigger than PAGE_SIZE if when freed: free_buffer_page() relies on this value. Align the value with the actual allocation size (buffer::subbuf_order).
Which versions are affected by CVE-2026-74602?
How do I fix CVE-2026-74602?
Apply the vendor's patch.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-74602 being exploited?
There is no known exploitation of CVE-2026-74602 in the wild and no public exploit code.
Sources
Also known as BELL-CVE-2026-74602, DEBIAN-CVE-2026-74602, GHSA-f8mj-87c7-35x8, UBUNTU-CVE-2026-74602.