CVE-2025-68802 json
drm/xe: Limit num_syncs to prevent oversized allocations
published 9mo ago modified 4mo ago also EUVD-2026-2298
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Limit num_syncs to prevent oversized allocations
The exec and vm_bind ioctl allow userspace to specify an arbitrary num_syncs value. Without bounds checking, a very large num_syncs can force an excessively large allocation, leading to kernel warnings from the page allocator as below.
Introduce DRM_XE_MAX_SYNCS (set to 1024) and reject any request exceeding this limit.
" ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at mm/page_alloc.c:5124 __alloc_frozen_pages_noprof+0x2f8/0x2180 mm/page_alloc.c:5124 ... Call Trace: <TASK> alloc_pages_mpol+0xe4/0x330 mm/mempolicy.c:2416 ___kmalloc_large_node+0xd8/0x110 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0xe0 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kmalloc_noprof+0x3d4/0x4b0 mm/slub.c:4388 kmalloc_noprof include/linux/slab.h:909 [inline] kmalloc_array_noprof include/linux/slab.h:948 [inline] xe_exec_ioctl+0xa47/0x1e70 drivers/gpu/drm/xe/xe_exec.c:158 drm_ioctl_kernel+0x1f1/0x3e0 drivers/gpu/drm/drm_ioctl.c:797 drm_ioctl+0x5e7/0xc50 drivers/gpu/drm/drm_ioctl.c:894 xe_drm_ioctl+0x10b/0x170 drivers/gpu/drm/xe/xe_device.c:224 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:598 [inline] __se_sys_ioctl fs/ioctl.c:584 [inline] __x64_sys_ioctl+0x18b/0x210 fs/ioctl.c:584 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xbb/0x380 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f ... "
v2: Add "Reported-by" and Cc stable kernels. v3: Change XE_MAX_SYNCS from 64 to 1024. (Matt & Ashutosh) v4: s/XE_MAX_SYNCS/DRM_XE_MAX_SYNCS/ (Matt) v5: Do the check at the top of the exec func. (Matt)
(cherry picked from commit b07bac9bd708ec468cd1b8a5fe70ae2ac9b0a11c)
Patch / fix
- Linux Linux 6.12.64, 6.18.3, 6.19
- linux Debian 13 6.12.69-1
- linux Debian 14 6.18.3-1
debian advisories DEBIAN-CVE-2025-68802
- linux Ubuntu 25.10 6.17.0-22.22
- linux-aws Ubuntu 25.10 6.17.0-1012.12
- linux-gcp Ubuntu 25.10 6.17.0-1012.12
- linux-azure Ubuntu 25.10 6.17.0-1013.13
- linux-raspi Ubuntu 25.10 6.17.0-1013.13
- linux-riscv Ubuntu 25.10 6.17.0-22.22.1
- linux-oracle Ubuntu 25.10 6.17.0-1011.11
- linux-aws-6.17 Ubuntu 24.04 LTS 6.17.0-1012.12~24.04.1
ubuntu advisories UBUNTU-CVE-2025-68802
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-rt Linux Micro 6.2 6.12.0-160000.26.1
- kernel-64kb SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-source SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-default SLES 16.0, SLE High Availability Extension 16.0, Linux Micro 6.2 +1 more 6.12.0-160000.26.1
- kernel-default-base SLES 16.0, Linux Micro 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1.160000.2.7
- kernel-syms SLES 16.0, Linux Micro Extras 6.2, SLES for SAP applications 16.0 6.12.0-160000.26.1
- kernel-azure SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.26.1
- kernel-obs-qa SLES for SAP applications 16.0, SLES 16.0 6.12.0-160000.26.1
suse advisories SUSE-SU-2026:20555-1SUSE-SU-2026:20599-1SUSE-SU-2026:20615-1SUSE-SU-2026:20570-1SUSE-SU-2026:0587-1SUSE-SU-2026:0472-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.26.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.26.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.26.1
opensuse advisories openSUSE-SU-2026:20287-1
Is CVE-2025-68802 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-68802 updated cvss 5.5
kernel: drm/xe: Limit num_syncs to prevent oversized allocations
-
Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).
Affected products
- Linux Linux
Classification
- Technology feeds
References
Sources
- CVE List CVE-2025-68802
- NVD CVE-2025-68802
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.