CVE-2024-40942: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: 4.19.317; 5.4.279; 5.10.221; 5.15.162; 6.1.95; 6.6.35; 6.9.6; 6.10 CVE record
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: mesh: Fix leak of mesh_preq_queue objects The hwmp code use objects of type mesh_preq_queue, added to a list in ieee80211_if_mesh, to keep track of mpath we need to resolve. If the mpath gets deleted, ex mesh interface is removed, the entries in that list will never get cleaned. Fix this by flushing all corresponding items of the preq_queue in mesh_path_flush_pending(). This should take care of KASAN reports like this: unreferenced object 0xffff00000668d800 (size 128): comm "kworker/u8:4", pid 67, jiffies 4295419552 (age 1836.444s) hex dump (first 32 bytes): 00 1f 05 09 00 00 ff ff 00 d5 68 06 00 00 ff ff ..........h..... 8e 97 ea eb 3e b8 01 00 00 00 00 00 00 00 00 00 ....>........... …
- weakness
- Not named by the CNA. NVD maps it to CWE-401.
- affected
- Linux
- published ranges
- linux kernel >= 2.6.26 < 4.19.317; linux kernel >= 4.20 < 5.4.279; linux kernel >= 5.5 < 5.10.221; linux kernel >= 5.11 < 5.15.162; and 5 more on the CVE page
- fixed in
- 4.19.317; 5.4.279; 5.10.221; 5.15.162; 6.1.95; 6.6.35; 6.9.6; 6.10
- fixed by package (from OSV advisories)
- Kernel (Linux): 4.19.317; 5.4.279; 5.15.162; 6.1.95; 5.10.221; 6.6.35; 6.9.6 CVE-2024-40942
- assigned by
- Linux
- published
- 2024-07-12
check us git.kernel.org git.kernel.org git.kernel.org git.kernel.org
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 13 Jul 2024 | 0.00044 | |
| 17 Mar 2025 | 0.0016 | scoring model v2025.03.14 |
| 19 Mar 2025 | 0.00218 | |
| 28 Mar 2025 | 0.00231 | |
| 4 Mar 2026 | 0.00015 | |
| 12 May 2026 | 0.00014 | |
| 15 Jun 2026 | 0.00259 | scoring model v2026.06.15 |
| 28 Sep 2026 | 0.00278 |
29 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-28 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: 4.19.317; 5.4.279; 5.10.221; 5.15.162; 6.1.95; 6.6.35; 6.9.6; 6.10. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-40942', '2026-10-30T23:59:59.999999Z', now());