net: gro: don't merge zcopy skbs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 753f1ca4e1e50248a1b760c9774d6d6b354562cc · < 4db79a322db8c97f7b73b8a347395ef4d685eb40| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: gro: don't merge zcopy skbs
skb_gro_receive() can currently copy frags between the source and GRO skb, without checking the zerocopy status, and in particular the SKBFL_MANAGED_FRAG_REFS flag.
When SKBFL_MANAGED_FRAG_REFS is set, the skb doesn't hold a reference on the pages in shinfo->frags. Appending those frags to another skb's frags without fixing up the page refcount can lead to UAF.
When either the last skb in the GRO chain (the one we would append frags to) or the source skb is zerocopy, don't merge the skbs.
From the CVE record · Linux
The Linux kernel’s GRO code can merge zerocopy socket buffers without accounting for page references, potentially causing a use-after-free. The input does not specify how an attacker could trigger this, or whether network access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their installations; affected versions are not specified.