CVE-2024-49953

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-10-21. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-43632 (ENISA EUVD) · GHSA-8qrg-fxff-9fcm (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice

The km.state is not checked in driver's delayed work. When xfrm_state_check_expire() is called, the state can be reset to XFRM_STATE_EXPIRED, even if it is XFRM_STATE_DEAD already. This happens when xfrm state is deleted, but not freed yet. As __xfrm_state_delete() is called again in xfrm timer, the following crash occurs.

To fix this issue, skip xfrm_state_check_expire() if km.state is not XFRM_STATE_VALID.

Oops: general protection fault, probably for non-canonical address 0xdead000000000108: 0000 [#1] SMP CPU: 5 UID: 0 PID: 7448 Comm: kworker/u102:2 Not tainted 6.11.0-rc2+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 Workqueue: mlx5e_ipsec: eth%d mlx5e_ipsec_handle_sw_limits [mlx5_core] RIP: 0010:__xfrm_state_delete+0x3d/0x1b0 Code: 0f 84 8b 01 00 00 48 89 fd c6 87 c8 00 00 00 05 48 8d bb 40 10 00 00 e8 11 04 1a 00 48 8b 95 b8 00 00 00 48 8b 85 c0 00 00 00 <48> 89 42 08 48 89 10 48 8b 55 10 48 b8 00 01 00 00 00 00 ad de 48 RSP: 0018:ffff88885f945ec8 EFLAGS: 00010246 RAX: dead000000000122 RBX: ffffffff82afa940 RCX: 0000000000000036 RDX: dead000000000100 RSI: 0000000000000000 RDI: ffffffff82afb980 RBP: ffff888109a20340 R08: ffff88885f945ea0 R09: 0000000000000000 R10: 0000000000000000 R11: ffff88885f945ff8 R12: 0000000000000246 R13: ffff888109a20340 R14: ffff88885f95f420 R15: ffff88885f95f400 FS: 0000000000000000(0000) GS:ffff88885f940000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2163102430 CR3: 00000001128d6001 CR4: 0000000000370eb0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ? die_addr+0x33/0x90 ? exc_general_protection+0x1a2/0x390 ? asm_exc_general_protection+0x22/0x30 ? __xfrm_state_delete+0x3d/0x1b0 ? __xfrm_state_delete+0x2f/0x1b0 xfrm_timer_handler+0x174/0x350 ? __xfrm_state_delete+0x1b0/0x1b0 __hrtimer_run_queues+0x121/0x270 hrtimer_run_softirq+0x88/0xd0 handle_softirqs+0xcc/0x270 do_softirq+0x3c/0x50 __local_bh_enable_ip+0x47/0x50 mlx5e_ipsec_handle_sw_limits+0x7d/0x90 [mlx5_core] process_one_work+0x137/0x2d0 worker_thread+0x28d/0x3a0 ? rescuer_thread+0x480/0x480 kthread+0xb8/0xe0 ? kthread_park+0x80/0x80 ret_from_fork+0x2d/0x50 ? kthread_park+0x80/0x80 ret_from_fork_asm+0x11/0x20

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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
0.3%
EPSS %ILE
23rd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

October 21, 2024

Last Modified

November 7, 2024

Vendor Advisories for CVE-2024-49953(1)

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

Patch Availability(15)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.4-1: fixed in 6.11.4-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.11.4-1: fixed in 6.11.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 7× 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 94 of 214 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 120 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-49953?
CVE-2024-49953 is a medium-severity vulnerability; its CVE record was published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix crash caused by calling __xfrm_state_delete() twice The km.state is not checked in driver's delayed work. When xfrm_state_check_expire() is called, the state can be reset to XFRM_STATE_EXPIRED, even if it is…
When was the CVE record for CVE-2024-49953 published?
The CVE record for CVE-2024-49953 was published on October 21, 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 November 7, 2024; the record at its source may have been updated since.
Is CVE-2024-49953 actively exploited?
CVE-2024-49953 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-49953?
CVE-2024-49953 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-49953?
A fix for CVE-2024-49953 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-49953 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-49953

Explore →

Is Your Infrastructure Affected by CVE-2024-49953?

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