Unknown

CVE-2026-98342 — dmaengine: wait for RCU readers before releasing dma_device

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.

Published Oct 6, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+1

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.18%

ahead of 7% of scored CVEs · Oct 14, 2026

Affects

Linux

CVSS base

—

Score not published yet.

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Linux	Linux	≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < ac8ce9f89638d6d79875cca7d8ae42566a9bde15≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < 14578c78405d51fa92e4ada4502a45f537c0fcb8≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < cbb3310a5167e868a5e763e32b9a23b4d50669ee≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < 8577a5ec4f7e00443015ef99f646def093121a1b≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < 4448a539a0c39141cccc67be6cacde0f35024313≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < 4aed7e47a10b94ea3c5171e8d1382081accd2e03≥ 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 and < dc750422170a563c7a81f6e49d36bb02c62ae37f and 1 more version 2.6.29	Vulnerable	CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Not enough vector or weakness data: use the affected application’s logs as a starting point.

application logs

Timeline

What happened to this CVE, newest first.

2026
Record published
Oct 13, 2026
Affected products added · linux/linux
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Source status changed · → Received
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Oct 6, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

git.kernel.org/stable/c/dc750422170a563c7a81f6e49d36bb02c62ae37f
NIST National Vulnerability Database
git.kernel.org/stable/c/fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77
NIST National Vulnerability Database
git.kernel.org/stable/c/4aed7e47a10b94ea3c5171e8d1382081accd2e03
NIST National Vulnerability Database
git.kernel.org/stable/c/cbb3310a5167e868a5e763e32b9a23b4d50669ee
NIST National Vulnerability Database
git.kernel.org/stable/c/14578c78405d51fa92e4ada4502a45f537c0fcb8
NIST National Vulnerability Database
git.kernel.org/stable/c/8577a5ec4f7e00443015ef99f646def093121a1b
NIST National Vulnerability Database
git.kernel.org/stable/c/ac8ce9f89638d6d79875cca7d8ae42566a9bde15
NIST National Vulnerability Database
git.kernel.org/stable/c/4448a539a0c39141cccc67be6cacde0f35024313
NIST National Vulnerability Database

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No CVSS score published by NVD, the CNA, CISA or GitHub so far.
No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-98342 is "dmaengine: wait for RCU readers before releasing dma_device", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.