VDB

CVE-2022-49872

CVE-2022-49872 PUBLISHED CVSS 7.5 HIGH

net: gso: fix panic on frag_list with mixed head alloc types

Reported by linux · Published May 1, 2025

In the Linux kernel, the following vulnerability has been resolved: net: gso: fix panic on frag_list with mixed head alloc types Since commit 3dcbdb134f32 ("net: gso: Fix skb_segment splat when splitting gso_size mangled skb having linear-headed frag_list"), it is allowed to change gso_size of a GRO packet. However, that commit assumes that "checking the first list_skb member suffices; i.e if either of the list_skb members have non head_frag head, then the first one has too". It turns out this assumption does not hold. We've seen BUG_ON being hit in skb_segment when skbs on the frag_list had differing head_frag with the vmxnet3 driver. This happens because __netdev_alloc_skb and __napi_alloc_skb can return a skb that is page backed or kmalloced depending on the requested size. As the result, the last small skb in the GRO packet can be kmalloced. There are three different locations where this can be fixed: (1) We could check head_frag in GRO and not allow GROing skbs with different head_frag. However, that would lead to performance regression on normal forward paths with unmodified gso_size, where !head_frag in the last packet is not a problem. (2) Set a flag in bpf_skb_net_grow and bpf_skb_net_shrink indicating that NETIF_F_SG is undesirable. That would need to eat a bit in sk_buff. Furthermore, that flag can be unset when all skbs on the frag_list are page backed. To retain good performance, bpf_skb_net_grow/shrink would have to walk the frag_list. (3) Walk the frag_list in skb_segment when determining whether NETIF_F_SG should be cleared. This of course slows things down. This patch implements (3). To limit the performance impact in skb_segment, the list is walked only for skbs with SKB_GSO_DODGY set that have gso_size changed. Normal paths thus will not hit it. We could check only the last skb but since we need to walk the whole list anyway, let's stay on the safe side.

EPSS 0.53% · 44.6th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel-livepatch-4.14.301-224.520Amazon Linux1.0-0.amzn2
perfAmazon Linux4.14.301-224.520.amzn2
linux_kernellinux6.0.9, 5.15.79, 5.10.155, 5.4.225, 5.3, 4.19.267, 4.14.300, 4.9.334
LinuxLinuxad25a115f50800c6847e0d841c5c7992a9f7c1b3, 9e4b7a99a03aefd37ba7bb1f022c8efab5019165, 65ad047fd83502447269fda8fd26c99077a9af47, 5876b7f249a1ecbbcc8e35072c3828d6526d1c3a, 50868de7dc4e7f0fcadd6029f32bf4387c102ee6, 0a9f56e525ea871d3950b90076912f5c7494f00f

Risk scores

CVSS 3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score
0.53%
44.6th percentile

Affected products

VendorProductVersions
LinuxLinux162a5a8c3aff15c449e6b38355cdf80ab4f77a5a, 55fb612bef7fd237fb70068e2b6ff1cd1543a8ef, 821302dd0c51d29269ef73a595bdff294419e2cd
LinuxLinux5.3, 0, 4.9.334
amazon:2kernel-livepatch-4.14.301-224.5200
amazon:2perf0
LinuxLinux5.2.16, 0, 4.9.334
amazon:2kernel-tools0
amazon:2kernel-headers0
amazon:2kernel0
linuxlinux_kernel5.3, 5.2.16, 4.19.74
amazon:2python-perf0
amazon:2kernel-devel0
amazon:2kernel-tools-devel0

Timeline

  • May 1, 2025 CVE Published
  • May 2, 2025 EPSS Score (30 in total, the first dated here)
  • May 23, 2026 Coalition ESS Score
  • Jun 2, 2026 Security Advisory
  • Aug 4, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2022-49872
vulnetix vdb fixes CVE-2022-49872

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-49872/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›