Review reviewHigh

CVE-2026-46250

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: MIPS: Work around LLVM bug when gp is used as global register variable On MIPS, __current_thread_info is defined as global register variable locating in $gp, and is simply assigned with new address during kernel relocation. This however is broken with LLVM, which always restores $gp if it finds $gp is clobbered in any form, including when intentionally through a global register variable. This is against GCC's documentation[1], which requires a callee-saved register used as global register variable not to be restored if it's...

CVSS
7.3
EPSS
0.13%
2.87% percentile
CISA KEV
Not listed
Published
2026.06.04
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.3

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: MIPS: Work around LLVM bug when gp is used as global register variable On MIPS, __current_thread_info is defined as global register variable locating in $gp, and is simply assigned with new address during kernel relocation. This however is broken with LLVM, which always restores $gp if it finds $gp is clobbered in any form, including when intentionally through a global register variable. This is against GCC's documentation[1], which requires a callee-saved register used as global register variable not to be restored if it's...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 05bff9b0ae095b2420cfebb4a96759a09334bec6, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 1fe3b402b1e97a1718df3be0a1d3eee20133e735, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 4dc65b40fb80c2020efbf139b9a38d30f9a37b92, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < c0155dee51b9f5f48aaf5c71cae005eb0e36521f, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < e3a6498a63394218561065a9a7a597a204f52f6a, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 561834f6d6f52b8a1791331e94b2aac753491d2a, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 9bc3b0ae5203aba650297fdf3e1e774125e423f2, >= 279b991b24d2439fbe9d2f093988b9c8aed2603d < 30bfc2d6a1132a89a5f1c3b96c59cf3e4d076ea3, >= 4.7, >= 4.7 < 5.10.252, >= 5.11 < 5.15.202, >= 5.16 < 6.1.165, >= 6.2 < 6.6.128, >= 6.7 < 6.12.75, >= 6.13 < 6.18.14, >= 6.19 < 6.19.4
Fixed versions
5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.12.75, 6.18.14, 6.19.4

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
CWE
Not available