CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().
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.29% (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 20ceae10623c3b29fdf7609690849475bcdebdb0, 5c0b485a8c6116516f33925b9ce5b6104a6eadfd, 7a67c4e47626e6daccda62888f8b096abb5d3940.
- Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 20ceae10623c3b29fdf7609690849475bcdebdb0, 5c0b485a8c6116516f33925b9ce5b6104a6eadfd, 7a67c4e47626e6daccda62888f8b096abb5d3940 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: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port(). syzkaller triggered the warning [0] in udp_v4_early_demux(). In udp_v[46]_early_demux() and sk_lookup(), we do not touch the refcount of the looked-up sk and use sock_pfree() as skb->destructor, so we check SOCK_RCU_FREE to ensure that the sk is safe to access during the RCU grace period. Currently, SOCK_RCU_FREE is flagged for a bound socket after being put into the hash table. Moreover, the SOCK_RCU_FREE check is done too early in udp_v[46]_early_demux() and sk_lookup(), so there could be a small race window: CPU1 CPU2 ---- ---- udp_v4_early_demux() udp_lib_get_port() | |- hlist_add_head_rcu() |- sk = __udp4_lib_demux_lookup() | |- DEBUG_NET_WARN_ON_ONCE(sk_is_refcounted(sk)); `- sock_set_flag(sk, SOCK_RCU_FREE) We had the same bug in TCP and fixed it in commit 871019b22d1b ("net: set SOCK_RCU_FREE before inserting socket into hashtable"). Let's apply the same fix for UDP. [0]: WARNING: CPU: 0 PID: 11198 at net/ipv4/udp.c:2599 udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599 Modules linked in: CPU: 0 PID: 11198 Comm: syz-executor.1 Not tainted 6.9.0-g93bda33046e7 #13 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014 RIP: 0010:udp_v4_early_demux+0x481/0xb70 net/ipv4/udp.c:2599 Code: c5 7a 15 fe bb 01 00 00 00 44 89 e9 31 ff d3 e3 81 e3 bf ef ff ff 89 de e8 2c 74 15 fe 85 db 0f 85 02 06 00 00 e8 9f 7a 15 fe <0f> 0b e8 98 7a 15 fe 49 8d 7e 60 e8 4f 39 2f fe 49 c7 46 60 20 52 RSP: 0018:ffffc9000ce3fa58 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000000 RCX: ffffffff8318c92c RDX: ffff888036ccde00 RSI: ffffffff8318c2f1 RDI: 0000000000000001 RBP: ffff88805a2dd6e0 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000000 R11: 0001ffffffffffff R12: ffff88805a2dd680 R13: 0000000000000007 R14: ffff88800923f900 R15: ffff88805456004e FS: 00007fc449127640(0000) GS:ffff88807dc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc449126e38 CR3: 000000003de4b002 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000600 PKRU: 55555554 Call Trace: <TASK> ip_rcv_finish_core.constprop.0+0xbdd/0xd20 net/ipv4/ip_input.c:349 ip_rcv_finish+0xda/0x150 net/ipv4/ip_input.c:447 NF_HOOK include/linux/netfilter.h:314 [inline] NF_HOOK include/linux/netfilter.h:308 [inline] ip_rcv+0x16c/0x180 net/ipv4/ip_input.c:569 __netif_receive_skb_one_core+0xb3/0xe0 net/core/dev.c:5624 __netif_receive_skb+0x21/0xd0 net/core/dev.c:5738 netif_receive_skb_internal net/core/dev.c:5824 [inline] netif_receive_skb+0x271/0x300 net/core/dev.c:5884 tun_rx_batched drivers/net/tun.c:1549 [inline] tun_get_user+0x24db/0x2c50 drivers/net/tun.c:2002 tun_chr_write_iter+0x107/0x1a0 drivers/net/tun.c:2048 new_sync_write fs/read_write.c:497 [inline] vfs_write+0x76f/0x8d0 fs/read_write.c:590 ksys_write+0xbf/0x190 fs/read_write.c:643 __do_sys_write fs/read_write.c:655 [inline] __se_sys_write fs/read_write.c:652 [inline] __x64_sys_write+0x41/0x50 fs/read_write.c:652 x64_sys_call+0xe66/0x1990 arch/x86/include/generated/asm/syscalls_64.h:2 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x4b/0x110 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7fc44a68bc1f Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 e9 cf f5 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 3c d0 f5 ff 48 RSP: 002b:00007fc449126c90 EFLAGS: 00000293 ORIG_RAX: 0000000000000001 RAX: ffffffffffffffda RBX: 00000000004bc050 RCX: 00007fc44a68bc1f R ---truncated---
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 22th 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.
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.20affected
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before 7a67c4e47626e6daccda62888f8b096abb5d3940affected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before 9f965684c57c3117cfd2f754dd3270383c529fbaaffected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before ddf516e50bf8a7bc9b3bd8a9831f9c7a8131a32aaffected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before a6db0d3ea6536e7120871e5448b3032570152ec6affected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before c5fd77ca13d657c6e99bf04f0917445e6a80231eaffected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before 20ceae10623c3b29fdf7609690849475bcdebdb0affected · git
- 6acc9b432e6714d72d7d77ec7c27f6f8358d0c71 and later · before 5c0b485a8c6116516f33925b9ce5b6104a6eadfdaffected · git
- before 4.20not affected · semver
- 5.4.280 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.20 and later · before 5.4.280
- linux linux kernel5.5 and later · before 5.10.222
- linux linux kernel5.11 and later · before 5.15.163
- linux linux kernel5.16 and later · before 6.1.100
- linux linux kernel6.2 and later · before 6.6.41
- linux linux kernel6.7 and later · before 6.9.10
- linux linux kernel6.10
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.223-1 | 5.10.223-1 |
| Debian:12 | linux | before 6.1.106-1 | 6.1.106-1 |
| Debian:13 | linux | before 6.9.10-1 | 6.9.10-1 |
| Red Hat:rhel_eus:9.2::appstream | bpftool-debuginfo | before 0:7.0.0-284.95.1.el9_2 | 0:7.0.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debug-devel-matched | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-64k-devel-matched | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debug-devel-matched | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-aarch64 | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-ppc64le | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-s390x | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-debuginfo-common-x86_64 | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-devel-matched | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-doc | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-tools-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-debuginfo | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
| Red Hat:rhel_eus:9.2::appstream | kernel-zfcpdump-devel | before 0:5.14.0-284.95.1.el9_2 | 0:5.14.0-284.95.1.el9_2 |
+55
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-41039Jul 29, 2024 · firmware: cs_dsp: Fix overflow checking of wmfw header31Monitor
- ← EarlierCVE-2024-41040Jul 29, 2024 · net/sched: Fix UAF when resolving a clash28Monitor
- Later →CVE-2024-41042Jul 29, 2024 · netfilter: nf_tables: prefer nft_chain_validate31Monitor
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 | 20ceae10623c3b29fdf7609690849475bcdebdb0 | Vendor (CNA) |
| Linux Linux | 5c0b485a8c6116516f33925b9ce5b6104a6eadfd | Vendor (CNA) |
| Linux Linux | 7a67c4e47626e6daccda62888f8b096abb5d3940 | Vendor (CNA) |
| Linux Linux | 9f965684c57c3117cfd2f754dd3270383c529fba | Vendor (CNA) |
| Linux Linux | a6db0d3ea6536e7120871e5448b3032570152ec6 | Vendor (CNA) |
| Linux Linux | c5fd77ca13d657c6e99bf04f0917445e6a80231e | Vendor (CNA) |
| Linux Linux | ddf516e50bf8a7bc9b3bd8a9831f9c7a8131a32a | Vendor (CNA) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.0.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:5.14.0-284.95.1.el9_2 · Red Hat:rhel_eus:9.2::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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1094 · Jul 30, 2024(Linux Kernel Güncellemesi)
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/5c0b485a8c6116516f33925b9ce5b6104a6eadfd
- git.kernel.org/stable/c/7a67c4e47626e6daccda62888f8b096abb5d3940
- git.kernel.org/stable/c/9f965684c57c3117cfd2f754dd3270383c529fba
- git.kernel.org/stable/c/a6db0d3ea6536e7120871e5448b3032570152ec6
- git.kernel.org/stable/c/c5fd77ca13d657c6e99bf04f0917445e6a80231e
- git.kernel.org/stable/c/ddf516e50bf8a7bc9b3bd8a9831f9c7a8131a32a
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.