{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98832 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98832 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98832 and fix it if it is affected.\n\nWhat it is: CVE-2026-98832 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98832 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-98832/ (Markdown: https://insights.sbomify.com/CVE-2026-98832/index.md)","id":"CVE-2026-98832","markdown":"https://insights.sbomify.com/CVE-2026-98832/index.md","name":"CVE-2026-98832","record":{"aliases":["DEBIAN-CVE-2026-98832","GHSA-9gxg-wj69-fwm2","UBUNTU-CVE-2026-98832"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A race condition in the Linux kernel block cgroup subsystem can cause a deadlock and system hang when interrupts are improperly enabled during nested lock acquisition.","user_interaction":"not_required","vuln_class":"race_condition"},"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\nblk-cgroup: save IRQ state in blkg_tryget_closest()\n\nbio_set_dev() associates the bio with a blkg through bio_associate_blkg().\nIf the blkg lookup misses, blkg_tryget_closest() takes q-\u003equeue_lock with\nspin_lock_irq() and releases it with spin_unlock_irq(), which\nunconditionally enables local interrupts.\n\nCallers may call bio_set_dev() with interrupts already disabled, e.g.\ndm-thin's pool_map() does so while holding pool-\u003elock taken with\nspin_lock_irq().  The nested spin_unlock_irq() then enables interrupts\nwhile pool-\u003elock is still held, so an I/O completion softirq can run on\nthe same CPU, re-acquire pool-\u003elock (thin_endio(), or overwrite_endio()\n-\u003e complete_mapping_preparation()) and deadlock.  lockdep reports this\nas inconsistent SOFTIRQ-ON-W to IN-SOFTIRQ-W usage.\n\nCommit 3a762de55b4e (\"block: save irq state in blkg_lookup_create()\")\nfixed the same problem while the lock lived in blkg_lookup_create(), but\ncommit 9327a865e395 (\"blk-cgroup: don't nest queue_lock under rcu in\nblkg_lookup_create()\") moved the locking into blkg_tryget_closest() and\nreverted it to spin_lock_irq().\n\nSave and restore the caller's IRQ state instead.","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":"blk-cgroup: save IRQ state in blkg_tryget_closest()","id":"CVE-2026-98832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"mtd: core: call _get_device() with the master MTD","id":"CVE-2026-98833"},"packages":[],"prev":{"headline":"of/overlay: don't leak fragment references when changeset init fails","id":"CVE-2026-98831"},"products":["Linux"],"published":"2026-10-18","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-19","vendors":["Linux"]},"summary":"A race condition in the Linux kernel block cgroup subsystem can cause a deadlock and system hang when interrupts are improperly enabled during nested lock acquisition.","url":"https://insights.sbomify.com/CVE-2026-98832/"}