CVE-2026-46250
Kernel Relocation Failure in Linux due to LLVM GP Register Handling
Publication date: 2026-06-03
Last updated on: 2026-06-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| llvm | llvm | From 18 (inc) to 21 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel on MIPS architecture due to a bug in LLVM compiler versions 18 to 21. The issue arises because the global pointer register ($gp), used as a global register variable for __current_thread_info, is restored incorrectly by LLVM after kernel relocation. LLVM restores $gp even when it is intentionally clobbered, which contradicts GCC's behavior and documentation. As a result, $gp points to the unrelocated kernel, causing an early crash during kernel initialization (init_idle).
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash early during system startup on affected MIPS systems using LLVM versions 18 to 21. The crash occurs because the global pointer register points to an incorrect memory location, leading to kernel paging errors and system instability. This can result in denial of service as the system fails to boot properly.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability manifests as an early crash in the Linux kernel on MIPS architectures using LLVM, with kernel paging request errors and specific oops messages during system initialization.
To detect this issue, monitor your system logs (e.g., dmesg or /var/log/kern.log) for kernel oops messages similar to the following:
- CPU 0 Unable to handle kernel paging request at virtual address 0000000000000000
- Oops[#1]: CPU: 0 UID: 0 PID: 0 Comm: swapper Tainted: G W
- epc : ffffffff81afada8 init_idle+0x130/0x270
Suggested commands to check for these logs include:
- dmesg | grep -i 'Unable to handle kernel paging request'
- journalctl -k | grep -i 'Oops'
- cat /var/log/kern.log | grep -i 'init_idle'
These commands help identify if the kernel is crashing due to this specific issue related to the $gp register being restored incorrectly by LLVM.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is caused by LLVM restoring the $gp register incorrectly on MIPS architectures, leading to kernel crashes.
Immediate mitigation involves applying the patch that works around the LLVM bug by using inline assembly to assign the $gp register before a fix is widely available.
If you are maintaining your own kernel build, update to the fixed Linux kernel version that includes this workaround.
Alternatively, avoid using affected LLVM versions (from at least 18 to 21) for building the kernel on MIPS until the issue is resolved.
Monitor for updates from LLVM and your Linux distribution for official patches.