CVE-2024-44991: tcp: prevent concurrent execution of tcp_sk_exit_batch
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.24% (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.
- Fixed version: Linux Linux 565d121b69980637f040eb4d84289869cdaabedf, 99580ae890ec8bd98b21a2a9c6668f8f1555b62e, e3d9de3742f4d5c47ae35f888d3023a5b54fcd2f; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5.
Low priority for now. Upgrade to Linux Linux 565d121b69980637f040eb4d84289869cdaabedf, 99580ae890ec8bd98b21a2a9c6668f8f1555b62e, e3d9de3742f4d5c47ae35f888d3023a5b54fcd2f; Azure Linux 3.0 ARM 6.6.51.1-5; Azure Linux 3.0 x64 6.6.51.1-5 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: tcp: prevent concurrent execution of tcp_sk_exit_batch Its possible that two threads call tcp_sk_exit_batch() concurrently, once from the cleanup_net workqueue, once from a task that failed to clone a new netns. In the latter case, error unwinding calls the exit handlers in reverse order for the 'failed' netns. tcp_sk_exit_batch() calls tcp_twsk_purge(). Problem is that since commit b099ce2602d8 ("net: Batch inet_twsk_purge"), this function picks up twsk in any dying netns, not just the one passed in via exit_batch list. This means that the error unwind of setup_net() can "steal" and destroy timewait sockets belonging to the exiting netns. This allows the netns exit worker to proceed to call WARN_ON_ONCE(!refcount_dec_and_test(&net->ipv4.tcp_death_row.tw_refcount)); without the expected 1 -> 0 transition, which then splats. At same time, error unwind path that is also running inet_twsk_purge() will splat as well: WARNING: .. at lib/refcount.c:31 refcount_warn_saturate+0x1ed/0x210 ... refcount_dec include/linux/refcount.h:351 [inline] inet_twsk_kill+0x758/0x9c0 net/ipv4/inet_timewait_sock.c:70 inet_twsk_deschedule_put net/ipv4/inet_timewait_sock.c:221 inet_twsk_purge+0x725/0x890 net/ipv4/inet_timewait_sock.c:304 tcp_sk_exit_batch+0x1c/0x170 net/ipv4/tcp_ipv4.c:3522 ops_exit_list+0x128/0x180 net/core/net_namespace.c:178 setup_net+0x714/0xb40 net/core/net_namespace.c:375 copy_net_ns+0x2f0/0x670 net/core/net_namespace.c:508 create_new_namespaces+0x3ea/0xb10 kernel/nsproxy.c:110 ... because refcount_dec() of tw_refcount unexpectedly dropped to 0. This doesn't seem like an actual bug (no tw sockets got lost and I don't see a use-after-free) but as erroneous trigger of debug check. Add a mutex to force strict ordering: the task that calls tcp_twsk_purge() blocks other task from doing final _dec_and_test before mutex-owner has removed all tw sockets of dying netns.
- Published
- Sep 4, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th 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.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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
- 6.1affected
- e9bd0cca09d13ac2f08d25e195203e42d4ad1ce8 and later · before e3d9de3742f4d5c47ae35f888d3023a5b54fcd2faffected · git
- e9bd0cca09d13ac2f08d25e195203e42d4ad1ce8 and later · before 99580ae890ec8bd98b21a2a9c6668f8f1555b62eaffected · git
- e9bd0cca09d13ac2f08d25e195203e42d4ad1ce8 and later · before f6fd2dbf584a4047ba88d1369ff91c9851261ec1affected · git
- e9bd0cca09d13ac2f08d25e195203e42d4ad1ce8 and later · before 565d121b69980637f040eb4d84289869cdaabedfaffected · git
- before 6.1not affected · semver
- 6.1.107 and later · up to and including 6.1.*not affected · semver
- 6.6.48 and later · up to and including 6.6.*not affected · semver
- 6.10.7 and later · up to and including 6.10.*not affected · semver
- 6.11 and laternot affected · original_commit_for_fix
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1 and later · before 6.1.107
- linux linux kernel6.2 and later · before 6.6.48
- linux linux kernel6.7 and later · before 6.10.7
- linux linux kernel6.11
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.112-1 | 6.1.112-1 |
| Debian:13 | linux | before 6.10.7-1 | 6.10.7-1 |
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-44985Sep 4, 2024 · ipv6: prevent possible UAF in ip6_xmit()31Monitor
- ← EarlierCVE-2024-44988Sep 4, 2024 · net: dsa: mv88e6xxx: Fix out-of-bound access22Monitor
- Later →CVE-2024-44992Sep 4, 2024 · smb/client: avoid possible NULL dereference in cifs_free_subrequest()22Monitor
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 | 565d121b69980637f040eb4d84289869cdaabedf | Vendor (CNA) |
| Linux Linux | 99580ae890ec8bd98b21a2a9c6668f8f1555b62e | Vendor (CNA) |
| Linux Linux | e3d9de3742f4d5c47ae35f888d3023a5b54fcd2f | Vendor (CNA) |
| Linux Linux | f6fd2dbf584a4047ba88d1369ff91c9851261ec1 | Vendor (CNA) |
| Azure Linux 3.0 ARM | 6.6.51.1-5 · kernel | Microsoft (MSRC) |
| Azure Linux 3.0 x64 | 6.6.51.1-5 · kernel | Microsoft (MSRC) |
| debian:linux | 6.1.112-1 · Debian:12 | 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.