CVE-2026-97614

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-86745 (ENISA EUVD) · GHSA-3px2-442r-8h6r (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:

net: dsa: tag_brcm: legacy FCS: request needed tailroom

The legacy FCS tagger calculates the CRC over skb->len bytes starting at skb->data. When a nonlinear skb reaches the tagger, this reads past the linear head into unrelated slab memory.

The tagger appends an Ethernet FCS but does not declare that tailroom. As a result, DSA leaves NETIF_F_SG and NETIF_F_FRAGLIST enabled on the user port, and nonlinear skbs can reach the CRC calculation.

Declare the required tailroom. DSA will then clear those features and the networking core will linearize skbs before the tagger runs.

A KASAN-enabled dsa_loop test using this tagger reports:

BUG: KASAN: slab-out-of-bounds in crc32_le Read of size 1 at addr ffff8880397086c0 by task exp/135

Call Trace: crc32_le (lib/crc/crc32-main.c:38) brcm_leg_fcs_tag_xmit (net/dsa/tag_brcm.c:343) dsa_user_xmit (net/dsa/user.c:942) dev_hard_start_xmit (net/core/dev.c:3937) __dev_queue_xmit (net/core/dev.c:4926) packet_sendmsg (net/packet/af_packet.c:3110) __sys_sendto (net/socket.c:2281)

The buggy address belongs to the object at ffff888039708400 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 0 bytes to the right of allocated 704-byte region [ffff888039708400, ffff8880397086c0)

CVSS
—
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
9th
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-11-18). 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, and whom BOD 26-04 binds: 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.

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

September 25, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-97614(2)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-18ubuntu
ubuntulinux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute2026-11-18ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1023.23) @ resolute2026-11-18ubuntu
linuxKernel @ 6.18.53 (fixes >=6.17.0)—osv

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Additional Vendor Advisories

(5)

Data Freshness Timeline

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

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. 1 repeat row among the latest 82 is merged into the row it repeats.

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

Frequently asked(4)

What is CVE-2026-97614?
CVE-2026-97614 is a vulnerability whose severity is not yet rated; its CVE record was published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: dsa: tag_brcm: legacy FCS: request needed tailroom The legacy FCS tagger calculates the CRC over skb->len bytes starting at skb->data. When a nonlinear skb reaches the tagger, this reads past the linear head into unrelated…
When was the CVE record for CVE-2026-97614 published?
The CVE record for CVE-2026-97614 was published on September 25, 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-97614 actively exploited?
CVE-2026-97614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-97614?
A fix for CVE-2026-97614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-97614 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-97614

Explore →

Is Your Infrastructure Affected by CVE-2026-97614?

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