CVE-2026-31479·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/xe: always keep track of remap prev/next During 3D workload, user is reporting hitting: [ 413.361679] WARNING: drivers/gpu/drm/xe/xe_vm.c:1217 at vm_bind_ioctl_ops_unwind+0x1e2/0x2e0 [xe], CPU#7: vkd3d_queue/9925 [ 413.361944] CPU: 7 UID: 1000 PID: 9925 Comm: vkd3d_queue Kdump: loaded Not tainted 7.0.0-070000rc3-generic #202603090038 PREEMPT(lazy) [ 413.361949] RIP: 0010:vm_bind_ioctl_ops_unwind+0x1e2/0x2e0 [xe] [ 413.362074] RSP: 0018:ffffd4c25c3df930 EFLAGS: 00010282 [ 413.362077] RAX: 0000000000000000 RBX: ffff8f3ee817ed10 RCX: 0000000000000000 [ 413.362078] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 413.362079] RBP: ffffd4c25c3df980 R08: 0000000000000000 R09: 0000000000000000 [ 413.362081] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8f41fbf99380 [ 413.362082] R13: ffff8f3ee817e968 R14: 00000000ffffffef R15: ffff8f43d00bd380 [ 413.362083] FS: 00000001040ff6c0(0000) GS:ffff8f4696d89000(0000) knlGS:00000000330b0000 [ 413.362085] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 [ 413.362086] CR2: 00007ddfc4747000 CR3: 00000002e6262005 CR4: 0000000000f72ef0 [ 413.362088] PKRU: 55555554 [ 413.362089] Call Trace: [ 413.362092] <TASK> [ 413.362096] xe_vm_bind_ioctl+0xa9a/0xc60 [xe] Which seems to hint that the vma we are re-inserting for the ops unwind is either invalid or overlapping with something already inserted in the vm. It shouldn't be invalid since this is a re-insertion, so must have worked before. Leaving the likely culprit as something already placed where we want to insert the vma. Following from that, for the case where we do something like a rebind in the middle of a vma, and one or both mapped ends are already compatible, we skip doing the rebind of those vma and set next/prev to NULL. As well as then adjust the original unmap va range, to avoid unmapping the ends. However, if we trigger the unwind path, we end up with three va, with the two ends never being removed and the original va range in the middle still being the shrunken size. If this occurs, one failure mode is when another unwind op needs to interact with that range, which can happen with a vector of binds. For example, if we need to re-insert something in place of the original va. In this case the va is still the shrunken version, so when removing it and then doing a re-insert it can overlap with the ends, which were never removed, triggering a warning like above, plus leaving the vm in a bad state. With that, we need two things here: 1) Stop nuking the prev/next tracking for the skip cases. Instead relying on checking for skip prev/next, where needed. That way on the unwind path, we now correctly remove both ends. 2) Undo the unmap va shrinkage, on the unwind path. With the two ends now removed the unmap va should expand back to the original size again, before re-insertion. v2: - Update the explanation in the commit message, based on an actual IGT of triggering this issue, rather than conjecture. - Also undo the unmap shrinkage, for the skip case. With the two ends now removed, the original unmap va range should expand back to the original range. v3: - Track the old start/range separately. vma_size/start() uses the va info directly. (cherry picked from commit aec6969f75afbf4e01fd5fb5850ed3e9c27043ac)
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.19.11
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 3% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-31479 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
Affected versions
From: 6.19
Until: 6.19.11
Fixed in: 6.19.11
How to fix this CVE
Update the Linux kernel to version 6.19.11 or later to resolve a critical memory mapping issue in the DRM/XE GPU driver that can cause kernel warnings and VM corruption during 3D workloads. This patch ensures proper tracking of virtual memory address ranges during bind operations, preventing overlapping mappings that lead to system instability. Apply the update immediately, especially if you use Intel XE GPU or run graphics-intensive applications.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check current kernel version with `uname -r` and verify if it falls within 6.19.0 to 6.19.10
- Step 2: Confirm XE GPU driver is loaded by running `lsmod | grep xe` — if output is empty, this CVE does not apply to your system
- Step 3: Search kernel logs for the specific warning with `sudo dmesg | grep -i 'vm_bind_ioctl_ops_unwind'` or `sudo journalctl -b | grep -i xe_vm`
- Step 4: After patching, verify the new kernel version is running with `uname -r` and confirm it is 6.19.11 or later
FAQ
What is CVE-2026-31479?
This is a memory management flaw in the Linux kernel's DRM/XE GPU driver where virtual memory address (VA) tracking during GPU buffer bind operations becomes inconsistent, allowing previously unmapped memory regions to persist and overlap with newly inserted mappings, causing kernel warnings and potential VM corruption.
Is CVE-2026-31479 being actively exploited?
No, this CVE is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are available. However, it can be triggered by normal 3D workloads (such as vkd3d_queue operations), making it a reliability issue for systems using Intel XE GPUs.
What versions of Kernel are affected by CVE-2026-31479?
Linux kernel versions 6.19.0 through 6.19.10 are affected. The vulnerability is fixed in kernel 6.19.11 and later versions.
How do I check if my server is vulnerable to CVE-2026-31479?
Run `uname -r` to check your kernel version. If the output shows 6.19.0 through 6.19.10, your system is vulnerable. Additionally, run `lsmod | grep xe` to confirm the XE GPU driver is active — if neither command shows a match, the vulnerability does not affect your configuration.
Does Defensia detect CVE-2026-31479?
Yes — Defensia's CVE advisory scanner compares installed kernel versions against the NVD database. If the Linux kernel is installed on a monitored server and falls within the vulnerable range, CVE-2026-31479 will appear in your dashboard with automated remediation guidance.
Related Kernel CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-31479. Free for 1 server.
Get started free