CVE-2026-74488: wifi: mwifiex: use the subframe length when parsing A-MSDU TDLS frames
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 25e5a3fe4f15e30f74eca42cbf3bcc3a3fbeda79, 3b02275833a0d3e6583627995d614fa99bdf364f, 5a21ab03829cb6d2682c127f22e2b9cd63b4393f; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 25e5a3fe4f15e30f74eca42cbf3bcc3a3fbeda79, 3b02275833a0d3e6583627995d614fa99bdf364f, 5a21ab03829cb6d2682c127f22e2b9cd63b4393f; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: use the subframe length when parsing A-MSDU TDLS frames mwifiex_11n_dispatch_amsdu_pkt() splits an A-MSDU with ieee80211_amsdu_to_8023s() and walks the resulting subframes. For each subframe it passes the subframe data pointer to mwifiex_process_tdls_action_frame(), but pairs it with skb->len, the length of the A-MSDU parent, instead of rx_skb->len: rx_skb = __skb_dequeue(&list); rx_hdr = (struct rx_packet_hdr *)rx_skb->data; if (ISSUPP_TDLS_ENABLED(priv->adapter->fw_cap_info) && ntohs(rx_hdr->eth803_hdr.h_proto) == ETH_P_TDLS) { mwifiex_process_tdls_action_frame(priv, (u8 *)rx_hdr, skb->len); } The parent is not a valid description of that buffer, and may not be valid memory at all. ieee80211_amsdu_to_8023s() ends with if (!reuse_skb) dev_kfree_skb(skb); and it only sets reuse_skb when the parent is linear, is not a head_frag, and is being consumed as the *last* subframe. So when the parent does not qualify for reuse it has already been freed, and the read of skb->len is a use-after-free. When it is reused, skb->len is the length of the last subframe, applied to every earlier subframe, which over-states the buffer whenever an earlier subframe is shorter. The callee cannot absorb a wrong length, because it derives its own ceiling from the value it is given. Each frame type computes ies_len = len - sizeof(struct ethhdr) - TDLS_*_FIX_LEN; and the element walk is then bounded entirely against that ceiling, for (end = pos + ies_len; pos + 1 < end; pos += 2 + pos[1]) { u8 ie_len = pos[1]; if (pos + 2 + ie_len > end) break; so a too-large len moves end past the end of the subframe and the walk reads and copies beyond it. The A-MSDU layout is chosen by the sender, which makes the difference between the last subframe and a shorter earlier one remotely selectable. Reaching this requires TDLS support in firmware and the TDLS ethertype on the subframe. The other caller, mwifiex_process_rx_packet(), is correct: it passes a pointer and a length that describe the same region of the RX buffer. Pass rx_skb->len, the length of the subframe actually being parsed.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.5affected
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before 707664027bb9307f7268eda403af7c4ccd9b8644affected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before 3b02275833a0d3e6583627995d614fa99bdf364faffected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before a1f0f7dc7eb15754e6931b433edb7beb754c996aaffected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before 25e5a3fe4f15e30f74eca42cbf3bcc3a3fbeda79affected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before ece2ebb34247d573142617dfc534a9dc11ba59beaffected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before c9dcfe6b8b71369e1d732e2ff622c3696a2f032caffected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before 5a21ab03829cb6d2682c127f22e2b9cd63b4393faffected · git
- 776f742040ca5eb6242c60f29ac73d5752a5b621 and later · before 99a948382af8a225e2d5e54a7052158cd6281cc6affected · git
- before 4.5not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74486Aug 15, 2026 · binfmt_misc: use exe_file_deny_write_access() for the interpreter clone0Monitor
- ← EarlierCVE-2026-74487Aug 15, 2026 · binfmt_misc: restore write access when removing an entry0Monitor
- Later →CVE-2026-74489Aug 15, 2026 · wifi: mac80211: fix tid_tx use-after-free on BA session stop35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 25e5a3fe4f15e30f74eca42cbf3bcc3a3fbeda79 | Vendor (CNA) |
| Linux Linux | 3b02275833a0d3e6583627995d614fa99bdf364f | Vendor (CNA) |
| Linux Linux | 5a21ab03829cb6d2682c127f22e2b9cd63b4393f | Vendor (CNA) |
| Linux Linux | 707664027bb9307f7268eda403af7c4ccd9b8644 | Vendor (CNA) |
| Linux Linux | 99a948382af8a225e2d5e54a7052158cd6281cc6 | Vendor (CNA) |
| Linux Linux | a1f0f7dc7eb15754e6931b433edb7beb754c996a | Vendor (CNA) |
| Linux Linux | c9dcfe6b8b71369e1d732e2ff622c3696a2f032c | Vendor (CNA) |
| Linux Linux | ece2ebb34247d573142617dfc534a9dc11ba59be | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3b02275833a0d3e6583627995d614fa99bdf364f
- git.kernel.org/stable/c/5a21ab03829cb6d2682c127f22e2b9cd63b4393f
- git.kernel.org/stable/c/707664027bb9307f7268eda403af7c4ccd9b8644
- git.kernel.org/stable/c/99a948382af8a225e2d5e54a7052158cd6281cc6
- git.kernel.org/stable/c/a1f0f7dc7eb15754e6931b433edb7beb754c996a
- git.kernel.org/stable/c/c9dcfe6b8b71369e1d732e2ff622c3696a2f032c
- git.kernel.org/stable/c/ece2ebb34247d573142617dfc534a9dc11ba59be
Vendor advisories and official records. Exploit/PoC links are deliberately left out.