CVE-2026-74464

net: openvswitch: fix skb leak on flow key update failure during ct

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.3 ≤ v < 5.10.2654.3 ≤ v < 5.15.2164.3 ≤ v < 6.1.1834.3 ≤ v < 6.12.1034.3 ≤ v < 6.18.444.3 ≤ v < 6.6.1514.3 ≤ v < 7.1.84.3 ≤ v < 7.24.3ec0d043d05e6e3c0c2fac5de922c800c027c6386
Vendor states this is fixed in 22e0ca88090d89c128078062186b03bb5fdc4f98 (fixed)
Vendor states this is fixed in 393f3c72600ab6721d732a0ab245bc896c5b28fc (fixed)
Vendor states this is fixed in 6cc523eaee72c4e91894136cff64946ae9de2cda (fixed)
Vendor states this is fixed in 736e972f3f8a304158345223ac6e816166a467ce (fixed)
Vendor states this is fixed in b77126b2915900f69f9fcf5d624a77c8e6d50c31 (fixed)
Vendor states this is fixed in bc62e843bc48f933da765ce47079fd992e535794 (fixed)
Vendor states this is fixed in e0ba8eaef2a0d02a7a485e6a7157e47272b65cea (fixed)
Vendor states this is fixed in e84dfaac50aab45ad8c670da43e3aa1f97bd2a41 (fixed)
Vendor states this is fixed in 4.3 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card