Skip to main content
VulnerabilityPublished

CVE-2026-98521: Linux kernel · drm/i915: fix incorrect RCU teardown order

Source GCVE Database

0
Authoritative record:CVE-2026-98521· Medium

Not known to be exploited · fixed in d2da6696e0c4e60414706e607029d0bb0330c67e : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:05 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS
0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d2da6696e0c4e60414706e607029d0bb0330c67e, cc890d3f1b15bf6481dc7270fba0b4fbba572813, c53db9cc245219af6b528ca022a17ebfa91d80ba +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < d2da6696e0c4e60414706e607029d0bb0330c67e
Fixed in
  • d2da6696e0c4e60414706e607029d0bb0330c67e
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < cc890d3f1b15bf6481dc7270fba0b4fbba572813
Fixed in
  • cc890d3f1b15bf6481dc7270fba0b4fbba572813
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < c53db9cc245219af6b528ca022a17ebfa91d80ba
Fixed in
  • c53db9cc245219af6b528ca022a17ebfa91d80ba
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < b12e041aedcf9fa77c6002a49f07eb20d0521b86
Fixed in
  • b12e041aedcf9fa77c6002a49f07eb20d0521b86
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < 4d4ca84213327da1f84ef7af3946dea6b14c5d88
Fixed in
  • 4d4ca84213327da1f84ef7af3946dea6b14c5d88
LinuxLinuxAffected
  • ≥ 912ff2ebd695c582ca4cebf833ad73a378a99f23, < 2dd0190e397ec6468095fd3e80e79276a7361449
Fixed in
  • 2dd0190e397ec6468095fd3e80e79276a7361449

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix has been implemented in the Linux kernel to address this issue by deferring the dropping of fence references until after the RCU grace period. Users should apply the official kernel updates that include this patch to remediate the vulnerability. Since this is a kernel-level fix, upgrading to the patched kernel version is the recommended mitigation.

Description

A vulnerability in the Linux kernel's drm/i915 component related to incorrect RCU teardown order has been resolved. The issue involves the i915_gem_busy_ioctl function iterating over fences in a GEM object without holding a proper reference, only the RCU read side lock. This can cause an endless loop if the GEM object is destroyed concurrently, as the iteration never finishes when encountering a destroyed dma_fence. The fix involves dropping fence references only after the RCU grace period.

References

Community reviews

Loading reviews…