{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80730 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80730 is a vulnerability in Linux, published on 3 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-80730 and fix it if it is affected.\n\nWhat it is: CVE-2026-80730 is a vulnerability in Linux, published on 3 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-80730 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-80730/ (Markdown: https://insights.sbomify.com/CVE-2026-80730/index.md)","id":"CVE-2026-80730","markdown":"https://insights.sbomify.com/CVE-2026-80730/index.md","name":"CVE-2026-80730","record":{"aliases":["AZL-99051","BELL-CVE-2026-80730","DEBIAN-CVE-2026-80730","GHSA-p8f7-pqwj-r94v","UBUNTU-CVE-2026-80730"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A kernel crash occurs during ring-buffer self-tests when error pointers are mishandled, causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","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 crash passing ERR_PTR to kthread_stop()\n\nIn test_ringbuffer()'s out_free cleanup loop, the check\n`!rb_threads[cpu]` only catches NULL entries and misses entries that\nhold an ERR_PTR.\n\nrb_threads[] is static, so unassigned slots are NULL. But when\nkthread_run_on_cpu() fails for a cpu, it stores ERR_PTR(-ENOMEM) (or\n-EINTR) in rb_threads[cpu] before the creation loop jumps to out_free.\nThat entry is non-NULL, so the old `!ptr` check does not break, and the\ncleanup proceeds to call kthread_stop() on the ERR_PTR. kthread_stop()\nthen dereferences the bogus pointer, crashing the kernel during the\nlate_initcall self-test.\n\ncrash logs:\n  BUG: kernel NULL pointer dereference, address: 000000000000001c\n  Oops: 0002 [#1] SMP NOPTI\n  CPU: 1 PID: 1 Comm: swapper/0 Not tainted 7.2.0-rc6-dirty #7 PREEMPT(lazy)\n  RIP: 0010:kthread_stop+0x2e/0x220\n  RBX: fffffffffffffff4\n  CR2: 000000000000001c\n  Call Trace:\n   \u003cTASK\u003e\n   test_ringbuffer+0x1ec/0x650\n   do_one_initcall+0x6c/0x2c0\n   kernel_init_freeable+0x21d/0x420\n   kernel_init+0x15/0x1c0\n   ret_from_fork+0x21b/0x320\n   \u003c/TASK\u003e\n  Kernel panic - not syncing: Fatal exception","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 crash passing ERR_PTR to kthread_stop()","id":"CVE-2026-80730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header","id":"CVE-2026-80731"},"packages":[],"prev":{"headline":"mm/huge_memory: initialise workingset state before folio split","id":"CVE-2026-80729"},"products":["Linux"],"published":"2026-09-03","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-09-03","vendors":["Linux"]},"summary":"A kernel crash occurs during ring-buffer self-tests when error pointers are mishandled, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2026-80730/"}