GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Check your stack
CVE-2026-99158unknown

ring-buffer: Fix false warning in ring_buffer_map_get_reader()

Impact

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

Source excerpt · Linux

What to do

Remove the caller's reader_page == commit_page check as well, since the reader-page helper already handles that case.

Linux guidance

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Linux · Linux

Other versions: unaffected

Version / rangeSource status
117c39200d9d760cbd5944bb89efb7b9c51965aa to before 029770f5badedc0f0ff85fc45e24785cbbee4a67affected
117c39200d9d760cbd5944bb89efb7b9c51965aa to before 68e6ab180cfb6dfa79652f41ed7899a6d4cf5438affected
117c39200d9d760cbd5944bb89efb7b9c51965aa to before 89bab1dba8a0167ef0d819e0f55b6bafa038e87faffected
Linux version evidence

Linux · Linux

Other versions: affected

Version / rangeSource status
6.10affected
0 to before 6.10unaffected
6.18.59 through 6.18.* (inclusive)unaffected
7.2.13 through 7.2.* (inclusive)unaffected
7.3 through * (inclusive)unaffected
Linux version evidence

Original source 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