cbcvebase.
CVE-2024-26921
published 2024-04-18

CVE-2024-26921: In the Linux kernel, the following vulnerability has been resolved: inet: inet_defrag: prevent sk release while still in use ip_local_out() and other functions…

PriorityP424medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.38%
30.8th percentile
In the Linux kernel, the following vulnerability has been resolved: inet: inet_defrag: prevent sk release while still in use ip_local_out() and other functions can pass skb->sk as function argument. If the skb is a fragment and reassembly happens before such function call returns, the sk must not be released. This affects skb fragments reassembled via netfilter or similar modules, e.g. openvswitch or ct_act.c, when run as part of tx pipeline. Eric Dumazet made an initial analysis of this bug. Quoting Eric: Calling ip_defrag() in output path is also implying skb_orphan(), which is buggy because output path relies on sk not disappearing. A relevant old patch about the issue was : 8282f27449bf ("inet: frag: Always orphan skbs inside ip_defrag()") [..] net/ipv4/ip_output.c depends on skb->sk being set, and probably to an inet socket, not an arbitrary one. If we orphan the packet in ipvlan, then downstream things like FQ packet scheduler will not work properly. We need to change ip_defrag() to only use skb_orphan() when really needed, ie whenever frag_list is going to be used. Eric suggested to stash sk in fragment queue and made an initial patch. However there is a problem with this: If skb is refragmented again right after, ip_do_fragment() will copy head->sk to the new fragments, and sets up destructor to sock_wfree. IOW, we have no choice but to fix up sk_wmem accouting to reflect the fully reassembled skb, else wmem will underflow. This change moves the orphan down into the core, to last possible moment. As ip_defrag_offset is aliased with sk_buff->sk member, we must move the offset into the FRAG_CB, else skb->sk gets clobbered. This allows to delay the orphaning long enough to learn if the skb has to be queued or if the skb is completing the reasm queue. In the former case, things work as before, skb is orphaned. This is safe because skb gets queued/stolen and won't continue past reasm engine. In the latter case, we will steal the skb->sk reference,

Affected

36 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.85-1 (bookworm)linux 6.1.85-1 (bookworm)
googlechrome_chrome
linuxlinux
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < 1b6de5e6575b56502665c65cf93b0ae6aa0f51ab1b6de5e6575b56502665c65cf93b0ae6aa0f51ab
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < 9705f447bf9a6cd088300ad2c407b5e1c65910919705f447bf9a6cd088300ad2c407b5e1c6591091
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < 4318608dc28ef184158b4045896740716bea23f04318608dc28ef184158b4045896740716bea23f0
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < 7d0567842b78390dd9b60f00f1d8f838d540e3257d0567842b78390dd9b60f00f1d8f838d540e325
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < f4877225313d474659ee53150ccc3d553a978727f4877225313d474659ee53150ccc3d553a978727
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < e09cbe017311508c21e0739e97198a8388b98981e09cbe017311508c21e0739e97198a8388b98981
linuxlinux>= 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab < 18685451fc4e546fc0e718580d32df3c0e5c827218685451fc4e546fc0e718580d32df3c0e5c8272
linuxlinux_kernel
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.85-16.1.85-1
linuxlinux_kernel>= 0 < 6.8.9-16.8.9-1
linuxlinux_kernel>= 0 < 6.8.9-16.8.9-1
linuxlinux_kernel>= 0 < 5.4.0-193.2135.4.0-193.213
linuxlinux_kernel>= 0 < 5.15.0-119.1295.15.0-119.129
linuxlinux_kernel>= 0 < 6.8.0-38.386.8.0-38.38
linuxlinux_kernel>= 0 < 4.4.0-267.3014.4.0-267.301
linuxlinux_kernel>= 0 < 4.15.0-232.2444.15.0-232.244
linuxlinux_kernel>= 0 < 4.15.0-233.2454.15.0-233.245
linuxlinux_kernel>= 0 < 5.4.0-198.2185.4.0-198.218
linuxlinux_kernel>= 0 < 5.4.0-205.2255.4.0-205.225
linuxlinux_kernel>= 0 < 5.4.0-204.2245.4.0-204.224
linuxlinux_kernel>= 0 < 5.15.0-124.1345.15.0-124.134

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.4HIGH
vendor_ubuntu8.4HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.