CVE-2024-42114

MEDIUMNVD 4.45.5
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2024-07-30. NVD baseline CVSS 4.4; sources differ by 1.1.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
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.2%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: cfg80211: restrict NL80211_ATTR_TXQ_QUANTUM values

syzbot is able to trigger softlockups, setting NL80211_ATTR_TXQ_QUANTUM to 2^31.

We had a similar issue in sch_fq, fixed with commit d9e15a273306 ("pkt_sched: fq: do not accept silly TCA_FQ_QUANTUM")

watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [kworker/1:0:24] Modules linked in: irq event stamp: 131135 hardirqs last enabled at (131134): [] __exit_to_kernel_mode arch/arm64/kernel/entry-common.c:85 [inline] hardirqs last enabled at (131134): [] exit_to_kernel_mode+0xdc/0x10c arch/arm64/kernel/entry-common.c:95 hardirqs last disabled at (131135): [] __el1_irq arch/arm64/kernel/entry-common.c:533 [inline] hardirqs last disabled at (131135): [] el1_interrupt+0x24/0x68 arch/arm64/kernel/entry-common.c:551 softirqs last enabled at (125892): [] neigh_hh_init net/core/neighbour.c:1538 [inline] softirqs last enabled at (125892): [] neigh_resolve_output+0x268/0x658 net/core/neighbour.c:1553 softirqs last disabled at (125896): [] local_bh_disable+0x10/0x34 include/linux/bottom_half.h:19 CPU: 1 PID: 24 Comm: kworker/1:0 Not tainted 6.9.0-rc7-syzkaller-gfda5695d692c #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024 Workqueue: mld mld_ifc_work pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __list_del include/linux/list.h:195 [inline] pc : __list_del_entry include/linux/list.h:218 [inline] pc : list_move_tail include/linux/list.h:310 [inline] pc : fq_tin_dequeue include/net/fq_impl.h:112 [inline] pc : ieee80211_tx_dequeue+0x6b8/0x3b4c net/mac80211/tx.c:3854 lr : __list_del_entry include/linux/list.h:218 [inline] lr : list_move_tail include/linux/list.h:310 [inline] lr : fq_tin_dequeue include/net/fq_impl.h:112 [inline] lr : ieee80211_tx_dequeue+0x67c/0x3b4c net/mac80211/tx.c:3854 sp : ffff800093d36700 x29: ffff800093d36a60 x28: ffff800093d36960 x27: dfff800000000000 x26: ffff0000d800ad50 x25: ffff0000d800abe0 x24: ffff0000d800abf0 x23: ffff0000e0032468 x22: ffff0000e00324d4 x21: ffff0000d800abf0 x20: ffff0000d800abf8 x19: ffff0000d800abf0 x18: ffff800093d363c0 x17: 000000000000d476 x16: ffff8000805519dc x15: ffff7000127a6cc8 x14: 1ffff000127a6cc8 x13: 0000000000000004 x12: ffffffffffffffff x11: ffff7000127a6cc8 x10: 0000000000ff0100 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 0000000000000000 x5 : ffff80009287aa08 x4 : 0000000000000008 x3 : ffff80008034c7fc x2 : ffff0000e0032468 x1 : 00000000da0e46b8 x0 : ffff0000e0032470 Call trace: __list_del include/linux/list.h:195 [inline] __list_del_entry include/linux/list.h:218 [inline] list_move_tail include/linux/list.h:310 [inline] fq_tin_dequeue include/net/fq_impl.h:112 [inline] ieee80211_tx_dequeue+0x6b8/0x3b4c net/mac80211/tx.c:3854 wake_tx_push_queue net/mac80211/util.c:294 [inline] ieee80211_handle_wake_tx_queue+0x118/0x274 net/mac80211/util.c:315 drv_wake_tx_queue net/mac80211/driver-ops.h:1350 [inline] schedule_and_wake_txq net/mac80211/driver-ops.h:1357 [inline] ieee80211_queue_skb+0x18e8/0x2244 net/mac80211/tx.c:1664 ieee80211_tx+0x260/0x400 net/mac80211/tx.c:1966 ieee80211_xmit+0x278/0x354 net/mac80211/tx.c:2062 __ieee80211_subif_start_xmit+0xab8/0x122c net/mac80211/tx.c:4338 ieee80211_subif_start_xmit+0xe0/0x438 net/mac80211/tx.c:4532 __netdev_start_xmit include/linux/netdevice.h:4903 [inline] netdev_start_xmit include/linux/netdevice.h:4917 [inline] xmit_one net/core/dev.c:3531 [inline] dev_hard_start_xmit+0x27c/0x938 net/core/dev.c:3547 __dev_queue_xmit+0x1678/0x33fc net/core/dev.c:4341 dev_queue_xmit include/linux/netdevice.h:3091 [inline] neigh_resolve_output+0x558/0x658 net/core/neighbour.c:1563 neigh_output include/net/neighbour.h:542 [inline] ip6_fini ---truncated---

CVSS v3
4.4
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.2% × 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.2%
EPSS %ILE
6th
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.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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 30, 2024

Last Modified

October 15, 2026

Patch Availability(20)

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 (43 versions)
  • every version up to 5.10.226-1: fixed in 5.10.226-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.9-1: fixed in 6.9.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.9-1: fixed in 6.9.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 95 of 212 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. 5 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-42114?
CVE-2024-42114 is a medium-severity vulnerability; its CVE record was published on July 30, 2024. In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: restrict NL80211ATTRTXQ_QUANTUM values syzbot is able to trigger softlockups, setting NL80211ATTRTXQ_QUANTUM to 2^31. We had a similar issue in sch_fq, fixed with commit d9e15a273306 ("pktsched: fq: do not accept…
When was the CVE record for CVE-2024-42114 published?
The CVE record for CVE-2024-42114 was published on July 30, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-42114 actively exploited?
CVE-2024-42114 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-42114?
CVE-2024-42114 has a CVSS v3 base score of 4.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.5 (MEDIUM).
How do I remediate CVE-2024-42114?
A fix for CVE-2024-42114 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-42114 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-42114

Explore →

Is Your Infrastructure Affected by CVE-2024-42114?

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