Skip to main content

Linux CVE-2026-98342

| EUVDEUVD-2026-93327
2026-10-06 Linux GHSA-jvjw-jpr2-5gjp
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:

dmaengine: wait for RCU readers before releasing dma_device

dma_issue_pending_all() walks the dma_device_list with list_for_each_entry_rcu() under rcu_read_lock(). dma_device_release() unlinks the device with list_del_rcu() and then calls device->device_release() (which in many drivers, such as plx_dma.c, directly calls kfree()).

Because there is no grace period between unlinking the device and freeing it, concurrent RCU readers in dma_issue_pending_all() can access the device after it has been freed.

The lockless walk originally relied on clients holding a dmaengine reference to pin the provider module, and therefore the device, for as long as they might traverse the list. Commit 8ad342a86359 ("dmaengine: Add reference counting to dma_device struct") decoupled the dma_device lifetime from the module reference, so the device can now be released while a reader is still walking the list.

Add synchronize_rcu() before the device is freed, so RCU readers are guaranteed to have finished. Keep it unconditional: providers that do not implement device_release() free the device themselves once dma_async_device_unregister() returns. This call will delay for a grace period with dma_list_mutex held, which is safe and only teardown path is delayed.

Affected VersionsENISA

Linux patch: 5.10.271
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <cbb3310a5167e868a5e763e32b9a23b4d50669ee
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77
Linux patch: 7.3-rc4
Linux patch: 6.12.112
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <14578c78405d51fa92e4ada4502a45f537c0fcb8
Linux 2.6.29
Linux patch: 6.6.158
Linux patch: 5.15.222
Linux patch: 6.18.54
Linux patch: 0
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <4aed7e47a10b94ea3c5171e8d1382081accd2e03
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <dc750422170a563c7a81f6e49d36bb02c62ae37f
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <8577a5ec4f7e00443015ef99f646def093121a1b
Linux patch: 7.2.8
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <4448a539a0c39141cccc67be6cacde0f35024313
Linux 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 <ac8ce9f89638d6d79875cca7d8ae42566a9bde15
Linux patch: 6.1.189

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 06, 2026 - 10:02 EUVD
CVE Published
Oct 06, 2026 - 08:46 cve.org
UNKNOWN (no severity yet)

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% 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