CVE-2025-71083: Linux kernel · drm/ttm: Avoid NULL pointer deref for evicted BOs
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b94182b3d7228aec18d069cba56d5982e9bfe1b1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in b94182b3d7228aec18d069cba56d5982e9bfe1b1, 491adc6a0f9903c32b05f284df1148de39e8e644, 47a85604a761005d255ae38115ee630cc6931756 +3
Exploitation evidence
Disclosed: evidence found.
CVE published 13 Jan 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 to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: drm/ttm: Avoid NULL pointer deref for evicted BOs It is possible for a BO to exist that is not currently associated with a resource, e.g. because it has been evicted. When devcoredump tries to read the contents of all BOs for dumping, we need to expect this as well -- in this case, ENODATA is recorded instead of the buffer contents.
References
- git.kernel.org/stable/c/47a85604a761005d255ae38115ee630cc6931756 (opens in a new tab)
- git.kernel.org/stable/c/4b9944493c6d92d7b29cfd83aaf3deb842b8da79 (opens in a new tab)
- git.kernel.org/stable/c/3d004f7341d4898889801ebb2ef61ffca610dd6f (opens in a new tab)
- git.kernel.org/stable/c/5a81095d3e1b521ac7cfe3b14d5f149bace3d6e0 (opens in a new tab)
- git.kernel.org/stable/c/b94182b3d7228aec18d069cba56d5982e9bfe1b1 (opens in a new tab)
- git.kernel.org/stable/c/491adc6a0f9903c32b05f284df1148de39e8e644 (opens in a new tab)