CVE-2026-90049

CVE CVE-2026-90049EUVD EUVD-2026-80657Published 2026-09-16T10:33:45.000ZLast changed 2026-09-16T14:42:05.000ZCVSS 9.3

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy() skb_zerocopy() copies frags from @from into @to. On an skb_orphan_frags() failure it calls skb_tx_error(@from), a destructive operation on the source skb the copy helper does not own. That completes @from's zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, including the SKBFL_SHARED_FRAG page-ownership marker. Both callers already report the failure on their own drop path. nfnetlink_queue does it at nla_put_failure, and Open vSwitch does it in the flow-miss drop arm of ovs_dp_process_packet(), so nothing is lost by dropping it here. On Open vSwitch's OVS_ACTION_ATTR_USERSPACE path the skb is not freed on this error: do_execute_actions() ignores output_userspace()'s return value and, unless the upcall was the last action, keeps forwarding the same skb through the flow's remaining actions. The uarg is completed while that skb is still in flight, telling the producer its buffers are free, and SKBFL_SHARED_FRAG is cleared on an skb the rest of the stack still handles. That flag is what makes esp_input() call skb_cow_data() instead of decrypting in place, so a later local ESP delivery can decrypt over frags the skb does not own privately. Leave error reporting to the callers.

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 1674b4bf3eea3cac51b70778e89f8025f7cfe695; patch: 0; patch: 7.3-rc1; patch: 7.2.5; 3.10.51 <3.11; 3.12.40 <3.13; 36d5fe6a000790f56039afe26834265db0a3ad4c <8069643ae64dfdf634b6c78c7f622e5323031436; 36d5fe6a000790f56039afe26834265db0a3ad4c <04dd250a78e268af3e7124beb1dc10ec1dd88d60; 36d5fe6a000790f56039afe26834265db0a3ad4c <bab5a851e44a3601d31f2aa8043f385bb50ac5d9; patch: 5.10.270; c5f0c0e7525443add533495e93ba8de6feab2396; 36d5fe6a000790f56039afe26834265db0a3ad4c <fb10e0e9b220a2eed08931a60dbaad9a2370c908; patch: 5.15.221; patch: 6.18.51; 36d5fe6a000790f56039afe26834265db0a3ad4c <a13b1e80e5015cd732440b475c0ef443dc4a2157; 36d5fe6a000790f56039afe26834265db0a3ad4c <767ec2a65cc022d303b0c9c12811e7db22057341; patch: 6.1.188; patch: 6.6.157; 36d5fe6a000790f56039afe26834265db0a3ad4c <849bdb83123760a865bcb2970127f4c0b9423ba3; 3.14; patch: 6.12.110; 36d5fe6a000790f56039afe26834265db0a3ad4c <8ece906150128d5ec2462aabcc978c568433eca4

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.