CVE-2026-98143

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

accel: ethosu: Don't read the U65 rounding mode as a storage mode

Bits 15:14 of NPU_SET_{IFM,OFM}_PRECISION select the activation storage mode on U85 only. On U65 the same field holds the rounding mode, and the command stream parser has read it as a storage mode since the driver was added.

That went unnoticed while unknown values fell through the switch, but now that they are rejected, every U65 command stream that asks for natural rounding (2) fails CMDSTREAM_BO_CREATE with -EINVAL. Mesa emits it for average pooling, concatenation, split, unpack, strided slice, LUT and argmax, which is 72 failures of the Teflon test suite on an i.MX93. Truncating rounding (1) is misread as well: it picks the two-tile address path and computes a bogus feature map size from tile bases the command stream never set.

Read the field as a storage mode only on the hardware where it is one.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

accel: ethosu: Don't read the U65 rounding mode as a storage mode - kernel/git/stable/linux.git - Linux kernel stable tree

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

accel: ethosu: Don't read the U65 rounding mode as a storage mode - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b08adbda8ea797849e3654ce12cb3856ce6051a

Vendor Advisories for CVE-2026-98143(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 27× 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.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-04 20:58 UTCGHSA enrichment
  3. 2026-10-04 08:10 UTCGHSA enrichment
  4. 2026-10-03 19:22 UTCEG score recompute
  5. 2026-10-03 19:22 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 06:35 UTCEG score recompute
  8. 2026-10-03 06:35 UTCGHSA enrichment
  9. 2026-10-02 17:57 UTCEPSS rescore
  10. 2026-10-02 17:47 UTCGHSA enrichment
  11. 2026-10-02 04:58 UTCEG score recompute
  12. 2026-10-02 04:58 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 16:08 UTCGHSA enrichment
  15. 2026-10-01 03:20 UTCEG score recompute
  16. 2026-10-01 03:20 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 14:33 UTCGHSA enrichment
  19. 2026-09-30 12:38 UTCGHSA enrichment
  20. 2026-09-29 23:49 UTCEG score recompute
  21. 2026-09-29 23:49 UTCGHSA enrichment
  22. 2026-09-29 08:59 UTCEG score recompute
  23. 2026-09-29 08:58 UTCGHSA enrichment
  24. 2026-09-28 20:10 UTCEG score recompute
  25. 2026-09-28 20:10 UTCGHSA enrichment
Show 20 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 07:23 UTCGHSA enrichment
  4. 2026-09-27 18:36 UTCEG score recompute
  5. 2026-09-27 18:36 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 05:48 UTCGHSA enrichment
  8. 2026-09-26 17:01 UTCEG score recompute
  9. 2026-09-26 17:00 UTCGHSA enrichment
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-26 04:11 UTCEG score recompute
  12. 2026-09-26 04:11 UTCGHSA enrichment
  13. 2026-09-25 15:23 UTCEG score recompute
  14. 2026-09-25 15:23 UTCGHSA enrichment
  15. 2026-09-25 14:51 UTCEG score recompute▲ 7.80
  16. 2026-09-25 14:51 UTCGHSA enrichment
  17. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  18. 2026-09-25 11:30 UTCNVD update
  19. 2026-09-25 10:48 UTCEG score recompute
  20. 2026-09-25 10:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98143?
CVE-2026-98143 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: accel: ethosu: Don't read the U65 rounding mode as a storage mode Bits 15:14 of NPUSET{IFM,OFM}_PRECISION select the activation storage mode on U85 only. On U65 the same field holds the rounding mode, and the command stream parser…
When was CVE-2026-98143 disclosed?
CVE-2026-98143 was first published on September 25, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98143 actively exploited?
CVE-2026-98143 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-98143?
CVE-2026-98143 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-98143?
No fix for CVE-2026-98143 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98143 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-98143

Explore →

Is Your Infrastructure Affected by CVE-2026-98143?

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