cve.bz

CVE-2026-80606 linux linux

7.8 highEPSS 0.2%Fix available

High (7.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: drm/xe/userptr: Hold notifier_lock for write on inject test path When CONFIG_DRM_XE_USERPTR_INVAL_INJECT=y, xe_pt_svm_userptr_pre_commit() runs vma_check_userptr() with the svm notifier_lock taken for read. The test injection causes vma_check_userptr() to call xe_vma_userptr_force_invalidate(), which feeds into xe_vma_userptr_do_inval() with drm_gpusvm_ctx.in_notifier=true. That flag tells drm_gpusvm_unmap_pages() the caller already holds notifier_lock for write and only asserts the mode. Because the caller actually holds it for read, the assertion fires: WARNING: drivers/gpu/drm/drm_gpusvm.c:1669 at \ drm_gpusvm_unmap_pages+0xd4/0x130 [drm_gpusvm_helper] Call Trace: xe_vma_userptr_do_inval+0x40d/0xfd0 [xe] xe_vma_userptr_invalidate_pass1+0x3e6/0x8d0 [xe] xe_vma_userptr_force_invalidate+0xde/0x290 [xe] vma_check_userptr.constprop.0+0x1c6/0x220 [xe] xe_pt_svm_userptr_pre_commit+0x6a3/0xc60 [xe] ... xe_vm_bind_ioctl+0x3a0a/0x4480 [xe] Acquire notifier_lock for write in pre-commit when the inject Kconfig is enabled, via new helpers xe_pt_svm_userptr_notifier_lock()/_unlock(). Rename xe_svm_assert_held_read() to xe_svm_assert_held_read_or_inject_write() so it asserts the correct mode under each build configuration. Production builds (CONFIG_DRM_XE_USERPTR_INVAL_INJECT=n) keep the existing read-mode behavior bit-for-bit. (cherry picked from commit 80ccbd97ffee8ad2e73167d826fe7be548364365)

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-80606 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80606?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80606?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80606 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.18 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.40
Linux7.17.1.5
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian14linux7.1.5-1DEBIAN-CVE-2026-80606
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-80606
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-80606
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-80606
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 moreno fix listedUBUNTU-CVE-2026-80606
Ubuntu24.04:LTSlinux-aws-7.0, linux-gcp-7.07.0.0-1014.14~24.04.1UBUNTU-CVE-2026-80606 USN-8887-2 USN-8887-3
Ubuntu24.04:LTSlinux-azure-7.07.0.0-1017.17~24.04.1UBUNTU-CVE-2026-80606 USN-8888-2
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1016.16~24.04.1UBUNTU-CVE-2026-80606 USN-8888-2
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-38.38~24.04.4UBUNTU-CVE-2026-80606 USN-8887-3
Ubuntu24.04:LTSlinux-nvidia-7.07.0.0-1024.25~24.04.1UBUNTU-CVE-2026-80606 USN-9003-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1013.13~24.04.1UBUNTU-CVE-2026-80606 USN-8887-3
Ubuntu24.04:LTSlinux-riscv, linux-oem-6.8, linux-aws-6.14 and 22 moreno fix listedUBUNTU-CVE-2026-80606
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-38.38.1~24.04.1UBUNTU-CVE-2026-80606
12 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquitastreamlinux-lts6.18.43-r0BELL-CVE-2026-80606

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A low impact flaw was found in the Linux kernel drm/xe/userptr driver. When the test-only kernel configuration option CONFIG_DRM_XE_USERPTR_INVAL_INJECT is enabled, xe_pt_svm_userptr_pre_commit() runs vma_check_userptr() while holding the SVM notifier_lock for read, but the userptr invalidation injection path requires that lock for write. This incorrect lock mode triggers an assertion failure in drm_gpusvm_unmap_pages() that can crash the kernel, resulting in a local denial of service. A local user with access to the DRM device can trigger this path through the VM bind ioctl. Only availability is affected; there is no impact on confidentiality or integrity. Production builds, which ship with CONFIG_DRM_XE_USERPTR_INVAL_INJECT disabled, keep the existing read-lock behavior and are not affected, which is why the Red Hat affected-product scope distinguishes builds that enable this test configuration. Because the flaw is limited to a test-injection code path and to availability impact, Red Hat rates its severity lower (impact LOW, CVSS 5.5) than the upstream CVEORG score of 7.8.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80606.

References

Check your stackJSON