Skip to main content

Linux CVE-2026-98521

| EUVDEUVD-2026-103761
2026-10-18 Linux GHSA-7hvf-3rfm-fg86
View
Monitor Track and reassess. Why: No CVSS yet + weak signal (CWE or non-zero EPSS).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisCVE.org

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

drm/i915: fix incorrect RCU teardown order

i915_gem_busy_ioctl uses dma_resv_for_each_fence_unlocked() to iterate over the fences in an GEM object without holding a reference but only the RCU read side lock.

What can happen here is that the GEM object is destroyed concurrently while i915_gem_busy_ioctl is still running. This won't free the GEM objects memory, but still drops all the dma_fence references.

Now when dma_resv_for_each_fence_unlocked() sees a destroyed dma_fence it assumes that a new fence list was installed and re-starts the loop.

But in the case of a destroyed GEM object a new fence list is never installed, only the old one freed and therefore the iteration never finishes resulting in an endless loop.

The solution is to drop the fence references only after the RCU grace period.

The fixes tag is not necessary the patch introducing the problem, but the one making it so worse that we need to address it.

This problem was pointed out by Sashiko-bot.

(cherry picked from commit 5113479556025093bf8133bb2dcaa33be2d50921)

Affected VersionsENISA

Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <cc890d3f1b15bf6481dc7270fba0b4fbba572813
Linux patch: 7.2.9
Linux patch: 6.18.55
Linux patch: 7.3-rc5
Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <d2da6696e0c4e60414706e607029d0bb0330c67e
Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <4d4ca84213327da1f84ef7af3946dea6b14c5d88
Linux patch: 6.12.112
Linux patch: 0
Linux 5.17
Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <b12e041aedcf9fa77c6002a49f07eb20d0521b86
Linux patch: 6.6.158
Linux patch: 6.1.189
Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <2dd0190e397ec6468095fd3e80e79276a7361449
Linux 912ff2ebd695c582ca4cebf833ad73a378a99f23 <c53db9cc245219af6b528ca022a17ebfa91d80ba

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Lifecycle Timeline

2
Patch available
Oct 18, 2026 - 16:02 EUVD
CVE Published
Oct 18, 2026 - 15:17 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity Not scored yet
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
No CVSS yet + weak signal (CWE or non-zero EPSS)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy