Skip to main content
VulnerabilityPublished Updated

CVE-2026-74464: Linux kernel · net: openvswitch: fix skb leak on flow key update failure during ct

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in e84dfaac50aab45ad8c670da43e3aa1f97bd2a41 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 18:02 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in e84dfaac50aab45ad8c670da43e3aa1f97bd2a41, e0ba8eaef2a0d02a7a485e6a7157e47272b65cea, bc62e843bc48f933da765ce47079fd992e535794 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < e84dfaac50aab45ad8c670da43e3aa1f97bd2a41
Fixed in
  • e84dfaac50aab45ad8c670da43e3aa1f97bd2a41
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < e0ba8eaef2a0d02a7a485e6a7157e47272b65cea
Fixed in
  • e0ba8eaef2a0d02a7a485e6a7157e47272b65cea
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < bc62e843bc48f933da765ce47079fd992e535794
Fixed in
  • bc62e843bc48f933da765ce47079fd992e535794
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < b77126b2915900f69f9fcf5d624a77c8e6d50c31
Fixed in
  • b77126b2915900f69f9fcf5d624a77c8e6d50c31
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < 736e972f3f8a304158345223ac6e816166a467ce
Fixed in
  • 736e972f3f8a304158345223ac6e816166a467ce
LinuxLinuxAffected
  • ≥ ec0d043d05e6e3c0c2fac5de922c800c027c6386, < 393f3c72600ab6721d732a0ab245bc896c5b28fc
Fixed in
  • 393f3c72600ab6721d732a0ab245bc896c5b28fc

AI-suggested

A fix is available and has been applied in the Linux kernel versions identified by the provided commit hashes. Users should update to a Linux kernel version that includes these fixes to prevent the skb leak. No additional mitigation actions are necessary as the issue is resolved by the official patch.

Description

A vulnerability in the Linux kernel's Open vSwitch (OVS) component could cause a socket buffer (skb) memory leak when flow key updates fail during connection tracking (ct). This occurs because ovs_ct_execute() properly frees or steals the skb on failure, but ovs_flow_key_update() does not, leading to leaked memory in rare cases where a packet becomes unparseable after applying certain actions. The issue has been fixed by adjusting error handling to ensure proper skb freeing.

References

Community reviews

Loading reviews…