CVE-2024-26921
Last modified
CVE-2024-26921 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.38% chance of exploitation in the next 30 days.
Description
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, reattach it to the head skb, and fix up wmem accouting when inet_frag inflates truesize.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.1, < 5.4.285 | — |
| Linux | Linux Kernel | >= 5.5, < 5.10.227 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.168 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.85 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.26 | — |
| Linux | Linux Kernel | >= 6.7, < 6.8.5 | — |
| Linux | Linux Kernel | 6.9 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-26921?
How severe is CVE-2024-26921?
How do I fix CVE-2024-26921?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-26916In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26917In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26918In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26919In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-2692SiYuan version 3.0.3 allows executing arbitrary commands on …9
- CVE-2024-26920In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26922In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26923In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2024-26924In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-26925In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26926In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-26927In the Linux kernel, the following vulnerability has been re…8.4
Are you affected by CVE-2024-26921?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
