CVE-2024-35789 — wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes
In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes When moving a station out of a VLAN and deleting the VLAN afterwards, the fast_rx entry still holds a pointer to the VLAN's netdev, which can cause use-after-free bugs. Fix this by immediately calling ieee80211_check_fast_rx after the VLAN change.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+4
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 10.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux |
version 22bc2a4814440c4a8979a381f46fec5d224f5c11≥ cc413b375c6d95e68a4629cb1ba9d099de78ebb9 and < e8b067c4058c0121ac8ca71559df8e2e08ff1a7e≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < c8bddbd91bc8e42c961a5e2cec20ab879f21100f≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < 7eeabcea79b67cc29563e6a9a5c81f9e2c664d5b≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < 6b948b54c8bd620725e0c906e44b10c0b13087a7≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < 2884a50f52313a7a911de3afcad065ddbb3d78fc≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < e8678551c0243f799b4859448781cbec1bd6f1cb≥ dd0b45538146cb6a54d6da7663b8c3afd16ebcfd and < 4f2bdb3c5e3189297e156b3ff84b140423d64685 and 9 more≥ bd7e90c82850f49c23004d54de14e46d373748a6 and < be1dd9254fc115321d6fbee042026d42afc8d931version 7cfe824f681e1aaac34ea64bb4def8a77801b672≥ 4.19.189 and < 4.19.312≥ 5.4.114 and < 5.4.274≥ 5.10.32 and < 5.10.215≥ 4.14.232 and < 4.15≥ 5.11.16 and < 5.12version 5.12≥ a7f1721684628b8ae6015bca9a176046ee6f30cc and < ea9a0cfc07a7d3601cc680718d9cff0d6927a921 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 6.9-rc1version 5.12-rc8version 5.12-rc7version 5.12≥ 6.8 and < 6.8.3≥ 6.7 and < 6.7.12≥ 6.2 and < 6.6.24≥ 5.16 and < 6.1.84 and 6 more≥ 5.12.1 and < 5.15.154≥ 5.11.16 and < 5.12≥ 5.10.32 and < 5.10.215≥ 5.4.114 and < 5.4.274≥ 4.19.189 and < 4.19.312≥ 4.14.232 and < 4.15 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.0 | CVSS 3.1 | High | 2.1 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.0 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- 2024
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
14 on the record
- git.kernel.org/stable/c/be1dd9254fc115321d6fbee042026d42afc8d931
- git.kernel.org/stable/c/e8b067c4058c0121ac8ca71559df8e2e08ff1a7e
- git.kernel.org/stable/c/4f2bdb3c5e3189297e156b3ff84b140423d64685
- git.kernel.org/stable/c/ea9a0cfc07a7d3601cc680718d9cff0d6927a921
- git.kernel.org/stable/c/e8678551c0243f799b4859448781cbec1bd6f1cb
- git.kernel.org/stable/c/2884a50f52313a7a911de3afcad065ddbb3d78fc
- git.kernel.org/stable/c/6b948b54c8bd620725e0c906e44b10c0b13087a7
- git.kernel.org/stable/c/7eeabcea79b67cc29563e6a9a5c81f9e2c664d5b
- git.kernel.org/stable/c/c8bddbd91bc8e42c961a5e2cec20ab879f21100f
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- github.com/advisories/GHSA-v4h4-wp66-6q5x
- nvd.nist.gov/vuln/detail/CVE-2024-35789
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html
- cert-portal.siemens.com/productcert/html/ssa-265688.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2024-35789 is "wifi: mac80211: check/clear fast rx for non-4addr sta VLAN changes", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.36% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.