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-74464net: openvswitch: fix skb leak on flow key update failure during ct

Description

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix skb leak on flow key update failure during ct ovs_ct_execute() always steals or frees the skb on failure while ovs_flow_key_update() does not. So, if it fails and we return right away, the skb ends up leaked. Fix that by breaking instead and letting the common error handling code at the bottom of the loop to free the skb properly. This is a very unlikely scenario as it requires the packet to become unparseable by applying a set of actions on a previously parseable skb, but should be fixed nevertheless. Reported by Sashiko.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 3 months 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < b77126b2915900f69f9fcf5d624a77c8e6d50c31
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < 6cc523eaee72c4e91894136cff64946ae9de2cda
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < 22e0ca88090d89c128078062186b03bb5fdc4f98
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < 736e972f3f8a304158345223ac6e816166a467ce
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < e84dfaac50aab45ad8c670da43e3aa1f97bd2a41
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < e0ba8eaef2a0d02a7a485e6a7157e47272b65cea
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < 393f3c72600ab6721d732a0ab245bc896c5b28fc
    • affected ec0d043d05e6e3c0c2fac5de922c800c027c6386 – < bc62e843bc48f933da765ce47079fd992e535794
  • Linux · Linux

    • affected 4.3
    • unaffected < 4.3
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.151 – ≤ 6.6.*
    • unaffected 6.12.103 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .