CVE-2025-68802: drm/xe: Limit num_syncs to prevent oversized allocations
In the Linux kernel, the following vulnerability has been resolved:
drm/xe: Limit numsyncs to prevent oversized allocations
The exec and vmbind ioctl allow userspace to specify an arbitrary numsyncs value. Without bounds checking, a very large numsyncs can force an excessively large allocation, leading to kernel warnings from the page allocator as below.
Introduce DRMXEMAXSYNCS (set to 1024) and reject any request exceeding this limit.
" ------------[ cut here ]------------ WARNING: CPU: 0 PID: 1217 at mm/pagealloc.c:5124 allocfrozenpagesnoprof+0x2f8/0x2180 mm/pagealloc.c:5124 ... Call Trace: <TASK> allocpagesmpol+0xe4/0x330 mm/mempolicy.c:2416 kmalloclargenode+0xd8/0x110 mm/slub.c:4317 kmalloclargenodenoprof+0x18/0xe0 mm/slub.c:4348 dokmallocnode mm/slub.c:4364 [inline] kmallocnoprof+0x3d4/0x4b0 mm/slub.c:4388 kmallocnoprof include/linux/slab.h:909 [inline] kmallocarraynoprof include/linux/slab.h:948 [inline] xeexecioctl+0xa47/0x1e70 drivers/gpu/drm/xe/xeexec.c:158 drmioctlkernel+0x1f1/0x3e0 drivers/gpu/drm/drmioctl.c:797 drmioctl+0x5e7/0xc50 drivers/gpu/drm/drmioctl.c:894 xedrmioctl+0x10b/0x170 drivers/gpu/drm/xe/xedevice.c:224 vfsioctl fs/ioctl.c:51 [inline] dosysioctl fs/ioctl.c:598 [inline] sesysioctl fs/ioctl.c:584 [inline] x64sysioctl+0x18b/0x210 fs/ioctl.c:584 dosyscallx64 arch/x86/entry/syscall64.c:63 [inline] dosyscall64+0xbb/0x380 arch/x86/entry/syscall64.c:94 entrySYSCALL64afterhwframe+0x77/0x7f ... "
v2: Add "Reported-by" and Cc stable kernels. v3: Change XEMAXSYNCS from 64 to 1024. (Matt & Ashutosh) v4: s/XEMAXSYNCS/DRMXEMAXSYNCS/ (Matt) v5: Do the check at the top of the exec func. (Matt)
(cherry picked from commit b07bac9bd708ec468cd1b8a5fe70ae2ac9b0a11c)
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Upgrade
Upgrade
ubuntu/linux-aws-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1012.12~24.04.1 - Upgrade
Upgrade
ubuntu/linux-azure-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1013.13~24.04.1 - Upgrade
Upgrade
ubuntu/linux-gcp-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1012.12~24.04.1 - Upgrade
Upgrade
ubuntu/linux-hwe-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-22.22~24.04.1 - Upgrade
Upgrade
ubuntu/linux-nvidia-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1018.18 - Upgrade
Upgrade
ubuntu/linux-oem-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1020.20 - Upgrade
Upgrade
ubuntu/linux-oracle-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1011.11~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-22.22.1~24.04.1 - Upgrade
Upgrade
ubuntu/linux-realtime-6.17to a version that resolves this vulnerability.Fixed in 6.17.0-1010.11~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 6.17.0-22.22 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 6.17.0-1012.12 - Upgrade
Upgrade
ubuntu/linux-azureto a version that resolves this vulnerability.Fixed in 6.17.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 6.17.0-1012.12 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 6.17.0-1011.11 - Upgrade
Upgrade
ubuntu/linux-raspito a version that resolves this vulnerability.Fixed in 6.17.0-1013.13 - Upgrade
Upgrade
ubuntu/linux-realtimeto a version that resolves this vulnerability.Fixed in 6.17.0-1010.11 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 6.17.0-22.22.1 - Upgrade
Upgrade
Linux kernelto a version that resolves this vulnerability.Patch b07bac9bd708ec468cd1b8a5fe70ae2ac9b0a11c
Event History
Frequently Asked Questions
What is the severity of CVE-2025-68802?
CVE-2025-68802 is classified as a high severity vulnerability due to its potential to cause oversized memory allocations.
How does CVE-2025-68802 affect the Linux kernel?
CVE-2025-68802 allows userspace to specify an arbitrary num_syncs value which leads to a lack of bounds checking and potential resource exhaustion.
How do I fix CVE-2025-68802?
To fix CVE-2025-68802, update your Linux kernel to the latest patched version where this vulnerability has been addressed.
Which versions of the Linux kernel are affected by CVE-2025-68802?
CVE-2025-68802 affects various versions of the Linux kernel that do not implement limits on the num_syncs parameter in affected ioctls.
Is there a workaround for CVE-2025-68802?
Currently, the best workaround for CVE-2025-68802 is to apply the patch or update the kernel version to mitigate the risks associated.