CVE-2024-41040: net/sched: Fix UAF when resolving a clash
Noroxi assessment
Priority: Monitor (action score 28/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: 1% (FIRST EPSS); higher than 63.3% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 26488172b0292bed837b95a006a3f3431d1898c3, 2b4d68df3f57ea746c430941ba9c03d7d8b5a23f, 4e71b10a100861fb27d9c5755dfd68f615629fae.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.0.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 26488172b0292bed837b95a006a3f3431d1898c3, 2b4d68df3f57ea746c430941ba9c03d7d8b5a23f, 4e71b10a100861fb27d9c5755dfd68f615629fae 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: net/sched: Fix UAF when resolving a clash KASAN reports the following UAF: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr ffff888c07603600 by task handler130/6469 Call Trace: <IRQ> dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 </IRQ> <TASK> asm_common_interrupt+0x27/0x40 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 ____kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack] tcf_ct_act+0x12ad/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 The ct may be dropped if a clash has been resolved but is still passed to the tcf_ct_flow_table_process_conn function for further usage. This issue can be fixed by retrieving ct from skb again after confirming conntrack.
- Published
- Jul 29, 2024
- Updated
- Aug 5, 2026
- EPSS
- 1.0% · 63th percentile
- CWE
- CWE-416
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 9.8
- 2.8 point gap
CVSS:3.1/AV:N/AC:L/PR:N/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
- 30822781c89943b6a3ed122324ceb37cea7042a3, 5.13affected
- f07c548314776231f0d47d73ec6caa5b17e876e8 and later · before b81a523d54ea689414f67c9fb81a5b917a41ed55affected · git
- 0cc254e5aa37cf05f65bcdcdc0ac5c58010feb33 and later · before 2b4d68df3f57ea746c430941ba9c03d7d8b5a23faffected · git
- 0cc254e5aa37cf05f65bcdcdc0ac5c58010feb33 and later · before 4e71b10a100861fb27d9c5755dfd68f615629faeaffected · git
- 0cc254e5aa37cf05f65bcdcdc0ac5c58010feb33 and later · before 799a34901b634008db4a7ece3900e2b971d4c932affected · git
- 0cc254e5aa37cf05f65bcdcdc0ac5c58010feb33 and later · before ef472cc6693b16b202a916482df72f35d94bd69eaffected · git
- 0cc254e5aa37cf05f65bcdcdc0ac5c58010feb33 and later · before 26488172b0292bed837b95a006a3f3431d1898c3affected · git
- 5.10.43 and later · before 5.10.222affected · semver
- 5.12.10 and later · before 5.13affected · semver
- before 5.13not affected · semver
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10.43 and later · before 5.10.222
- linux linux kernel5.12.10 and later · before 5.13
- linux linux kernel5.13 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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:9 | bpftool | before 7.3.0-427.35.1.el9_4 | 7.3.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-devel-matched | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-debug-modules-extra | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-devel-matched | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-64k-modules-extra | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-abi-stablelists | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-cross-headers | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-debug | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-debug-core | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-debug-devel-matched | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
| AlmaLinux:9 | kernel-debug-modules | before 5.14.0-427.35.1.el9_4 | 5.14.0-427.35.1.el9_4 |
+96
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-41038Jul 29, 2024 · firmware: cs_dsp: Prevent buffer overrun when processing V2 alg headers22Monitor
- ← EarlierCVE-2024-41039Jul 29, 2024 · firmware: cs_dsp: Fix overflow checking of wmfw header31Monitor
- Later →CVE-2024-41041Jul 29, 2024 · udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().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 | 26488172b0292bed837b95a006a3f3431d1898c3 | Vendor (CNA) |
| Linux Linux | 2b4d68df3f57ea746c430941ba9c03d7d8b5a23f | Vendor (CNA) |
| Linux Linux | 4e71b10a100861fb27d9c5755dfd68f615629fae | Vendor (CNA) |
| Linux Linux | 5.10.222 | Vendor (CNA) |
| Linux Linux | 5.13 | Vendor (CNA) |
| Linux Linux | 799a34901b634008db4a7ece3900e2b971d4c932 | Vendor (CNA) |
| Linux Linux | b81a523d54ea689414f67c9fb81a5b917a41ed55 | Vendor (CNA) |
| Linux Linux | ef472cc6693b16b202a916482df72f35d94bd69e | Vendor (CNA) |
| almalinux:bpftool | 7.3.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 5.14.0-427.35.1.el9_4 · AlmaLinux:9 | Package registry (OSV) |
| debian:linux | 6.1.106-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:7.3.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:5.14.0-427.35.1.el9_4 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
+4
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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);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 (6 more)Show less
- git.kernel.org/stable/c/2b4d68df3f57ea746c430941ba9c03d7d8b5a23f
- git.kernel.org/stable/c/4e71b10a100861fb27d9c5755dfd68f615629fae
- git.kernel.org/stable/c/799a34901b634008db4a7ece3900e2b971d4c932
- git.kernel.org/stable/c/b81a523d54ea689414f67c9fb81a5b917a41ed55
- git.kernel.org/stable/c/ef472cc6693b16b202a916482df72f35d94bd69e
- lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.