CVE-2026-98911

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-108867 (ENISA EUVD) · GHSA-2gxg-jvpv-v5rf (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
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.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

dpaa2-switch: fix the error path in dpaa2_switch_rx()

In case of an error in dpaa2_switch_rx(), the dpaa2_switch_free_fd() function is called in order to free the FD. This is incorrect since the dpaa2_switch_free_fd() is intended to be used on Tx frame descriptors, meaning that it expects in the software annotation area of the FD data to find a valid skb pointer on which to call dev_kfree_skb().

Fix this by extracting the dma_unmap_page() from dpaa2_switch_build_linear_skb() directly into the dpaa2_switch_rx() function. This allows us to directly use free_pages() in case of an error before an SKB was created and kfree_skb() afterwards.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
25th
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.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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

October 23, 2026

Last Modified

October 26, 2026

Advisory Details (6)

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

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

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

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/791068c962469af0090e1a1ee63657fb9eef40db
Web page

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74c1c9f5c0c30bbd0c2cf87b6e3507e7ea46c13d
Web page

dpaa2-switch: fix the error path in dpaa2_switch_rx() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/259ad6093204b999d41e7e6d0ad90ef9a71a44ab

Vendor Advisories for CVE-2026-98911(2)

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

Patch Availability(17)

These rows come from Ubuntu. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (57 versions)
  • every version up to 6.1.190-1: fixed in 6.1.190-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Additional Vendor Advisories

(17)

Data Freshness Timeline

(refreshed 11× in last 7d / 42× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-22 12:34 UTCEchelonGraph re-scored
  2. 2026-11-22 12:34 UTCVendor advisory
  3. 2026-11-22 12:34 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-11-18 05:32 UTCEchelonGraph re-scored
  9. 2026-11-18 05:32 UTCVendor advisory
  10. 2026-11-18 05:31 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  19. 2026-11-10 14:13 UTCEchelonGraph re-scored
  20. 2026-11-10 14:13 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  22. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  23. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  24. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  25. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
Show 29 more
  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  2. 2026-11-02 22:57 UTCEchelonGraph re-scored
  3. 2026-11-02 22:57 UTCVendor advisory
  4. 2026-11-02 22:57 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  5. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  6. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  8. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  9. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  10. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  11. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  12. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  13. 2026-10-26 07:26 UTCEchelonGraph re-scored
  14. 2026-10-26 07:26 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-10-26 07:12 UTCEchelonGraph re-scored
  16. 2026-10-26 07:11 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  18. 2026-10-25 13:46 UTCEchelonGraph re-scored
  19. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-24 14:26 UTCEchelonGraph re-scored
  21. 2026-10-24 14:26 UTCVendor advisory
  22. 2026-10-24 14:26 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf
  23. 2026-10-24 14:14 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
  24. 2026-10-24 14:14 UTCVendor advisory
  25. 2026-10-24 14:14 UTCGHSA enrichmentGHSA-2gxg-jvpv-v5rf
  26. 2026-10-24 14:13 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  27. 2026-10-23 12:25 UTCNVD update
  28. 2026-10-23 12:01 UTCEchelonGraph re-scored
  29. 2026-10-23 11:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98911?
CVE-2026-98911 is a high-severity vulnerability; its CVE record was published on October 23, 2026. In the Linux kernel, the following vulnerability has been resolved: dpaa2-switch: fix the error path in dpaa2_switch_rx() In case of an error in dpaa2_switch_rx(), the dpaa2_switch_free_fd() function is called in order to free the FD. This is incorrect since the dpaa2_switch_free_fd() is intended…
When was the CVE record for CVE-2026-98911 published?
The CVE record for CVE-2026-98911 was published on October 23, 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 26, 2026; the record at its source may have been updated since.
Is CVE-2026-98911 actively exploited?
CVE-2026-98911 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98911?
CVE-2026-98911 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98911?
A fix for CVE-2026-98911 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98911 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-98911

Explore →

Is Your Infrastructure Affected by CVE-2026-98911?

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