CVE-2026-31784: Linux kernel · drm/xe/pxp: Clear restart flag in pxp_start after jumping back
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 76903b2057c8677c2c006e87fede15f496555dc0 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:33 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- 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-11-06.
- Patch
- Available – fixed in 76903b2057c8677c2c006e87fede15f496555dc0, 400ee45f80480c05c3fa673967f25faab8323753, 9e962e68a9d26135af67c423767c0983d9ad94c3
Exploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 2026.
What to do
Upgrade Linux kernel to 76903b2057c8677c2c006e87fede15f496555dc0, 400ee45f80480c05c3fa673967f25faab8323753 or 9e962e68a9d26135af67c423767c0983d9ad94c3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been fixed in the specified commits. Users should update their Linux kernel to a version including these fixes to remediate the issue.
Description
A vulnerability in the Linux kernel's drm/xe/pxp component was fixed by clearing a restart flag in the pxp_start function after jumping back. Without clearing this flag, the function would repeatedly jump back to its beginning, causing unintended behavior. This issue was resolved in specific commits.