Answer in brief
CVE-2026-90049 records a Critical severity (CVSS 9.3) vulnerability in net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=36d5fe6a000790f56039afe26834265db0a3ad4c <849bdb83123760a865bcb2970127f4c0b9423ba3 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <fb10e0e9b220a2eed08931a60dbaad9a2370c908 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <767ec2a65cc022d303b0c9c12811e7db22057341 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <8069643ae64dfdf634b6c78c7f622e5323031436 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <04dd250a78e268af3e7124beb1dc10ec1dd88d60 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <a13b1e80e5015cd732440b475c0ef443dc4a2157 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <bab5a851e44a3601d31f2aa8043f385bb50ac5d9 || >=36d5fe6a000790f56039afe26834265db0a3ad4c <8ece906150128d5ec2462aabcc978c568433eca4 || c5f0c0e7525443add533495e93ba8de6feab2396 || 1674b4bf3eea3cac51b70778e89f8025f7cfe695 || >=3.10.51 <3.11 || >=3.12.40 <3.13 | 849bdb83123760a865bcb2970127f4c0b9423ba3, fb10e0e9b220a2eed08931a60dbaad9a2370c908, 767ec2a65cc022d303b0c9c12811e7db22057341, 8069643ae64dfdf634b6c78c7f622e5323031436, 04dd250a78e268af3e7124beb1dc10ec1dd88d60, a13b1e80e5015cd732440b475c0ef443dc4a2157, bab5a851e44a3601d31f2aa8043f385bb50ac5d9, 8ece906150128d5ec2462aabcc978c568433eca4, 3.11, 3.13 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Sep 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.