CVE-2026-80840

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-71290 (ENISA EUVD) · GHSA-56f8-x2fw-63m3 (GitHub Security Advisories)Source: ENISA EUVD

—
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

A fix is available — apply it.

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

ipv6: seg6: clear IPv4 control block on IPIP decapsulation

End.DX4 and End.DT4 decapsulate an IPv4 packet through decap_and_validate() and send it directly to IPv4 routing. The inner packet therefore bypasses ip_rcv_core(), which normally clears IPCB before IPv4 interprets skb->cb.

The skb instead retains IP6CB data from the outer packet. IP6CB and IPCB use the same skb->cb storage, so IP6CB(skb)->lastopt overlaps IPCB(skb)->opt.optlen and srr, while IP6CB(skb)->nhoff overlaps rr and ts.

The sender can make the stale optlen byte nonzero with a valid outer extension-header chain. The reproducers put an eight-byte Destination Options header immediately after the 40-byte IPv6 header and before the Segment Routing Header. ipv6_destopt_rcv() records the sender-controlled Destination Options offset in both lastopt and nhoff, setting them to

  • On the reproduced little-endian x86-64 kernel, IPv4 therefore sees
optlen = 40 and rr = 40.

Both tcp_v4_save_options() and __ip_options_echo() skip option copying when optlen is zero. Here optlen is 40, so the TCP SYN path allocates room for 40 bytes of option data and calls __ip_options_echo(). The stale rr value makes that function read inner packet byte 41 as the Record Route option length. The reproducers set that sender-controlled byte to 255, so __ip_options_echo() copies 255 bytes into the 40-byte option-data area.

Separate End.DX4 and End.DT4 reproducers on the unpatched v7.2-rc5 kernel both produced:

BUG: KASAN: slab-out-of-bounds in __ip_options_echo() Write of size 255

The relevant End.DX4 call path is:

__ip_options_echo tcp_v4_route_req tcp_conn_request tcp_v4_conn_request tcp_rcv_state_process tcp_v4_do_rcv tcp_v4_rcv ip_protocol_deliver_rcu ip_local_deliver_finish ip_local_deliver input_action_end_dx4_finish input_action_end_dx4

The relevant End.DT4 call path is:

__ip_options_echo tcp_v4_route_req tcp_conn_request tcp_v4_conn_request tcp_rcv_state_process tcp_v4_do_rcv tcp_v4_rcv ip_protocol_deliver_rcu ip_local_deliver_finish ip_local_deliver input_action_end_dt4

tcp_v4_save_options() is inlined into the tcp_v4_route_req() path, so it does not appear as a separate frame.

When decap_and_validate() handles IPPROTO_IPIP, save the ingress interface from IP6CB, clear IPCB, and restore the saved value. Doing this in the common decapsulation path covers End.DX4, End.DT4, and End.DT46's IPv4 arm.

Use IP6CB(skb)->iif rather than skb->skb_iif. These actions run after l3mdev processing, which can replace skb_iif with the L3 master; IP6CB iif still records the receiving interface set at IPv6 ingress.

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
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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: the BOD 26-04 block below.

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

September 4, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-80840(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
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.1~rc7-1~exp1 (172 versions)
  • every version up to 7.1.13-1: fixed in 7.1.13-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 49× 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.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 84 are merged into the row they repeat.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-25 13:59 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-19 09:25 UTCNVD update
  10. 2026-10-19 09:23 UTCEG score recompute
  11. 2026-10-19 09:23 UTCVendor advisory
  12. 2026-10-19 09:23 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  13. 2026-10-19 08:58 UTCMITRE cvelistV5
  14. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-18 03:09 UTCEG score recompute
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  18. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-12 14:57 UTCEG score recompute
  23. 2026-10-11 19:21 UTCEG score recompute
  24. 2026-10-11 16:37 UTCEG score recompute
  25. 2026-10-11 13:55 UTCEG score recompute
Show 57 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-10 17:19 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  4. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-10-07 23:08 UTCVendor advisory
  8. 2026-10-07 23:07 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  9. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-05 00:07 UTCVendor advisory
  12. 2026-10-05 00:07 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-02 06:00 UTCVendor advisory
  17. 2026-10-02 06:00 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  18. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-29 11:49 UTCEG score recompute
  21. 2026-09-29 11:49 UTCVendor advisory
  22. 2026-09-29 11:49 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-26 17:31 UTCVendor advisory
  26. 2026-09-26 17:31 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  27. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-23 23:25 UTCVendor advisory
  31. 2026-09-23 23:25 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  32. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  33. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  34. 2026-09-21 05:06 UTCVendor advisory
  35. 2026-09-21 05:06 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  36. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  37. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  38. 2026-09-18 10:56 UTCVendor advisory
  39. 2026-09-18 10:56 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  40. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  41. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  42. 2026-09-15 16:50 UTCVendor advisory
  43. 2026-09-15 16:50 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  44. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  45. 2026-09-12 22:45 UTCVendor advisory
  46. 2026-09-12 22:45 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  47. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  48. 2026-09-10 04:39 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  49. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  50. 2026-09-07 10:30 UTCEG score recompute
  51. 2026-09-07 10:30 UTCVendor advisory
  52. 2026-09-07 10:30 UTCGHSA enrichmentGHSA-56f8-x2fw-63m3
  53. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  54. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-09-04 16:22 UTCNVD update
  56. 2026-09-04 16:05 UTCEG score recompute
  57. 2026-09-04 16:04 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80840?
CVE-2026-80840 is a vulnerability whose severity is not yet rated; its CVE record was published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: ipv6: seg6: clear IPv4 control block on IPIP decapsulation End.DX4 and End.DT4 decapsulate an IPv4 packet through decapandvalidate() and send it directly to IPv4 routing. The inner packet therefore bypasses iprcvcore(), which…
When was the CVE record for CVE-2026-80840 published?
The CVE record for CVE-2026-80840 was published on September 4, 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 19, 2026; the record at its source may have been updated since.
Is CVE-2026-80840 actively exploited?
CVE-2026-80840 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80840?
A fix for CVE-2026-80840 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80840 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-80840

Explore →

Is Your Infrastructure Affected by CVE-2026-80840?

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