CVE-2026-74664

published 22 Aug 2026 · updated 8 Nov 2026

net: openvswitch: reallocate update replies for mismatched IDs

4.4MediumCVSS 4.4EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel bd8ca84d48cd9a4f6fc63df26512c55e1d339927, Kernel 00f987f066e802793a37dd2167459e67cf2cf2ec, Kernel 20751193d83be2e9735d4faee71375691c09cd13 and 12 more.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=74ed7ab9264c54471c7f057409d352052820d750 <bd8ca84d48cd9a4f6fc63df26512c55e1d339927, >=74ed7ab9264c54471c7f057409d352052820d750 <00f987f066e802793a37dd2167459e67cf2cf2ec, >=74ed7ab9264c54471c7f057409d352052820d750 <20751193d83be2e9735d4faee71375691c09cd13, >=74ed7ab9264c54471c7f057409d352052820d750 <23716dd9d8d46a5908536b73dc085e62f2b5c237, >=74ed7ab9264c54471c7f057409d352052820d750 <5d1c224dd914579524a183a514c12b95095d12ce, >=74ed7ab9264c54471c7f057409d352052820d750 <696a0b9435fce9cf4f1e9ba7f6afa6bee96c97fc, >=74ed7ab9264c54471c7f057409d352052820d750 <69f40ccf85074981340847d650a9cbf9adabfbbe, >=74ed7ab9264c54471c7f057409d352052820d750 <87d0c0040b5d4b61de51ae39132c4c46709f2f77, =4.0bd8ca84d48cd9a4f6fc63df26512c55e1d339927, 00f987f066e802793a37dd2167459e67cf2cf2ec, 20751193d83be2e9735d4faee71375691c09cd13, 23716dd9d8d46a5908536b73dc085e62f2b5c237, 5d1c224dd914579524a183a514c12b95095d12ce, 696a0b9435fce9cf4f1e9ba7f6afa6bee96c97fc, 69f40ccf85074981340847d650a9cbf9adabfbbe, 87d0c0040b5d4b61de51ae39132c4c46709f2f77
linux-kernel: Kernel>=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.45, >=6.19.0 <7.1.9, >=6.2.0 <6.6.152, >=6.7.0 <6.12.104, >=4.0.0 <5.10.2655.15.216, 6.1.183, 6.18.45, 7.1.9, 6.6.152, 6.12.104, 5.10.265

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74664 severity on Zeptric[![CVE-2026-74664](https://zeptric.io/badge/cve/CVE-2026-74664.svg)](https://zeptric.io/cve/CVE-2026-74664)