CVE-2026-99158

ring-buffer: Fix false warning in ring_buffer_map_get_reader()

Published Oct 28, 2026 CVSS 3.1 · 4.1 Medium EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

ring-buffer: Fix false warning in ring_buffer_map_get_reader()

The mmap reader can warn when it catches up with a writer that is still
committing events. rb_get_reader_page() returns NULL in this case, but
ring_buffer_map_get_reader() treats that result as an error.

The initial rb_per_cpu_empty() check filters out an empty buffer, but it
does not guarantee that the next reader page has committed data. Writers
do not take reader_lock and can advance commit_page before publishing the
committed length on the new page. rb_get_reader_page() can swap to that
page, catch up with the writer and return NULL.

Handle NULL through the existing no-data exit without warning. Remove the
caller's reader_page == commit_page check as well, since the reader-page
helper already handles that case. The existing metadata update and return
path remain in place.

Analysis

AI-generated

Technical impact

The report addresses a bug in the Linux kernel ring-buffer subsystem. The function ring_buffer_map_get_reader() incorrectly treats a NULL return from rb_get_reader_page() as an error, causing a false warning when the reader catches up to a writer that is still committing events. This issue originates from a race condition whereby writers can advance commit_page before publishing the committed length on the new page. Because the warning is purely diagnostic and does not correlate with data corruption, there is no direct threat to confidentiality, integrity, or availability.

Affected Systems

The vulnerability applies to all Linux kernel versions that include the buggy ring-buffer implementation. It affects distributions that ship a kernel containing the unpatched code, and vendors maintaining such kernels must verify that the fix has been merged. The specific commits referenced in the provided Git URLs identify the patch that resolves the problem.

Risk and Exploitability

The CVSS base score of 4.1 indicates low severity. The EPSS score is under 1%, implying a very low probability of exploitation in the wild. The vulnerability is not listed in the CISA KEV catalog. Because the fault only generates an unnecessary warning and does not expose data or permit privilege escalation, the practical risk to an attacker is negligible. The likely attack vector involves observing kernel log messages; it offers no actionable foothold for remote code execution or denial of service.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to the latest stable release that incorporates commit 029770f5badedc0f0ff85fc45e24785cbbee4a67 or later.
  • If your distribution does not yet ship the fix, apply the patch manually using the source files referenced in the provided Git URLs.
  • Adjust or disable logging for ring-buffer warnings so that false alerts do not trigger monitoring or incident response.

Generated by OpenCVE AI on November 2, 2026 at 03:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
History
Type Values Removed Values Added
Weaknesses CWE-690
Type Values Removed Values Added
Weaknesses CWE-617
References
Metrics threat_severity

None

cvssV3_1

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

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Linux linux
Vendors & Products Linux linux
Type Values Removed Values Added
Weaknesses CWE-690
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix false warning in ring_buffer_map_get_reader() The mmap reader can warn when it catches up with a writer that is still committing events. rb_get_reader_page() returns NULL in this case, but ring_buffer_map_get_reader() treats that result as an error. The initial rb_per_cpu_empty() check filters out an empty buffer, but it does not guarantee that the next reader page has committed data. Writers do not take reader_lock and can advance commit_page before publishing the committed length on the new page. rb_get_reader_page() can swap to that page, catch up with the writer and return NULL. Handle NULL through the existing no-data exit without warning. Remove the caller's reader_page == commit_page check as well, since the reader-page helper already handles that case. The existing metadata update and return path remain in place.
Title ring-buffer: Fix false warning in ring_buffer_map_get_reader()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Oct 30, 2026, 12:42 PM
Reserved
Sep 25, 2026, 10:25 AM
Status
Received
Published
Oct 28, 2026, 11:17 AM
Modified
Oct 30, 2026, 1:21 PM
Severity
Moderate
Public date
Oct 28, 2026, 10:35 AM