In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: save IRQ state in blkg_tryget_closest() bio_set_dev() associates the… (CVE-2026-98832)
Description
A vulnerability in the Linux kernel's blk-cgroup subsystem involves improper handling of interrupt states in the function blkg_tryget_closest(). This can lead to deadlocks due to interrupts being enabled while a spinlock is held, allowing nested lock acquisition in softirq context. The issue arises when bio_set_dev() is called with interrupts disabled, but blkg_tryget_closest() unconditionally enables interrupts, causing inconsistent lock usage and potential deadlock. The problem was introduced after changes to locking mechanisms and requires saving and restoring the caller's IRQ state to prevent this condition.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel blk-cgroup vulnerability (CVE-2026-98832) stems from improper interrupt state management in blkg_tryget_closest(). Specifically, bio_set_dev() associates a bio with a block group (blkg), and if the blkg lookup misses, blkg_tryget_closest() acquires the queue lock using spin_lock_irq() and releases it with spin_unlock_irq(), which unconditionally enables local interrupts. If the caller had interrupts disabled (e.g., dm-thin's pool_map()), this leads to interrupts being enabled while holding a spinlock, allowing an I/O completion softirq to run on the same CPU and re-acquire the same lock, causing a deadlock. Previous fixes were reverted due to changes in locking location. The correct fix involves saving and restoring the caller's IRQ state to avoid enabling interrupts unexpectedly.
Potential Impact
This vulnerability can cause deadlocks in the Linux kernel blk-cgroup subsystem when interrupts are enabled while holding a spinlock, leading to inconsistent lock usage and potential system hangs or degraded performance. It affects kernel stability and reliability but does not directly indicate privilege escalation or data corruption.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix involves saving and restoring the caller's IRQ state in blkg_tryget_closest() to prevent enabling interrupts while holding locks. Users should monitor official Linux kernel advisories for patches addressing this issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9gxg-wj69-fwm2
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-98832"]
Threat ID: 6ad520a92cdf04f6569938a9
Added to database: 10/18/2026, 19:40:25 UTC
Last enriched: 10/18/2026, 22:17:44 UTC
Last updated: 10/18/2026, 22:17:44 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.