{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99160 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99160 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99160 and fix it if it is affected.\n\nWhat it is: CVE-2026-99160 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99160 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-99160/ (Markdown: https://insights.sbomify.com/CVE-2026-99160/index.md)","id":"CVE-2026-99160","markdown":"https://insights.sbomify.com/CVE-2026-99160/index.md","name":"CVE-2026-99160","record":{"aliases":["BELL-CVE-2026-99160","DEBIAN-CVE-2026-99160","GHSA-pw95-h85m-gvhp","UBUNTU-CVE-2026-99160"],"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: Do not show buffer_meta for CPUs without a buffer\n\nThe per_cpu/cpuN/buffer_meta files are created for every possible CPU,\nbut buffer-\u003ebuffers[cpu] is only allocated once that CPU comes online.\nReading the file of a CPU that never came online dereferences a NULL\ncpu_buffer in rbm_start().\n\nFail the open with -ENODEV when the CPU has no buffer, as the other\nper CPU ring buffer interfaces do.","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: Do not show buffer_meta for CPUs without a buffer","id":"CVE-2026-99160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe()","id":"CVE-2026-99161"},"packages":[],"prev":{"headline":"ring-buffer: Fix the sub-buffer array base in rb_meta_subbuf_idx()","id":"CVE-2026-99159"},"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-99160/"}