CVE-2025-38690
BaseFortify
Publication date: 2025-09-04
Last updated on: 2025-11-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-617 | The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's drm/xe/migrate function, where an infinite recursion can happen due to misaligned bounce buffers allocated on the stack. When the buffer plus offset is not aligned to XE_CACHELINE_BYTES, a bounce buffer is used. However, this bounce buffer is only naturally aligned to u8, not to XE_CACHELINE_BYTES. If the bounce buffer is also misaligned, the function recurses again, potentially causing infinite recursion and eventually a stack overflow or kernel panic. The fix involves using kmalloc to allocate the bounce buffer with proper power-of-two alignment, preventing the infinite recursion and kernel panic.
How can this vulnerability impact me? :
This vulnerability can cause a kernel panic due to infinite recursion and stack overflow when the affected code path is triggered. This can lead to system instability, crashes, and potential denial of service on systems running the vulnerable Linux kernel.
What immediate steps should I take to mitigate this vulnerability?
Update the Linux kernel to a version that includes the fix for this vulnerability, which replaces the stack-allocated bounce buffer with a kmalloc-allocated buffer to prevent infinite recursion and kernel panic. Avoid triggering the vulnerable code path through eudebug until the patch is applied.