CVE-2026-46250

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-03. the CNA's CVSS baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 5 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

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 clobbered.

As a result, $gp will continue to point to the unrelocated kernel after the epilog of relocate_kernel(), leading to an early crash in init_idle,

[ 0.000000] CPU 0 Unable to handle kernel paging request at virtual address 0000000000000000, epc == ffffffff81afada8, ra == ffffffff81afad90 [ 0.000000] Oops[#1]: [ 0.000000] CPU: 0 UID: 0 PID: 0 Comm: swapper Tainted: G W 6.19.0-rc5-00262-gd3eeb99bbc99-dirty #188 VOLUNTARY [ 0.000000] Tainted: [W]=WARN [ 0.000000] Hardware name: loongson,loongson64v-4core-virtio [ 0.000000] $ 0 : 0000000000000000 0000000000000000 0000000000000001 0000000000000000 [ 0.000000] $ 4 : ffffffff80b80ec0 ffffffff80b53d48 0000000000000000 00000000000f4240 [ 0.000000] $ 8 : 0000000000000100 ffffffff81d82f80 ffffffff81d82f80 0000000000000001 [ 0.000000] $12 : 0000000000000000 ffffffff81776f58 00000000000005da 0000000000000002 [ 0.000000] $16 : ffffffff80b80e40 0000000000000000 ffffffff80b81614 9800000005dfbe80 [ 0.000000] $20 : 00000000540000e0 ffffffff81980000 0000000000000000 ffffffff80f81c80 [ 0.000000] $24 : 0000000000000a26 ffffffff8114fb90 [ 0.000000] $28 : ffffffff80b50000 ffffffff80b53d40 0000000000000000 ffffffff81afad90 [ 0.000000] Hi : 0000000000000000 [ 0.000000] Lo : 0000000000000000 [ 0.000000] epc : ffffffff81afada8 init_idle+0x130/0x270 [ 0.000000] ra : ffffffff81afad90 init_idle+0x118/0x270 [ 0.000000] Status: 540000e2 KX SX UX KERNEL EXL [ 0.000000] Cause : 00000008 (ExcCode 02) [ 0.000000] BadVA : 0000000000000000 [ 0.000000] PrId : 00006305 (ICT Loongson-3) [ 0.000000] Process swapper (pid: 0, threadinfo=(____ptrval____), task=(____ptrval____), tls=0000000000000000) [ 0.000000] Stack : 9800000005dfbf00 ffffffff8178e950 0000000000000000 0000000000000000 [ 0.000000] 0000000000000000 ffffffff81970000 000000000000003f ffffffff810a6528 [ 0.000000] 0000000000000001 9800000005dfbe80 9800000005dfbf00 ffffffff81980000 [ 0.000000] ffffffff810a6450 ffffffff81afb6c0 0000000000000000 ffffffff810a2258 [ 0.000000] ffffffff81d82ec8 ffffffff8198d010 ffffffff81b67e80 ffffffff8197dd98 [ 0.000000] ffffffff81d81c80 ffffffff81930000 0000000000000040 0000000000000000 [ 0.000000] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 0.000000] 0000000000000000 000000000000009e ffffffff9fc01000 0000000000000000 [ 0.000000] 0000000000000000 0000000000000000 0000000000000000 0000000000000000 [ 0.000000] 0000000000000000 ffffffff81ae86dc ffffffff81b3c741 0000000000000002 [ 0.000000] ... [ 0.000000] Call Trace: [ 0.000000] [] init_idle+0x130/0x270 [ 0.000000] [] sched_init+0x5c8/0x6c0 [ 0.000000] [] start_kernel+0x27c/0x7a8

This bug has been reported to LLVM[2] and affects version from (at least) 18 to 21. Let's work around this by using inline assembly to assign $gp before a fix is widely available.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

June 3, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 11, 2026
No patch confirmed yet.
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3a6498a63394218561065a9a7a597a204f52f6a
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0155dee51b9f5f48aaf5c71cae005eb0e36521f
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9bc3b0ae5203aba650297fdf3e1e774125e423f2
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/561834f6d6f52b8a1791331e94b2aac753491d2a
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4dc65b40fb80c2020efbf139b9a38d30f9a37b92
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/30bfc2d6a1132a89a5f1c3b96c59cf3e4d076ea3
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1fe3b402b1e97a1718df3be0a1d3eee20133e735
generic

MIPS: Work around LLVM bug when gp is used as global register variable - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05bff9b0ae095b2420cfebb4a96759a09334bec6

Vendor Advisories for CVE-2026-46250(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-14ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
linuxKernel @ 5.10.252osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

All Vendor Advisories

(23)

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 288 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 05:34 UTCEG score recompute
  3. 2026-09-14 05:34 UTCVendor advisory
  4. 2026-09-14 05:33 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 23:36 UTCOSV refresh
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-27 14:25 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 03:39 UTCEG score recompute
  22. 2026-08-25 03:39 UTCVendor advisory
  23. 2026-08-25 03:38 UTCGHSA enrichment
  24. 2026-08-24 00:30 UTCVendor advisory
  25. 2026-08-24 00:29 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 12:50 UTCEG score recompute
  2. 2026-08-23 12:50 UTCVendor advisory
  3. 2026-08-23 12:49 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 14:42 UTCEG score recompute
  7. 2026-08-21 14:42 UTCVendor advisory
  8. 2026-08-21 14:42 UTCGHSA enrichment
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 21:44 UTCVendor advisory
  11. 2026-08-20 21:43 UTCGHSA enrichment
  12. 2026-08-20 10:02 UTCEG score recompute
  13. 2026-08-20 10:02 UTCVendor advisory
  14. 2026-08-20 10:01 UTCGHSA enrichment
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 15:48 UTCEG score recompute
  18. 2026-08-17 15:48 UTCVendor advisory
  19. 2026-08-17 15:48 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 03:45 UTCVendor advisory
  22. 2026-08-17 03:45 UTCGHSA enrichment
  23. 2026-08-16 14:57 UTCEG score recompute
  24. 2026-08-16 14:57 UTCVendor advisory
  25. 2026-08-16 14:57 UTCGHSA enrichment
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 02:23 UTCEG score recompute
  28. 2026-08-16 02:23 UTCVendor advisory
  29. 2026-08-16 02:23 UTCGHSA enrichment
  30. 2026-08-16 02:14 UTCEPSS rescore
  31. 2026-08-15 14:44 UTCEG score recompute
  32. 2026-08-15 14:44 UTCVendor advisory
  33. 2026-08-15 14:44 UTCGHSA enrichment
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-14 22:32 UTCVendor advisory
  36. 2026-08-14 22:32 UTCGHSA enrichment
  37. 2026-08-14 10:52 UTCVendor advisory
  38. 2026-08-14 10:52 UTCGHSA enrichment
  39. 2026-08-13 23:13 UTCEG score recompute
  40. 2026-08-13 23:13 UTCVendor advisory
  41. 2026-08-13 23:13 UTCGHSA enrichment
  42. 2026-08-13 22:00 UTCEPSS rescore
  43. 2026-08-13 08:57 UTCVendor advisory
  44. 2026-08-13 08:57 UTCGHSA enrichment
  45. 2026-08-12 21:17 UTCEG score recompute
  46. 2026-08-12 21:17 UTCVendor advisory
  47. 2026-08-12 21:17 UTCGHSA enrichment
  48. 2026-08-12 13:51 UTCEPSS rescore
  49. 2026-08-12 09:38 UTCVendor advisory
  50. 2026-08-12 09:38 UTCGHSA enrichment
  51. 2026-08-11 21:58 UTCEG score recompute
  52. 2026-08-11 21:58 UTCVendor advisory
  53. 2026-08-11 21:58 UTCGHSA enrichment
  54. 2026-08-11 10:18 UTCEG score recompute
  55. 2026-08-11 10:18 UTCVendor advisory
  56. 2026-08-11 10:18 UTCGHSA enrichment
  57. 2026-08-11 00:00 UTCEPSS rescore
  58. 2026-08-10 22:38 UTCVendor advisory
  59. 2026-08-10 22:38 UTCGHSA enrichment
  60. 2026-08-10 10:22 UTCVendor advisory
  61. 2026-08-10 10:22 UTCGHSA enrichment
  62. 2026-08-09 22:42 UTCEG score recompute
  63. 2026-08-09 22:42 UTCVendor advisory
  64. 2026-08-09 22:42 UTCGHSA enrichment
  65. 2026-08-09 13:46 UTCEPSS rescore
  66. 2026-08-09 11:03 UTCVendor advisory
  67. 2026-08-09 11:03 UTCGHSA enrichment
  68. 2026-08-08 23:22 UTCEG score recompute
  69. 2026-08-08 23:22 UTCVendor advisory
  70. 2026-08-08 23:22 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 11:42 UTCVendor advisory
  73. 2026-08-08 11:42 UTCGHSA enrichment
  74. 2026-08-07 23:58 UTCEG score recompute
  75. 2026-08-07 23:58 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-46250?
CVE-2026-46250 is a high vulnerability published on June 3, 2026. 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, currentthreadinfo is defined as global register variable locating in $gp, and is simply assigned with new address during kernel relocation. This…
When was CVE-2026-46250 disclosed?
CVE-2026-46250 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46250 actively exploited?
CVE-2026-46250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-46250?
CVE-2026-46250 has a CVSS v4.0 base score of 7.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-46250?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46250, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46250

Explore →

Is Your Infrastructure Affected by CVE-2026-46250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.