CVE-2026-93284: Linux kernel · drm/pagemap: dma-unmap pages before handling migration errors
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in e4331c6644db85bc6ceb470bd84bcf371b6dbfa6 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in e4331c6644db85bc6ceb470bd84bcf371b6dbfa6, 415f5a755cec5164b149037bf294e270b78d36c6, 9e6372ec2a3990662ae0a67f56ac0aee19848d5b
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 Linux kernel to e4331c6644db85bc6ceb470bd84bcf371b6dbfa6, 415f5a755cec5164b149037bf294e270b78d36c6 or 9e6372ec2a3990662ae0a67f56ac0aee19848d5b.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in specific Linux kernel commits (e4331c6644db85bc6ceb470bd84bcf371b6dbfa6, 415f5a755cec5164b149037bf294e270b78d36c6, 9e6372ec2a3990662ae0a67f56ac0aee19848d5b). Users and administrators should update to these fixed versions or later to remediate the vulnerability.
Description
CVE-2026-93284 is a high-severity vulnerability in the Linux kernel's drm/pagemap component. It involves improper handling of DMA unmapping during page migration error cleanup, where the pages array is cleared too early, leading to invalid page information during DMA unmapping. This flaw has been fixed by ensuring DMA unmapping occurs before the pages array is cleared.