How to Fix CVE-2026-31490: drm/xe/pf: Fix use-after-free in Linux
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-31512: Bluetooth: L2CAP: Validate PDU length before reading SDU length in Linux — Bluetooth: L2CAP: Validate PDU length before reading SDU length in Linux
- How to Fix CVE-2026-23230: Critical Vulnerability in Linux — Critical Vulnerability in Linux
- How to Fix CVE-2026-31406: Linux (Bundle Sibling) , Linux (Bundle Sibling)
- How to Fix CVE-2026-23438: Linux (Bundle Sibling) , Linux (Bundle Sibling)
- How to Fix CVE-2026-5121: Critical Vulnerability in Red Hat Enterprise Linux 7 Extended Lifecycle Support , Critical Vulnerability in Red Hat Enterprise Linux 7 Extended Lifecycle Support
Last verified: 2026-05-25
CVE-2026-31490 is a drm/xe/pf: fix use-after-free in Linux Linux. Fix it by upgrading to 6.19.11, 7.0.
| Severity | CVSS 7.8 - High |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | Linux 1ed30397c0b92b97381dbd11362fdbbf93e046d2 up to (excluding) e28552b4ddea5cb4725380dd08237831af835124; Linux 1ed30397c0b92b97381dbd11362fdbbf93e046d2 up to (excluding) 87997b6c6516e049cbaf2fc6810b213d587a06b1; Linux 6.19 |
| Fixed in | 6.19.11, 7.0 |
| Type (CWE) | Not verified |
What is CVE-2026-31490?
CVE-2026-31490 is a drm/xe/pf: fix use-after-free flaw in Linux Linux. It carries a CVSS base score of 7.8 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: In the Linux kernel, the following vulnerability has been resolved:
drm/xe/pf: Fix use-after-free in migration restore
When an error is returned from xe_sriov_pf_migration_restore_produce(),
the data pointer is not set to NULL, which can trigger use-after-free
in subsequent .write() calls.
Set the pointer to NULL upon error to fix the problem.
(cherry picked from commit 4f53d8c6d23527d734fe3531d08e15cb170a0819)
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of Linux matches a version listed in the Affected row above.
# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux
How to fix CVE-2026-31490
Apply the vendor patch. Target the build named in the Fixed in row above (6.19.11, 7.0). The runnable command set below covers the most common deployment patterns for Linux.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version
RHEL / CentOS / Rocky
sudo dnf upgrade linux -y
rpm -q linux
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux
Expected: a version at or above 6.19.11, 7.0.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-31490 being exploited in the wild?
As of 2026-05-25, CVE-2026-31490 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-31490?
The CVSS base score is 7.8 (High).
What version fixes this?
Upgrade to 6.19.11, 7.0.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://git.kernel.org/stable/c/e28552b4ddea5cb4725380dd08237831af835124
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31490
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://git.kernel.org/stable/c/87997b6c6516e049cbaf2fc6810b213d587a06b1
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*