CVE-2026-74664

net: openvswitch: reallocate update replies for mismatched IDs

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 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: reallocate update replies for mismatched IDs ovs_flow_cmd_new() preallocates the optional reply skb before it takes ovs_mutex and before it knows which existing flow will be updated. That is normally fine because the skb is sized from the request flow identifier. That identifier also becomes the inserted flow's identifier. For updates, however, a request with a UFID may miss the UFID lookup and then fall back to the flow key lookup. That lookup can legitimately find an existing key-identified flow. UFIDs are optional and the flow key is the primary identifier. For echoed replies, ovs_flow_cmd_fill_info() writes the matched flow's identifier, not the request identifier used for the preallocation. A short request UFID can therefore leave too little room for the key identifier. The fill can then fail with -EMSGSIZE and hit the BUG_ON(error < 0) in the update path. Once the update target has been resolved, reallocate the reply skb if the matched flow needs a larger reply than the request identifier allowed. Do this before replacing the actions so the request can still fail cleanly if the rare extra allocation fails.

Affected

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

4.074ed7ab9264c54471c7f057409d352052820d750
Vendor states this is fixed in 00f987f066e802793a37dd2167459e67cf2cf2ec (fixed)
Vendor states this is fixed in 20751193d83be2e9735d4faee71375691c09cd13 (fixed)
Vendor states this is fixed in 23716dd9d8d46a5908536b73dc085e62f2b5c237 (fixed)
Vendor states this is fixed in 5d1c224dd914579524a183a514c12b95095d12ce (fixed)
Vendor states this is fixed in 696a0b9435fce9cf4f1e9ba7f6afa6bee96c97fc (fixed)
Vendor states this is fixed in 69f40ccf85074981340847d650a9cbf9adabfbbe (fixed)
Vendor states this is fixed in 87d0c0040b5d4b61de51ae39132c4c46709f2f77 (fixed)
Vendor states this is fixed in bd8ca84d48cd9a4f6fc63df26512c55e1d339927 (fixed)
Vendor states this is fixed in 4.0 (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.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (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