CVE-2026-98228

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.8EG
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.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

mips: select CONFIG_WEAK_REORDERING_BEYOND_LLSC from CONFIG_EYEQ

On I6500 CPU cores, lld and scd give no ordering guarantees (same as all other instructions). To respect the assumption that arch_cmpxchg() is fully ordered, we must inject sync instructions above and below our lld/scd loops using the already in place WEAK_REORDERING_BEYOND_LLSC infrastructure.

Otherwise, bad things can happen:

[ 34.054496] CPU 3 Unable to handle kernel paging request at virtual address 0000000000000000, epc == a80000080838e01c, ra == a80000080838dfc4 [ 34.054559] Oops[#1]: [ 34.069561] CPU: 3 UID: 0 PID: 170 Comm: pipe_race Not tainted 7.2.0-rc6-01553-gb73c35220968-dirty #103 VOLUNTARY [ 34.079932] Hardware name: Mobile EyeQ5 MP5 Evaluation board [ 34.085592] $ 0 : 0000000000000000 0000000000000001 0000000000000000 0000000000000000 [ 34.093616] $ 4 : a800000808ee2618 000000000b7a879d 0000000000001000 0000000000000000 [ 34.101638] $ 8 : 0000000000e3f2c9 0000000000000000 a800000808a2a9f8 0000000000000000 [ 34.109660] $12 : a8000008139ffcd8 ffffffff84080018 a80000080837fae0 7878787878787878 [ 34.117682] $16 : a800000807e82940 0000000000001000 0000000000000000 0000000000000000 [ 34.125704] $20 : a800000802920e00 a8000008139ffdf8 a800000802649400 0000000000e3f2c9 [ 34.133726] $24 : 0000000000000006 00000001200406e0 [ 34.141783] $28 : a8000008139fc000 a8000008139ffd10 0000000000e3f2c8 a80000080838dfc4 [ 34.149837] epc : a80000080838e01c anon_pipe_read+0xd4/0x428 [ 34.155697] ra : a80000080838dfc4 anon_pipe_read+0x7c/0x428 [ 34.161549] Status: 140000e3 KX SX UX KERNEL EXL IE [ 34.166551] Cause : 40800408 (ExcCode 02) [ 34.170574] BadVA : 0000000000000000 [ 34.174161] PrId : 0001b028 (MIPS I6500) [ 34.178183] Process pipe_race (pid: 170, threadinfo=000000005ca35720, task=00000000e1013890, tls=000000014ebbb780) [ 34.188568] Stack : a800000802649400 0000000000000000 0000000000000000 a8000008139ffdd0 [ 34.196623] 0000000000000fba a800000808ee0000 0000000000000001 a8000008130c3e80 [ 34.204676] a8000008080d1280 a8000008139ffd58 a8000008139ffd58 1dbd2b22ea1dd500 [ 34.212729] a800000802649400 a800000808ee0000 ffffffffffffffea 0000000000000001 [ 34.220783] 0000000000001000 0000000000000000 00000001200ae518 ffffffffffffffff [ 34.228836] 000000fffbe0e530 a80000080837edf4 000000fffbe0e530 0000000000000000 [ 34.236890] 0000000000000000 0000000000000000 000000014ebb55a0 0000000000001000 [ 34.244943] 0000000000000001 a800000802649400 0000000000000000 0000000000000000 [ 34.252996] 0000000000000000 0000400400000000 0000000000000000 1dbd2b22ea1dd500 [ 34.261049] 00000000140000e3 a800000802649400 a800000802649400 a800000808ee0000 [ 34.269103] ... [ 34.271568] Call Trace: [ 34.274026] [] anon_pipe_read+0xd4/0x428 [ 34.279533] [] vfs_read+0x25c/0x318 [ 34.284607] [] ksys_read+0x104/0x138 [ 34.289763] [] syscall_common+0x44/0x68 [ 34.295187] [ 34.296689] Code: f84000cf 02209825 de020010 d8400004 02002825 0040f809 02802025 f84000c3 [ 34.306504] [ 34.308099] ---[ end trace 0000000000000000 ]---

My initial reproducer was the xdp-tools test suite. A standalone reproducer would be an lld/scd loop that, when the read is reordered by the CPU, triggers a fault. We can achieve this from userspace by stressing an anonymous pipe, which uses a mutex. Program used:

// SPDX-License-Identifier: GPL-2.0 // pipe_race.c - reproducer for MIPS LL/SC reordering vs fs/pipe.c // // Two userspace processes on an anonymous pipe: // parent = writer: tight write() loop // child = reader: tight read() loop

#define _GNU_SOURCE #include #include #include #include #include #include #include #include #include ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
35
EG Risk 35/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
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
1st
KEV
Not listed

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.

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

October 6, 2026

Last Modified

October 7, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available.
Web page

mips: select CONFIG_WEAK_REORDERING_BEYOND_LLSC from CONFIG_EYEQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bbc448c541ed90d52f9ec22f17394304e3bf170e
Web page

mips: select CONFIG_WEAK_REORDERING_BEYOND_LLSC from CONFIG_EYEQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f017c2ca8c31a1e135dd87be647096866d6b196

Vendor Advisories for CVE-2026-98228(1)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.8-1: fixed in 7.2.8-1
—

Data Freshness Timeline

(refreshed 29× in last 7d / 39× 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.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-13 03:58 UTCEG score recompute
  3. 2026-10-13 03:58 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-12 14:38 UTCEG score recompute
  6. 2026-10-12 04:07 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-11 19:10 UTCEG score recompute
  8. 2026-10-11 16:25 UTCEG score recompute
  9. 2026-10-11 16:24 UTCEG score recompute
  10. 2026-10-11 16:24 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-11 13:37 UTCEG score recompute
  13. 2026-10-11 04:46 UTCEG score recompute
  14. 2026-10-11 04:46 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-10 17:04 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-10 05:27 UTCEG score recompute
  18. 2026-10-10 05:27 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-09 17:48 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-09 06:09 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-08 18:31 UTCEG score recompute
  23. 2026-10-08 18:31 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-10-08 06:47 UTCEG score recompute
Show 14 more
  1. 2026-10-08 06:47 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-07 19:09 UTCEG score recompute
  4. 2026-10-07 19:08 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-07 07:29 UTCEG score recompute
  6. 2026-10-07 07:29 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w
  7. 2026-10-07 06:58 UTCEG score recomputeFirst assessed: 7.8 HIGH
  8. 2026-10-07 06:58 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w
  9. 2026-10-07 06:56 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  10. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-06 09:49 UTCGHSA enrichmentGHSA-h7gx-m7h9-c46w
  12. 2026-10-06 09:28 UTCNVD update
  13. 2026-10-06 08:55 UTCEG score recompute
  14. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98228?
CVE-2026-98228 is a high-severity vulnerability; its CVE record was published on October 6, 2026. In the Linux kernel, the following vulnerability has been resolved: mips: select CONFIGWEAKREORDERINGBEYONDLLSC from CONFIG_EYEQ On I6500 CPU cores, lld and scd give no ordering guarantees (same as all other instructions). To respect the assumption that arch_cmpxchg() is fully ordered, we must…
When was the CVE record for CVE-2026-98228 published?
The CVE record for CVE-2026-98228 was published on October 6, 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 October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-98228 actively exploited?
CVE-2026-98228 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98228?
CVE-2026-98228 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98228?
A fix for CVE-2026-98228 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98228 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-98228

Explore →

Is Your Infrastructure Affected by CVE-2026-98228?

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

Book a Demo →Browse All CVEs