Skip to main content
VulnerabilityPublished Updated

CVE-2026-97617: Linux kernel · ring-buffer: Check resize_disabled before publishing the new subbuf order

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f2099644e1b2a2c0805c5240d63ab0522d9d0174 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:47 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in f2099644e1b2a2c0805c5240d63ab0522d9d0174, d860c67c051685abb0460b593b193f0f45f4fa92, 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Linux kernel to f2099644e1b2a2c0805c5240d63ab0522d9d0174, d860c67c051685abb0460b593b193f0f45f4fa92, 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76 or 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < f2099644e1b2a2c0805c5240d63ab0522d9d0174
Fixed in
  • f2099644e1b2a2c0805c5240d63ab0522d9d0174
LinuxLinuxAffected
  • ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < d860c67c051685abb0460b593b193f0f45f4fa92
Fixed in
  • d860c67c051685abb0460b593b193f0f45f4fa92
LinuxLinuxAffected
  • ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76
Fixed in
  • 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76
LinuxLinuxAffected
  • ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06
Fixed in
  • 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06
LinuxLinuxAffected
  • =6.10
Fixed in–

AI-suggested

A fix is available in the Linux kernel as identified by the commits f2099644e1b2a2c0805c5240d63ab0522d9d0174, d860c67c051685abb0460b593b193f0f45f4fa92, 32bf47db9237c5b8b6f6aaa5356bb4c79d241f76, and 9fd4ea952e6ac12a63c3fe89f08ad02771aa2c06. Users and administrators should update to the patched Linux kernel version 6.10 or later containing these fixes to remediate the issue.

Description

A vulnerability in the Linux kernel's ring-buffer subsystem allows a race condition during resizing of user-mapped buffers. The function ring_buffer_subbuf_order_set() updates the sub-buffer order without properly checking if resizing is disabled on CPUs, leading to potential inconsistencies in memory mapping. This can cause the kernel to insert pages beyond the intended sub-buffer into the virtual memory area (VMA). The issue is fixed by verifying CPU states before updating the sub-buffer order.

References

Community reviews

Loading reviews…