CVE-2026-74664

CVE CVE-2026-74664EUVD EUVD-2026-64351Published 2026-08-22T15:32:36.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 74ed7ab9264c54471c7f057409d352052820d750 <5d1c224dd914579524a183a514c12b95095d12ce; patch: 7.2; 74ed7ab9264c54471c7f057409d352052820d750 <23716dd9d8d46a5908536b73dc085e62f2b5c237; 4.0; patch: 0; patch: 6.1.183; 74ed7ab9264c54471c7f057409d352052820d750 <69f40ccf85074981340847d650a9cbf9adabfbbe; 74ed7ab9264c54471c7f057409d352052820d750 <20751193d83be2e9735d4faee71375691c09cd13; patch: 7.1.9; patch: 5.15.216; patch: 6.12.104; patch: 6.18.45; 74ed7ab9264c54471c7f057409d352052820d750 <00f987f066e802793a37dd2167459e67cf2cf2ec; 74ed7ab9264c54471c7f057409d352052820d750 <87d0c0040b5d4b61de51ae39132c4c46709f2f77; patch: 6.6.152; 74ed7ab9264c54471c7f057409d352052820d750 <bd8ca84d48cd9a4f6fc63df26512c55e1d339927; patch: 5.10.265; 74ed7ab9264c54471c7f057409d352052820d750 <696a0b9435fce9cf4f1e9ba7f6afa6bee96c97fc

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.