{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99158 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99158 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99158 and fix it if it is affected.\n\nWhat it is: CVE-2026-99158 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99158 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-99158/ (Markdown: https://insights.sbomify.com/CVE-2026-99158/index.md)","id":"CVE-2026-99158","markdown":"https://insights.sbomify.com/CVE-2026-99158/index.md","name":"CVE-2026-99158","record":{"aliases":["BELL-CVE-2026-99158","DEBIAN-CVE-2026-99158","GHSA-vq2v-33jv-5cr9","UBUNTU-CVE-2026-99158"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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's 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ring-buffer: Fix false warning in ring_buffer_map_get_reader()","id":"CVE-2026-99158","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ring-buffer: Fix the sub-buffer array base in rb_meta_subbuf_idx()","id":"CVE-2026-99159"},"packages":[],"prev":{"headline":"scsi: bsg: Pass reply_len to bsg_setup_queue() to fit UFS ARPMB replies","id":"CVE-2026-99157"},"products":["Linux"],"published":"2026-10-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99158/"}