VulnerabilityPublished 28 Oct 2026

CVE-2026-99158: Linux kernel · ring-buffer: Fix false warning in ring_buffer_map_get_reader()

Affects Linux kernelSource CVE Database V5

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

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 029770f5badedc0f0ff85fc45e24785cbbee4a67, 89bab1dba8a0167ef0d819e0f55b6bafa038e87f, 68e6ab180cfb6dfa79652f41ed7899a6d4cf5438

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to 029770f5badedc0f0ff85fc45e24785cbbee4a67, 89bab1dba8a0167ef0d819e0f55b6bafa038e87f or 68e6ab180cfb6dfa79652f41ed7899a6d4cf5438.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < 029770f5badedc0f0ff85fc45e24785cbbee4a67	Fixed in 029770f5badedc0f0ff85fc45e24785cbbee4a67
LinuxLinux	Affected ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < 89bab1dba8a0167ef0d819e0f55b6bafa038e87f	Fixed in 89bab1dba8a0167ef0d819e0f55b6bafa038e87f
LinuxLinux	Affected ≥ 117c39200d9d760cbd5944bb89efb7b9c51965aa, < 68e6ab180cfb6dfa79652f41ed7899a6d4cf5438	Fixed in 68e6ab180cfb6dfa79652f41ed7899a6d4cf5438
LinuxLinux	Affected =6.10	Fixed in–

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.

References

Community reviews

Loading reviews…