net: skbuff: don't touch shared zerocopy state in skb_tx_error()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 25121173f7b1e4ac3fc692df6e7b8c52ec36abba · < 288f9970670841044ab030104fa6b6ed159949d0| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: skbuff: don't touch shared zerocopy state in skb_tx_error()
skb_tx_error() completes the zerocopy uarg and clears SKBFL_ALL_ZEROCOPY, and skb_zcopy_downgrade_managed() clears SKBFL_MANAGED_FRAG_REFS. Both live in skb_shinfo(), which every clone shares, while the caller only owns the reference it is about to drop. Through a clone it tells the producer its pages are free and drops SKBFL_SHARED_FRAG for an skb that is still in flight.
Open vSwitch reaches this with a non-last OVS_ACTION_ATTR_RECIRC: clone_execute() sends a skb_clone() into ovs_dp_process_packet() while do_execute_actions() keeps forwarding the original, and skb_clone() does not privatise the frags here -- skb_orphan_frags() returns early on SKBFL_DONT_ORPHAN. A flow miss on the clone then strips the marker from the packet still being forwarded, and a later local ESP delivery decrypts in place over frags it does not own privately.
Skip it for a cloned skb. Nothing is lost: skb_release_data() clears the zerocopy state once the last reference to the shared data goes.
From the CVE record · Linux
In the Linux kernel, skb_tx_error() can change zerocopy state shared with another packet clone, making fragments still in flight appear safe to reuse. This can occur when an Open vSwitch recirculation clone encounters a flow miss and the original packet is later delivered locally through ESP, which may decrypt in place over fragments it does not privately own. The input does not specify attacker access or authentication requirements.
Engineers running Linux kernels with Open vSwitch packet recirculation should check their kernel; affected versions are not specified.