CVE-2024-41040

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2024-07-29. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 5 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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: 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 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.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.0%
EPSS %ILE
62nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2024

Last Modified

August 5, 2026

References (6)

Vendor Advisories for CVE-2024-41040(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-10-20ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-10-20ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1072.70) @ jammy2026-10-20ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-10-20ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.121.121) @ jammy2026-10-20ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1072.81~20.04.1.49) @ focal2026-10-20ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.121.110) @ jammy2026-10-20ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-10-20ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-10-20ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-10-20ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1067.73~20.04.1) @ focal2026-10-20ubuntu
redhatkernel-rt-0:5.14.0-284.99.1.rt14.384.el9_22025-01-08redhat
redhatkernel-0:5.14.0-284.99.1.el9_22025-01-08redhat
redhatkernel-0:4.18.0-477.75.1.el8_82024-10-15redhat
redhatkernel-0:4.18.0-553.22.1.el8_102024-09-24redhat
redhatkernel-rt-0:4.18.0-553.22.1.rt7.363.el8_102024-09-24redhat
redhatkernel-0:5.14.0-427.35.1.el9_42024-09-11redhat
linuxKernel @ 5.10.222 (fixes >=0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (42 versions)
  • every version up to 5.10.223-1: fixed in 5.10.223-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.99-1 (26 versions)
  • every version up to 6.1.106-1: fixed in 6.1.106-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.10-1: fixed in 6.9.10-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.10-1: fixed in 6.9.10-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 206 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 110 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  3. 2026-10-21 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  4. 2026-10-20 19:32 UTCEG score recompute
  5. 2026-10-20 19:32 UTCVendor advisory
  6. 2026-10-20 19:32 UTCGHSA enrichmentGHSA-g37m-wg3j-xw8v · GitHub severity HIGH · GitHub CVSS 7.0
  7. 2026-10-20 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  8. 2026-10-19 18:25 UTCOSV refresh
  9. 2026-10-19 16:29 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  10. 2026-10-18 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  11. 2026-10-18 07:07 UTCEG score recompute
  12. 2026-10-17 16:31 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  13. 2026-10-16 16:36 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  14. 2026-10-15 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  15. 2026-10-14 16:30 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-10-13 16:30 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  17. 2026-10-12 17:48 UTCEG score recompute
  18. 2026-10-12 16:31 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-10-11 21:13 UTCEG score recompute
  20. 2026-10-11 16:06 UTCEG score recompute
  21. 2026-10-11 13:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  22. 2026-10-10 19:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-10-09 20:05 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-10-08 17:08 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  25. 2026-10-07 23:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 71 more
  1. 2026-10-06 15:15 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  2. 2026-10-05 17:41 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  3. 2026-10-04 23:20 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  4. 2026-10-03 14:24 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-10-01 19:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  6. 2026-09-30 19:50 UTCEG score recompute
  7. 2026-09-30 15:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  8. 2026-09-29 15:17 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  9. 2026-09-28 13:50 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-09-27 13:44 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-09-26 23:42 UTCOSV refresh
  12. 2026-09-26 15:57 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  13. 2026-09-24 14:01 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  14. 2026-09-23 13:46 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  15. 2026-09-22 14:47 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  16. 2026-09-21 20:32 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  17. 2026-09-20 20:14 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  18. 2026-09-19 15:40 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  19. 2026-09-18 19:26 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  20. 2026-09-16 14:06 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  21. 2026-09-16 05:12 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  22. 2026-09-15 03:08 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  23. 2026-09-13 16:45 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  24. 2026-09-12 14:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  25. 2026-09-11 14:51 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  26. 2026-09-11 09:35 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  27. 2026-09-08 21:58 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  28. 2026-09-07 16:00 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  29. 2026-09-07 09:18 UTCOSV refresh
  30. 2026-09-06 13:46 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  31. 2026-09-05 15:27 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  32. 2026-09-04 13:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  33. 2026-09-04 05:05 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  34. 2026-09-02 14:10 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  35. 2026-09-01 13:52 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  36. 2026-08-30 19:16 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  37. 2026-08-28 21:39 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  38. 2026-08-27 14:23 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  39. 2026-08-25 13:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  40. 2026-08-24 14:15 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  41. 2026-08-23 00:18 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  42. 2026-08-21 23:47 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  43. 2026-08-20 22:54 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  44. 2026-08-20 18:31 UTCOSV refresh
  45. 2026-08-19 17:02 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  46. 2026-08-18 13:46 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  47. 2026-08-16 14:54 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  48. 2026-08-16 02:13 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  49. 2026-08-15 01:28 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  50. 2026-08-13 21:59 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  51. 2026-08-12 13:49 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  52. 2026-08-11 13:40 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  53. 2026-08-10 23:58 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  54. 2026-08-09 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  55. 2026-08-08 16:35 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  56. 2026-08-07 16:25 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  57. 2026-08-06 13:45 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  58. 2026-08-05 19:16 UTCEPSS rescoreEPSS 1.0% · 59th percentile
  59. 2026-08-05 12:08 UTCEG score recompute
  60. 2026-08-05 12:08 UTCVendor advisory
  61. 2026-08-05 12:08 UTCGHSA enrichmentGHSA-g37m-wg3j-xw8v · GitHub severity HIGH · GitHub CVSS 7.0
  62. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-08-04 11:59 UTCEG score recompute
  64. 2026-08-04 11:59 UTCVendor advisory
  65. 2026-08-04 11:59 UTCGHSA enrichmentGHSA-g37m-wg3j-xw8v · GitHub severity HIGH · GitHub CVSS 7.0
  66. 2026-08-04 10:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  67. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  68. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  69. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  70. 2026-07-31 06:12 UTCOSV refresh
  71. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-41040?
CVE-2024-41040 is a high-severity vulnerability; its CVE record was published on July 29, 2024. 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 tcfctflowtableprocessconn+0x12b/0x380 [actct] Read of size 1 at addr ffff888c07603600 by task handler130/6469 Call Trace:…
When was the CVE record for CVE-2024-41040 published?
The CVE record for CVE-2024-41040 was published on July 29, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-41040 actively exploited?
CVE-2024-41040 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-41040?
CVE-2024-41040 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2024-41040?
A fix for CVE-2024-41040 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-41040 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-41040

Explore →

Is Your Infrastructure Affected by CVE-2024-41040?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs