ring-buffer: Check resize_disabled before publishing the new subbuf order (CVE-2026-97617) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-97617

ring-buffer: Check resize_disabled before publishing the new subbuf order

Answer in brief

CVE-2026-97617 records a Unknown severity vulnerability in ring-buffer: Check resize_disabled before publishing the new subbuf order. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=117c39200d9d760cbd5944bb89efb7b9c51965aa <f2099644e1b2a2c0805c5240d63ab0522d9d0174 \|\| >=117c39200d9d760cbd5944bb89efb7b9c51965aa <9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06 \|\| >=117c39200d9d760cbd5944bb89efb7b9c51965aa <32bf47db9237c5b8b6f6aaa5356bb4c79d241f76 \|\| >=117c39200d9d760cbd5944bb89efb7b9c51965aa <d860c67c051685abb0460b593b193f0f45f4fa92	f2099644e1b2a2c0805c5240d63ab0522d9d0174, 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06, 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76, d860c67c051685abb0460b593b193f0f45f4fa92
Linux/Linuxgeneric	6.10	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to f2099644e1b2a2c0805c5240d63ab0522d9d0174 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.