{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99159 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99159 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99159 and fix it if it is affected.\n\nWhat it is: CVE-2026-99159 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99159 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-99159/ (Markdown: https://insights.sbomify.com/CVE-2026-99159/index.md)","id":"CVE-2026-99159","markdown":"https://insights.sbomify.com/CVE-2026-99159/index.md","name":"CVE-2026-99159","record":{"aliases":["BELL-CVE-2026-99159","DEBIAN-CVE-2026-99159","GHSA-pqhv-wx6p-7gp4","UBUNTU-CVE-2026-99159"],"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 the sub-buffer array base in rb_meta_subbuf_idx()\n\nOn a persistent ring buffer, rb_meta_subbuf_idx() can return an index one\nsub-buffer too high.  rb_setup_ids_meta_page() then fills subbuf_ids[]\nshifted by one and leaves subbuf_ids[0] NULL, which __rb_map_vma()\ndereferences when userspace maps trace_pipe_raw.  rb_update_meta_reader()\nwrites two such indices into meta-\u003ebuffers[], which rb_cpu_meta_valid()\nwould reject on the next boot, discarding the previous boot's trace.\n\nA CPU's sub-buffer array starts after its meta header and the nr_subbufs\nintegers that follow, aligned up to a sub-buffer.  rb_meta_subbuf_idx()\ninverts that calculation but skips only the integers, not the header, so\nits base is one sub-buffer low whenever the omitted header size crosses\nthe alignment boundary.\n\nInvert the calculation with rb_subbufs_from_meta() rather than repeating\nit.  rb_range_buffer() maps an index back to an address through the same\nhelper, so the two directions can no longer disagree.","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 the sub-buffer array base in rb_meta_subbuf_idx()","id":"CVE-2026-99159","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: Do not show buffer_meta for CPUs without a buffer","id":"CVE-2026-99160"},"packages":[],"prev":{"headline":"ring-buffer: Fix false warning in ring_buffer_map_get_reader()","id":"CVE-2026-99158"},"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-99159/"}