CVE-2026-98555

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-18. 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-103600 (ENISA EUVD) · GHSA-q422-9435-7hfq (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:

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure

In llc_conn_ac_resend_i_xxx_x_set_0_or_send_rr(), if llc_mac_hdr_init() fails, kfree_skb(skb) is called instead of kfree_skb(nskb). This leaks the newly allocated nskb, reads from the freed skb via LLC_I_GET_NR(pdu), and double-frees skb when llc_conn_state_process() drops its reference.

In llc_sap_action_send_xid_r() and llc_sap_action_send_test_r(), nskb is leaked if llc_mac_hdr_init() returns an error.

Free nskb in all three error paths.

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
24th
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-17). 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 18, 2026

Last Modified

October 24, 2026

Advisory Details (8)

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

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b855b645841b5a04e20339a22bb6d593c9b790d
Web page

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72f9dd522f8d6c5a00be9695c7bb74631eb5069e
Web page

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41dcae82bece9f106b4dff0ee777bba8d157c8a8
Web page

llc: fix skb UAF and leaks on llc_mac_hdr_init() failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/060f827aa3dc47939ee306da715cd6700d129616

Vendor Advisories for CVE-2026-98555(2)

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

Patch Availability(16)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
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
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1, 6.12.111-1~deb12u1
  • every version up to 6.12.113-1~deb12u1: fixed in 6.12.113-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (36 versions)
  • every version up to 6.12.113-1: fixed in 6.12.113-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (184 versions)
  • every version up to 7.2.9-1: fixed in 7.2.9-1
—

Additional Vendor Advisories

(16)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-98555?
CVE-2026-98555 is a high-severity vulnerability; its CVE record was published on October 18, 2026. In the Linux kernel, the following vulnerability has been resolved: llc: fix skb UAF and leaks on llc_mac_hdr_init() failure In llc_conn_ac_resend_i_xxx_x_set_0_or_send_rr(), if llc_mac_hdr_init() fails, kfree_skb(skb) is called instead of kfree_skb(nskb). This leaks the newly allocated nskb, reads…
When was the CVE record for CVE-2026-98555 published?
The CVE record for CVE-2026-98555 was published on October 18, 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 24, 2026; the record at its source may have been updated since.
Is CVE-2026-98555 actively exploited?
CVE-2026-98555 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (24th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98555?
CVE-2026-98555 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-98555?
A fix for CVE-2026-98555 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98555 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-98555

Explore →

Is Your Infrastructure Affected by CVE-2026-98555?

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