Linux kernel RCE in the dw-edma DMA driver can lead to kernel memory corruption or code execution across many Linux-based devices; widespread kernel impact warrants broad IT notification.
CVE-2026-93042
Linux dw-edma DMA termination bug can cause use-after-free and kernel RCE.
do firstUpgrade to a fixed release: < 5.3, >= 6.6.157 and <= 6.6.*, >= 6.12.110 and <= 6.12.*, >= 6.18.52 and <= 6.18.* (+2 more below).
Is CVE-2026-93042 being exploited?
Not confirmed. CVE-2026-93042 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-93042?
CVE-2026-93042 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-93042?
Yes. A fix has been recorded for CVE-2026-93042. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-93042 affect?
CVE-2026-93042 affects Linux kernel (dw-edma / dmaengine), Devices using Synopsys DesignWare EDMA (embedded SoCs), Any distro/kernel including patched driver. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-93042?
Apply the upstream/stable kernel patch or vendor update and reboot affected systems.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Use-after-free during DMA termination enables kernel memory corruption, local privilege escalation or arbitrary kernel code execution via malicious DMA or crafted workloads.
Immediate action required
- affected>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf and < 65e387b95d3855aa894ac729e1778e5bcb9083cb
- affected>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf and < 4793f9099a1cadf4e37f3a03d524af6bce88a0ea
- affected>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf and < be87d86537de7ea6fd025f41033d2faff880973f
- affected>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf and < f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7
- affected>= e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf and < 99109a51efd28c9a661fbfb9469b023c517b31d1
- affected5.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
timeline
- 17 Sept 2026Published
- 19 Sept 2026Analysed by vulneraibility.com · 2 days later
- 30 Oct 2026CVE record last updated · 41 days later
- Linkgit.kernel.org /stable/c/da56839aced48ecb70033962d7ea98f55b0c5656
- Linkgit.kernel.org /stable/c/65e387b95d3855aa894ac729e1778e5bcb9083cb
- Linkgit.kernel.org /stable/c/4793f9099a1cadf4e37f3a03d524af6bce88a0ea
- Linkgit.kernel.org /stable/c/be87d86537de7ea6fd025f41033d2faff880973f
- Linkgit.kernel.org /stable/c/f3ec6702a1d216be61f692cc0a983d6c8fb5ebf7
- Linkgit.kernel.org /stable/c/99109a51efd28c9a661fbfb9469b023c517b31d1
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.