CVE-2026-98832

Status: ReceivedUnscored—

Severity—Unscored

Exploitation probability0.15 %higher than 4% of CVEs

Active exploitationNonot in the CISA catalog

Public exploitNot knownno public code found

In the Linux kernel, the following vulnerability has been resolved:

blk-cgroup: save IRQ state in blkg_tryget_closest()

bio_set_dev() associates the bio with a blkg through bio_associate_blkg(). If the blkg lookup misses, blkg_tryget_closest() takes q->queue_lock with spin_lock_irq() and releases it with spin_unlock_irq(), which unconditionally enables local interrupts.

Callers may call bio_set_dev() with interrupts already disabled, e.g. dm-thin's pool_map() does so while holding pool->lock taken with spin_lock_irq().

Read full descriptionShow less

The nested spin_unlock_irq() then enables interrupts while pool->lock is still held, so an I/O completion softirq can run on the same CPU, re-acquire pool->lock (thin_endio(), or overwrite_endio() -> complete_mapping_preparation()) and deadlock. lockdep reports this as inconsistent SOFTIRQ-ON-W to IN-SOFTIRQ-W usage.

Commit 3a762de55b4e ("block: save irq state in blkg_lookup_create()") fixed the same problem while the lock lived in blkg_lookup_create(), but commit 9327a865e395 ("blk-cgroup: don't nest queue_lock under rcu in blkg_lookup_create()") moved the locking into blkg_tryget_closest() and reverted it to spin_lock_irq().

Save and restore the caller's IRQ state instead.

CVSS

NVD hasn't assigned a CVSS score to this CVE (common since the April 2026 policy change).

Exploitation probability (EPSS)

Probability of exploitation in the next 30 days: 0.15 %
Percentile among all scored CVEs: 4
Score date: 10/20/2026

EPSS (Exploit Prediction Scoring System, FIRST) estimates how likely a vulnerability is to be exploited in the wild within 30 days. It complements CVSS (impact) and CISA KEV (confirmed exploitation).

Affected technologies (1)

⚠ AI-inferred from the description — NVD hasn't analyzed this CVE yet, these aren't verified CPEs.

Linux — Linux Kernel^AI

References

Show 2 references

Raw JSON (NVD)

Show

{
  "id": "CVE-2026-98832",
  "cveTags": [],
  "metrics": {},
  "affected": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "affectedData": [
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "9327a865e395a53f67dffac4710beb1d4730495e",
              "lessThan": "9fcf4317384ce6758c3127a6e8914c54cbb9c8cc",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "9327a865e395a53f67dffac4710beb1d4730495e",
              "lessThan": "327c428ba79b13e4cc5253333a9d5c0aa5579bdf",
              "versionType": "git"
            }
          ],
          "programFiles": [
            "block/blk-cgroup.c"
          ],
          "defaultStatus": "unaffected"
        },
        {
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "product": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.2"
            },
            {
              "status": "unaffected",
              "version": "0",
              "lessThan": "7.2",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "7.2.10",
              "versionType": "semver",
              "lessThanOrEqual": "7.2.*"
            },
            {
              "status": "unaffected",
              "version": "7.3",
              "versionType": "original_commit_for_fix",
              "lessThanOrEqual": "*"
            }
          ],
          "programFiles": [
            "block/blk-cgroup.c"
          ],
          "defaultStatus": "affected"
        }
      ]
    }
  ],
  "published": "2026-10-18T16:17:37.443",
  "references": [
    {
      "url": "https://git.kernel.org/stable/c/327c428ba79b13e4cc5253333a9d5c0aa5579bdf",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    },
    {
      "url": "https://git.kernel.org/stable/c/9fcf4317384ce6758c3127a6e8914c54cbb9c8cc",
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "vulnStatus": "Received",
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    }
  ],
  "lastModified": "2026-10-19T10:19:47.233",
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}