CVE-2024-46755

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-09-18. 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-42016 (ENISA EUVD) · GHSA-ch3p-mhx6-fjx9 (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.4%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id()

mwifiex_get_priv_by_id() returns the priv pointer corresponding to the bss_num and bss_type, but without checking if the priv is actually currently in use. Unused priv pointers do not have a wiphy attached to them which can lead to NULL pointer dereferences further down the callstack. Fix this by returning only used priv pointers which have priv->bss_mode set to something else than NL80211_IFTYPE_UNSPECIFIED.

Said NULL pointer dereference happened when an Accesspoint was started with wpa_supplicant -i mlan0 with this config:

network={ ssid="somessid" mode=2 frequency=2412 key_mgmt=WPA-PSK WPA-PSK-SHA256 proto=RSN group=CCMP pairwise=CCMP psk="12345678" }

When waiting for the AP to be established, interrupting wpa_supplicant with and starting it again this happens:

| Unable to handle kernel NULL pointer dereference at virtual address 0000000000000140 | Mem abort info: | ESR = 0x0000000096000004 | EC = 0x25: DABT (current EL), IL = 32 bits | SET = 0, FnV = 0 | EA = 0, S1PTW = 0 | FSC = 0x04: level 0 translation fault | Data abort info: | ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 | CM = 0, WnR = 0, TnD = 0, TagAccess = 0 | GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 | user pgtable: 4k pages, 48-bit VAs, pgdp=0000000046d96000 | [0000000000000140] pgd=0000000000000000, p4d=0000000000000000 | Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP | Modules linked in: caam_jr caamhash_desc spidev caamalg_desc crypto_engine authenc libdes mwifiex_sdio +mwifiex crct10dif_ce cdc_acm onboard_usb_hub fsl_imx8_ddr_perf imx8m_ddrc rtc_ds1307 lm75 rtc_snvs +imx_sdma caam imx8mm_thermal spi_imx error imx_cpufreq_dt fuse ip_tables x_tables ipv6 | CPU: 0 PID: 8 Comm: kworker/0:1 Not tainted 6.9.0-00007-g937242013fce-dirty #18 | Hardware name: somemachine (DT) | Workqueue: events sdio_irq_work | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) | pc : mwifiex_get_cfp+0xd8/0x15c [mwifiex] | lr : mwifiex_get_cfp+0x34/0x15c [mwifiex] | sp : ffff8000818b3a70 | x29: ffff8000818b3a70 x28: ffff000006bfd8a5 x27: 0000000000000004 | x26: 000000000000002c x25: 0000000000001511 x24: 0000000002e86bc9 | x23: ffff000006bfd996 x22: 0000000000000004 x21: ffff000007bec000 | x20: 000000000000002c x19: 0000000000000000 x18: 0000000000000000 | x17: 000000040044ffff x16: 00500072b5503510 x15: ccc283740681e517 | x14: 0201000101006d15 x13: 0000000002e8ff43 x12: 002c01000000ffb1 | x11: 0100000000000000 x10: 02e8ff43002c0100 x9 : 0000ffb100100157 | x8 : ffff000003d20000 x7 : 00000000000002f1 x6 : 00000000ffffe124 | x5 : 0000000000000001 x4 : 0000000000000003 x3 : 0000000000000000 | x2 : 0000000000000000 x1 : 0001000000011001 x0 : 0000000000000000 | Call trace: | mwifiex_get_cfp+0xd8/0x15c [mwifiex] | mwifiex_parse_single_response_buf+0x1d0/0x504 [mwifiex] | mwifiex_handle_event_ext_scan_report+0x19c/0x2f8 [mwifiex] | mwifiex_process_sta_event+0x298/0xf0c [mwifiex] | mwifiex_process_event+0x110/0x238 [mwifiex] | mwifiex_main_process+0x428/0xa44 [mwifiex] | mwifiex_sdio_interrupt+0x64/0x12c [mwifiex_sdio] | process_sdio_pending_irqs+0x64/0x1b8 | sdio_irq_work+0x4c/0x7c | process_one_work+0x148/0x2a0 | worker_thread+0x2fc/0x40c | kthread+0x110/0x114 | ret_from_fork+0x10/0x20 | Code: a94153f3 a8c37bfd d50323bf d65f03c0 (f940a000) | ---[ end trace 0000000000000000 ]---

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.4% × 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.4%
EPSS %ILE
33rd
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.4% within 30 daysSource: FIRST EPSS. 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

September 18, 2024

Last Modified

August 5, 2026

Vendor Advisories for CVE-2024-46755(1)

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

Patch Availability(17)

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.106-1 ... 6.1.99-1 (29 versions)
  • every version up to 6.1.112-1: fixed in 6.1.112-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.11-1: fixed in 6.10.11-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 7× in last 7d / 39× 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 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 116 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.4% · 33rd percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-25 17:01 UTCEG score recompute
  10. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-24 04:38 UTCEG score recompute
  13. 2026-10-24 04:38 UTCVendor advisory
  14. 2026-10-24 04:38 UTCGHSA enrichmentGHSA-ch3p-mhx6-fjx9 · GitHub CVSS 5.5
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-19 17:55 UTCOSV refresh
  20. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-10-18 06:58 UTCEG score recompute
  23. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
Show 71 more
  1. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-10-12 17:44 UTCEG score recompute
  4. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  5. 2026-10-11 21:09 UTCEG score recompute
  6. 2026-10-11 16:02 UTCEG score recompute
  7. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-09-30 19:54 UTCEG score recompute
  18. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-09-26 23:12 UTCOSV refresh
  23. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  27. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  32. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  36. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  39. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  40. 2026-09-07 08:48 UTCOSV refresh
  41. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  43. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  44. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  47. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-08-20 18:31 UTCOSV refresh
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  60. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  63. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  64. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  65. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  66. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  69. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  70. 2026-08-05 12:01 UTCEG score recompute
  71. 2026-08-05 12:01 UTCVendor advisory

Frequently asked(5)

What is CVE-2024-46755?
CVE-2024-46755 is a medium-severity vulnerability; its CVE record was published on September 18, 2024. In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Do not return unused priv in mwifiex_get_priv_by_id() mwifiex_get_priv_by_id() returns the priv pointer corresponding to the bss_num and bss_type, but without checking if the priv is actually currently in use. Unused…
When was the CVE record for CVE-2024-46755 published?
The CVE record for CVE-2024-46755 was published on September 18, 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-46755 actively exploited?
CVE-2024-46755 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-46755?
CVE-2024-46755 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-46755?
A fix for CVE-2024-46755 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-46755 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-46755

Explore →

Is Your Infrastructure Affected by CVE-2024-46755?

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