CVE-2026-80603

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-28. a secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

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

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read

parse_dcc() treats data_end as an inclusive end pointer, but its only caller passes data_limit = ib_ptr + datalen, which points one past the last valid byte.

The newline search loop iterates while tmp <= data_end, so when no newline is present, *tmp is read at tmp == data_end, one byte beyond the region filled by skb_header_pointer().

irc_buffer is kmalloc'd as MAX_SEARCH_SIZE + 1 bytes and datalen is capped at MAX_SEARCH_SIZE, so the stray read does not fault. The byte is uninitialized or stale; if it contains an ASCII digit, simple_strtoul will consume it and produce a wrong DCC IP or port in the conntrack expectation. The extra allocation byte is also a fragile guard: if the cap or allocation size changes, this becomes a real out-of-bounds read.

Change the loop and its post-loop check to use strict less-than, consistent with the caller's exclusive-end convention. Update the function comment accordingly.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (8)

Auto-updated Aug 29, 2026
No patch confirmed yet.
generic

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

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

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/910c33e4a8c046c3cc1fa5a465a4d41a1bb398f1
generic

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/437e0a3854b3a44ec15afa9ab88ec215adf3a2fd
generic

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b70f61f569bb29acb380e6f616a1bbdee15668f
generic

netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2393f0bd7a467ad475598f3a5b9de27ca36e3037

Vendor Advisories for CVE-2026-80603(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 17× 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-08-30 03:11 UTCEG score recompute
  2. 2026-08-30 03:11 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 23:15 UTCGHSA enrichment
  5. 2026-08-29 19:18 UTCGHSA enrichment
  6. 2026-08-29 15:21 UTCGHSA enrichment
  7. 2026-08-29 11:25 UTCEG score recompute
  8. 2026-08-29 11:24 UTCGHSA enrichment
  9. 2026-08-29 07:27 UTCEG score recompute
  10. 2026-08-29 07:27 UTCGHSA enrichment
  11. 2026-08-29 06:37 UTCEG score recompute 9.10
  12. 2026-08-29 06:37 UTCGHSA enrichment
  13. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-28 08:20 UTCNVD update
  16. 2026-08-28 07:37 UTCEG score recompute
  17. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80603?
CVE-2026-80603 is a critical vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nfconntrackirc: fix parse_dcc() off-by-one OOB read parsedcc() treats dataend as an inclusive end pointer, but its only caller passes datalimit = ibptr + datalen, which points one past the last valid byte. The newline…
When was CVE-2026-80603 disclosed?
CVE-2026-80603 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80603 actively exploited?
CVE-2026-80603 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.7% of all scored CVEs.
What is the CVSS score of CVE-2026-80603?
CVE-2026-80603 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-80603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80603, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-80603

Explore →

Is Your Infrastructure Affected by CVE-2026-80603?

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