CVE-2024-40979

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-07-12. 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-38774 (ENISA EUVD) · GHSA-gvwx-6cpm-mjrj (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:

wifi: ath12k: fix kernel crash during resume

Currently during resume, QMI target memory is not properly handled, resulting in kernel crash in case DMA remap is not supported:

BUG: Bad page state in process kworker/u16:54 pfn:36e80 page: refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x36e80 page dumped because: nonzero _refcount Call Trace: bad_page free_page_is_bad_report __free_pages_ok __free_pages dma_direct_free dma_free_attrs ath12k_qmi_free_target_mem_chunk ath12k_qmi_msg_mem_request_cb

The reason is: Once ath12k module is loaded, firmware sends memory request to host. In case DMA remap not supported, ath12k refuses the first request due to failure in allocating with large segment size:

ath12k_pci 0000:04:00.0: qmi firmware request memory request ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 7077888 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 8454144 ath12k_pci 0000:04:00.0: qmi dma allocation failed (7077888 B type 1), will try later with small size ath12k_pci 0000:04:00.0: qmi delays mem_request 2 ath12k_pci 0000:04:00.0: qmi firmware request memory request

Later firmware comes back with more but small segments and allocation succeeds:

ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 262144 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 524288 ath12k_pci 0000:04:00.0: qmi mem seg type 4 size 65536 ath12k_pci 0000:04:00.0: qmi mem seg type 1 size 524288

Now ath12k is working. If suspend is triggered, firmware will be reloaded during resume. As same as before, firmware requests two large segments at first. In ath12k_qmi_msg_mem_request_cb() segment count and size are assigned:

ab->qmi.mem_seg_count == 2 ab->qmi.target_mem[0].size == 7077888 ab->qmi.target_mem[1].size == 8454144

Then allocation failed like before and ath12k_qmi_free_target_mem_chunk() is called to free all allocated segments. Note the first segment is skipped because its v.addr is cleared due to allocation failure:

chunk->v.addr = dma_alloc_coherent()

Also note that this leaks that segment because it has not been freed.

While freeing the second segment, a size of 8454144 is passed to dma_free_coherent(). However remember that this segment is allocated at the first time firmware is loaded, before suspend. So its real size is 524288, much smaller than 8454144. As a result kernel found we are freeing some memory which is in use and thus cras ---truncated---

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
22nd
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

July 12, 2024

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Oct 3, 2026
Patch available.
Web page

wifi: ath12k: fix kernel crash during resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bb50a4e711ff95348ad53641acb1306d89eb4c3a
Web page

wifi: ath12k: fix kernel crash during resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/303c017821d88ebad887814114d4e5966d320b28
Web page

wifi: ath12k: fix kernel crash during resume - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e323cb55705398123ae087d4870c44e0424e7c0

Vendor Advisories for CVE-2024-40979(2)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-10-24ubuntu
linuxKernel @ 6.9.7 (fixes >=6.3.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

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

Weakness Classification(2)

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

Additional Vendor Advisories

(7)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-40979?
CVE-2024-40979 is a medium-severity vulnerability; its CVE record was published on July 12, 2024. In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix kernel crash during resume Currently during resume, QMI target memory is not properly handled, resulting in kernel crash in case DMA remap is not supported: BUG: Bad page state in process kworker/u16:54 pfn:36e80…
When was the CVE record for CVE-2024-40979 published?
The CVE record for CVE-2024-40979 was published on July 12, 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 3, 2026; the record at its source may have been updated since.
Is CVE-2024-40979 actively exploited?
CVE-2024-40979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-40979?
CVE-2024-40979 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-40979?
A fix for CVE-2024-40979 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-40979 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-40979

Explore →

Is Your Infrastructure Affected by CVE-2024-40979?

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

Book a Demo →Browse All CVEs