Menu

Star on GitHub · 3.4k

CVE-2026-97617

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 a…

Published Sep 25, 2026EPSS 0.21%

Overview

CVE-2026-97617 is a known-severity vulnerability. It was published on September 25, 2026.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-97617?

CVE-2026-97617 is a known-severity vulnerability. It was published on September 25, 2026.

How severe is CVE-2026-97617?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-97617?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-97617?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-97617 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

CyberStrike v2 is here — more intelligence, greater reach