{"id":"CVE-2026-98832","published":"2026-10-18T16:17:37.443","lastModified":"2026-10-19T10:19:47.233","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.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/327c428ba79b13e4cc5253333a9d5c0aa5579bdf","tags":[]},{"url":"https://git.kernel.org/stable/c/9fcf4317384ce6758c3127a6e8914c54cbb9c8cc","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}