CVE-2026-46250

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2026-34112 (ENISA EUVD) · GHSA-9x8g-p3w8-2v5p (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

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.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-05). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 3, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 11, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(25)

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

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 rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 348 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 248 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-46250?
CVE-2026-46250 is a high-severity vulnerability; its CVE record was 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, __current_thread_info is defined as global register variable locating in $gp, and is simply assigned with new address during kernel relocation. This…
When was the CVE record for CVE-2026-46250 published?
The CVE record for CVE-2026-46250 was published on June 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2026-46250 actively exploited?
CVE-2026-46250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46250?
CVE-2026-46250 has a CVSS base score of 7.3 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2026-46250?
A fix for CVE-2026-46250 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46250 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs