CVE-2025-68802
BaseFortify
Publication date: 2026-01-13
Last updated on: 2026-01-14
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux_kernel | linux_kernel | to 3.13.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version that includes the fix which limits the num_syncs value to DRM_XE_MAX_SYNCS (1024). This prevents userspace from specifying an excessively large num_syncs value that causes oversized allocations. Until the kernel is updated, monitoring for the kernel warnings and restricting untrusted userspace access to the drm/xe driver ioctl interfaces can reduce risk.
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's drm/xe component allows userspace to specify an arbitrary num_syncs value via the exec and vm_bind ioctl calls. Without proper bounds checking, a very large num_syncs value can cause the kernel to attempt an excessively large memory allocation, leading to kernel warnings and potential instability. The fix introduces a limit (DRM_XE_MAX_SYNCS set to 1024) to reject requests exceeding this value, preventing oversized allocations.
How can this vulnerability impact me? :
If exploited, this vulnerability can cause the Linux kernel to perform excessively large memory allocations, which may lead to kernel warnings, degraded system performance, or potential denial of service due to resource exhaustion.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring kernel logs for warnings related to oversized allocations triggered by the drm/xe driver. Specifically, look for kernel warnings similar to the following message in dmesg or /var/log/kern.log: "WARNING: CPU: ... at mm/page_alloc.c:5124 __alloc_frozen_pages_noprof+0x2f8/0x2180" You can use the command: sudo dmesg | grep -i 'WARNING: CPU' | grep -i 'mm/page_alloc.c' or sudo journalctl -k | grep -i 'WARNING: CPU' | grep -i 'mm/page_alloc.c' to detect if such warnings have occurred, indicating attempts to exploit the vulnerability via oversized num_syncs allocations.