linux: In the Linux kernel, the following vulnerability has been resolved: drm/xe: Limit num_syncs to prevent oversized all...
CVE-2025-68802 is fixed in 18 products on 1 platform, first by DEBIAN-CVE-2025-68802, released January 13, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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)
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-64kb · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-64kb · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-azure · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.20.27.1 | SUSE-SU-2026:0472-1 | Feb 12, 2026 |
| kernel-azure · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-default · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-default · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-default-base · opensuse-leap 16.0 | 6.12.0-160000.26.1.160000.2.7 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.31.1.150700.17.21.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-default-base · sles 16.0 | 6.12.0-160000.26.1.160000.2.7 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-docs · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-docs · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-kvmsmall · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-kvmsmall · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-livepatch-SLE15-SP7-RT_Update_9 · sles 15.7 | 1-150700.1.3.2 | SUSE-SU-2026:0587-1 | Feb 20, 2026 |
| kernel-livepatch-SLE15-SP7_Update_9 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-obs-build · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-obs-qa · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-obs-qa · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-rt · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-source · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-source · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-source-azure · sles 15.7 | 6.4.0-150700.20.27.1 | SUSE-SU-2026:0472-1 | Feb 12, 2026 |
| kernel-syms · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-syms · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| kernel-syms-azure · sles 15.7 | 6.4.0-150700.20.27.1 | SUSE-SU-2026:0472-1 | Feb 12, 2026 |
| kernel-zfcpdump · opensuse-leap 16.0 | 6.12.0-160000.26.1 | OPENSUSE-SU-2026:20287-1 | Feb 27, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.31.1 | SUSE-SU-2026:0447-1 | Feb 11, 2026 |
| kernel-zfcpdump · sles 16.0 | 6.12.0-160000.26.1 | SUSE-SU-2026:20599-1 | Feb 27, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.69-1 | DEBIAN-CVE-2025-68802 | Jan 13, 2026 |
| linux · Debian 14 | 6.18.3-1 | DEBIAN-CVE-2025-68802 | Jan 13, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.