CVE-2026-98375

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (kernel.org) lists Linux versions before 2.6.23 and 7.3-rc7 and later as unaffected. No release containing a fix is confirmed on record.

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

xen/netfront: drop RX packets with a short Ethernet header

handle_incoming_queue() pulls pull_to bytes into the head before calling eth_type_trans(). pull_to is the length of the first RX slot, capped at RX_COPY_THRESHOLD, and that length comes from the backend. Nothing checks it against ETH_HLEN.

If the first slot is shorter than ETH_HLEN and more slots follow, the head ends up shorter than an Ethernet header while skb->len is longer, and eth_type_trans() BUG()s in __skb_pull(). If the whole packet is shorter than ETH_HLEN, eth_type_trans() reads the header past the end of the data instead.

Pull at least ETH_HLEN, and drop the packet if that fails, which also drops packets too short to hold an Ethernet header. This also checks the return value of the pull, which was ignored.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

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 9, 2026

Last Modified

October 11, 2026

References (5)

Vendor Advisories for CVE-2026-98375(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc6-1~exp1 (361 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.3~rc6-1~exp1 (184 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.3~rc6-1~exp1 (184 versions)
  • every version on: no fix on record
—

Data Freshness Timeline

(refreshed 21× in last 7d / 21× 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.2% · 6th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 14:38 UTCEG score recompute
  4. 2026-10-11 19:10 UTCEG score recompute
  5. 2026-10-11 16:24 UTCEG score recompute
  6. 2026-10-11 14:31 UTCGHSA enrichmentGHSA-6q97-4p5q-xv9v
  7. 2026-10-11 14:31 UTCNVD update
  8. 2026-10-11 13:57 UTCGHSA enrichmentGHSA-6q97-4p5q-xv9v
  9. 2026-10-11 13:56 UTCMITRE cvelistV5
  10. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-11 13:37 UTCEG score recompute
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-09 12:32 UTCGHSA enrichmentGHSA-6q97-4p5q-xv9v
  15. 2026-10-09 11:31 UTCGHSA enrichmentGHSA-6q97-4p5q-xv9v
  16. 2026-10-09 11:29 UTCNVD update
  17. 2026-10-09 10:29 UTCGHSA enrichmentGHSA-6q97-4p5q-xv9v
  18. 2026-10-09 10:28 UTCMITRE cvelistV5
  19. 2026-10-09 08:27 UTCNVD update
  20. 2026-10-09 07:34 UTCEG score recompute
  21. 2026-10-09 07:33 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98375?
CVE-2026-98375 is a vulnerability whose severity is not yet rated; its CVE record was published on October 9, 2026. In the Linux kernel, the following vulnerability has been resolved: xen/netfront: drop RX packets with a short Ethernet header handleincomingqueue() pulls pull_to bytes into the head before calling ethtypetrans(). pull_to is the length of the first RX slot, capped at RXCOPYTHRESHOLD, and that…
When was the CVE record for CVE-2026-98375 published?
The CVE record for CVE-2026-98375 was published on October 9, 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 11, 2026; the record at its source may have been updated since.
Is CVE-2026-98375 actively exploited?
CVE-2026-98375 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-98375?
No fix for CVE-2026-98375 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 CVE record's CNA (kernel.org) lists Linux versions before 2.6.23 and 7.3-rc7 and later as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-98375 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-98375

Explore →

Is Your Infrastructure Affected by CVE-2026-98375?

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

Book a Demo →Browse All CVEs