Description
In the Linux kernel, the following vulnerability has been resolved:

ring-buffer: Fix subbuf resize race with ring buffer readers

trace_buffer subbuf_size is read lockless in ring_buffer_read_page() and
ring_buffer_read_start(), while it can simultaneously be resized with
ring_buffer_subbuf_order_set().

Instead of trace_buffer::subbuf_size, use bpage::order in
ring_buffer_read_start() and ring_buffer_read_page().

In ring_buffer_read_start(), even with resize_disabled, there is still a
possibility of a race with a buffer modification. Hold the trace_buffer
mutex to synchronise with any pending ring buffer order modification.

trace_buffer::subbuf_size is now actually useless, remove it. Also,
create accessors rb_subbuf_capacity() and rb_page_capacity() which
return the actual size available for storing events, while
rb_subbuf_size() returns the actual subbuf page-size.
Published: 2026-09-11
Score: 7.8 High
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service
Action: Apply Patch
AI Analysis

Impact

A race condition exists in the Linux kernel trace buffer implementation where the subbuffer size field can be read while a resize operation modifies it, causing inconsistent buffer state. This inconsistency can corrupt trace event data and potentially lead to kernel instability, resulting in a denial of service. The weakness is a classic race condition, classified as CWE-366. The reported CVSS score of 7.8 reflects a high severity impact confined to systems running affected kernel versions.

Affected Systems

All Linux kernel releases that include the generic trace buffer implementation with the subbuf_size field are affected, which includes most recent kernel versions used by mainstream distributions. Any system built on such kernels that enables trace buffer logging is potentially vulnerable.

Risk and Exploitability

The EPSS score of less than 1% indicates a very low probability of active exploitation observed to date. The vulnerability is not listed in the CISA KEV catalog, suggesting no widespread exploitation. Although the flaw is local and relies on manipulating internal kernel state, an attacker with local access could trigger the race, leading to a denial of service. The overall risk is high due to the severity but the likelihood of exploitation remains low at this time.

Generated by OpenCVE AI on September 15, 2026 at 19:47 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the kernel to a version that contains the subbuf resize race fix, removing the subbuf_size field and adding proper mutex synchronization.
  • If the patch cannot be applied immediately, temporarily disable trace buffer logging (e.g., set trace_flag to 0 or disable the tracer) to avoid the race condition until the update is performed.
  • If the system is part of a critical environment where trace buffer cannot be disabled, consider applying the backported patch from the stable branch or a security patch bundle that includes this fix until the official kernel release.

Generated by OpenCVE AI on September 15, 2026 at 19:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Debian DSA Debian DSA DSA-6528-1 linux security update
History

Sun, 13 Sep 2026 06:45:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}

cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}


Sat, 12 Sep 2026 00:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-366
References
Metrics threat_severity

None

cvssV3_1

{'score': 4.7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate


Fri, 11 Sep 2026 23:45:00 +0000

Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix subbuf resize race with ring buffer readers trace_buffer subbuf_size is read lockless in ring_buffer_read_page() and ring_buffer_read_start(), while it can simultaneously be resized with ring_buffer_subbuf_order_set(). Instead of trace_buffer::subbuf_size, use bpage::order in ring_buffer_read_start() and ring_buffer_read_page(). In ring_buffer_read_start(), even with resize_disabled, there is still a possibility of a race with a buffer modification. Hold the trace_buffer mutex to synchronise with any pending ring buffer order modification. trace_buffer::subbuf_size is now actually useless, remove it. Also, create accessors rb_subbuf_capacity() and rb_page_capacity() which return the actual size available for storing events, while rb_subbuf_size() returns the actual subbuf page-size.
Title ring-buffer: Fix subbuf resize race with ring buffer readers
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-09-13T06:34:12.518Z

Reserved: 2026-09-11T19:38:34.765Z

Link: CVE-2026-89771

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-11T20:20:08.460

Modified: 2026-09-13T07:17:41.310

Link: CVE-2026-89771

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-09-11T19:47:10Z

Links: CVE-2026-89771 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-15T20:00:08Z

Weaknesses
  • CWE-366

    Race Condition within a Thread