GHSA-VQ2V-33JV-5CR9
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31In 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.
{
"affected": [],
"aliases": [
"CVE-2026-99158"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:36Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nring-buffer: Fix false warning in ring_buffer_map_get_reader()\n\nThe mmap reader can warn when it catches up with a writer that is still\ncommitting events. rb_get_reader_page() returns NULL in this case, but\nring_buffer_map_get_reader() treats that result as an error.\n\nThe initial rb_per_cpu_empty() check filters out an empty buffer, but it\ndoes not guarantee that the next reader page has committed data. Writers\ndo not take reader_lock and can advance commit_page before publishing the\ncommitted length on the new page. rb_get_reader_page() can swap to that\npage, catch up with the writer and return NULL.\n\nHandle NULL through the existing no-data exit without warning. Remove the\ncaller\u0027s reader_page == commit_page check as well, since the reader-page\nhelper already handles that case. The existing metadata update and return\npath remain in place.",
"id": "GHSA-vq2v-33jv-5cr9",
"modified": "2026-10-28T12:31:05Z",
"published": "2026-10-28T12:31:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99158"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/029770f5badedc0f0ff85fc45e24785cbbee4a67"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/68e6ab180cfb6dfa79652f41ed7899a6d4cf5438"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/89bab1dba8a0167ef0d819e0f55b6bafa038e87f"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.