{"cve":"CVE-2026-98832","nvd":{"published":"2026-10-18T16:17:37.443","modified":"2026-10-19T10:19:47.233","status":"Received","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->queue_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->lock taken with\nspin_lock_irq().  The nested spin_unlock_irq() then enables interrupts\nwhile pool->lock is still held, so an I/O completion softirq can run on\nthe same CPU, re-acquire pool->lock (thin_endio(), or overwrite_endio()\n-> 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.","cvss_v4":null,"cvss_v3":null,"cwes":[],"references":["https://git.kernel.org/stable/c/327c428ba79b13e4cc5253333a9d5c0aa5579bdf","https://git.kernel.org/stable/c/9fcf4317384ce6758c3127a6e8914c54cbb9c8cc"],"products":[],"source":"nvd","synced_at":"2026-10-19T23:00:53.604569364+00:00"},"epss":{"cve":"CVE-2026-98832","score":0.00155,"percentile":0.04642,"date":"2026-10-25"},"kev":null,"osv":[],"attribution":["This product uses the NVD API but is not endorsed or certified by the NVD.","EPSS scores: FIRST Exploit Prediction Scoring System, https://www.first.org/epss","Known exploited vulnerabilities: CISA Known Exploited Vulnerabilities Catalog, https://www.cisa.gov/known-exploited-vulnerabilities-catalog","Package advisories: OSV (https://osv.dev), from the GitHub Advisory Database, PyPA, Go, RustSec and other ecosystem databases, under CC-BY 4.0 or CC0","CVE records: the CVE Program's CVE List (https://www.cve.org), under its terms of use (https://www.cve.org/Legal/TermsOfUse). CVE is a registered trademark of The MITRE Corporation; this product is not affiliated with the CVE Program."]}