CVE-2024-26921: inet: inet_defrag: prevent sk release while still in use
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.39% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 18685451fc4e546fc0e718580d32df3c0e5c8272, 1b6de5e6575b56502665c65cf93b0ae6aa0f51ab, 4318608dc28ef184158b4045896740716bea23f0.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 18685451fc4e546fc0e718580d32df3c0e5c8272, 1b6de5e6575b56502665c65cf93b0ae6aa0f51ab, 4318608dc28ef184158b4045896740716bea23f0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Apr 18, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.3% · 34th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 7.8
- 2.3 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.1affected
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before 1b6de5e6575b56502665c65cf93b0ae6aa0f51abaffected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before 9705f447bf9a6cd088300ad2c407b5e1c6591091affected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before 4318608dc28ef184158b4045896740716bea23f0affected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before 7d0567842b78390dd9b60f00f1d8f838d540e325affected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before f4877225313d474659ee53150ccc3d553a978727affected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before e09cbe017311508c21e0739e97198a8388b98981affected · git
- 7026b1ddb6b8d4e6ee33dc2bd06c0ca8746fa7ab and later · before 18685451fc4e546fc0e718580d32df3c0e5c8272affected · git
- before 4.1not affected · semver
- 5.4.285 and later · up to and including 5.4.*not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.1 and later · before 5.4.285
- linux linux kernel5.5 and later · before 5.10.227
- linux linux kernel5.11 and later · before 5.15.168
- linux linux kernel5.16 and later · before 6.1.85
- linux linux kernel6.2 and later · before 6.6.26
- linux linux kernel6.7 and later · before 6.8.5
- linux linux kernel6.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.234-1 | 5.10.234-1 |
| Debian:12 | linux | before 6.1.85-1 | 6.1.85-1 |
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-1 |
| Red Hat:rhel_eus:9.4::appstream | bpftool-debuginfo | before 0:7.3.0-427.72.1.el9_4 | 0:7.3.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-64k-devel-matched | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debug-devel-matched | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-devel-matched | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-doc | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debug-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-rt-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
| Red Hat:rhel_eus:9.4::appstream | kernel-tools-debuginfo | before 0:5.14.0-427.72.1.el9_4 | 0:5.14.0-427.72.1.el9_4 |
+57
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-26919Apr 17, 2024 · usb: ulpi: Fix debugfs directory leak22Monitor
- ← EarlierCVE-2024-26920Apr 17, 2024 · tracing/trigger: Fix to return error if failed to alloc snapshot22Monitor
- Later →CVE-2024-26922Apr 23, 2024 · drm/amdgpu: validate the parameters of bo mapping operations more clearly22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 18685451fc4e546fc0e718580d32df3c0e5c8272 | Vendor (CNA) |
| Linux Linux | 1b6de5e6575b56502665c65cf93b0ae6aa0f51ab | Vendor (CNA) |
| Linux Linux | 4318608dc28ef184158b4045896740716bea23f0 | Vendor (CNA) |
| Linux Linux | 7d0567842b78390dd9b60f00f1d8f838d540e325 | Vendor (CNA) |
| Linux Linux | 9705f447bf9a6cd088300ad2c407b5e1c6591091 | Vendor (CNA) |
| Linux Linux | e09cbe017311508c21e0739e97198a8388b98981 | Vendor (CNA) |
| Linux Linux | f4877225313d474659ee53150ccc3d553a978727 | Vendor (CNA) |
| debian:linux | 6.1.85-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-427.72.1.el9_4 · Red Hat:rhel_eus:9.4::appstream | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1b6de5e6575b56502665c65cf93b0ae6aa0f51ab
- git.kernel.org/stable/c/4318608dc28ef184158b4045896740716bea23f0
- git.kernel.org/stable/c/7d0567842b78390dd9b60f00f1d8f838d540e325
- git.kernel.org/stable/c/9705f447bf9a6cd088300ad2c407b5e1c6591091
- git.kernel.org/stable/c/e09cbe017311508c21e0739e97198a8388b98981
- git.kernel.org/stable/c/f4877225313d474659ee53150ccc3d553a978727
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.