Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64056net: ethernet: cortina: Make RX SKB per-port

Description

In the Linux kernel, the following vulnerability has been resolved: net: ethernet: cortina: Make RX SKB per-port The SKB used to assemble packets from fragments in gmac_rx() is static local, but the Gemini has two ethernet ports, meaning there can be races between the ports on a bad day if a device is using both. Make the RX SKB a per-port variable and carry it over between invocations in the port struct instead. Zero the pointer once we call napi_gro_frags(), on error (after calling napi_free_frags()) or if the port is stopped. Zero it in some place where not strictly necessary just to emphasize what is going on. This was found by Sashiko during normal patch review.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 17 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64056, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Analyzed3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.55% · top 53% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.8.

Affected products

  • Linux · Linux

    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 27856d533eca3804008695f61c1e4d5ff984196b
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < b6b22824b30e48ce1df3a2e80990f4b8505deb50
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 6bba24e9ebe6f1c0b356cd471e36bdc7fa434897
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 3b249988d774dacf13b203817e971934a42243c4
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 72158ea185b27afae163949b0e86164cb6b64e55
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < cfd62907f3cdbc3b6da8f49ba907c0390018fe5e
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 67a35e7da7ef9d2f000aa758552a128324c604a0
    • affected 4d5ae32f5e1e13f7f36d6439ec3257993b9f5b88 – < 06937db21ee311ed07eba47954447245041a982d
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 5.10.258 – ≤ 5.10.*
    • unaffected 5.15.209 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.142 – ≤ 6.6.*
    • unaffected 6.12.92 – ≤ 6.12.*
    • unaffected 6.18.34 – ≤ 6.18.*
    • unaffected 7.0.11 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64056 badge
[![CVE-2026-64056](https://cveledger.app/badge/CVE-2026-64056.svg)](https://cveledger.app/cve/CVE-2026-64056)

Record last updated .