Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-40321: wifi: brcmfmac: fix crash while sending Action Frames in standalone AP Mode

—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 0/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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 3776c685ebe5f43e9060af06872661de55e80b9a, 55f60a72a178909ece4e32987e4c642ba57e1cf4, 64e3175d1c8a3bea02032e7c9d1befd5f43786fa; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.1-1.

Low priority for now. Upgrade to Linux Linux 3776c685ebe5f43e9060af06872661de55e80b9a, 55f60a72a178909ece4e32987e4c642ba57e1cf4, 64e3175d1c8a3bea02032e7c9d1befd5f43786fa; azl3 kernel 6.6.112.1-2 on Azure Linux 3.0 6.6.117.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: brcmfmac: fix crash while sending Action Frames in standalone AP Mode Currently, whenever there is a need to transmit an Action frame, the brcmfmac driver always uses the P2P vif to send the "actframe" IOVAR to firmware. The P2P interfaces were available when wpa_supplicant is managing the wlan interface. However, the P2P interfaces are not created/initialized when only hostapd is managing the wlan interface. And if hostapd receives an ANQP Query REQ Action frame even from an un-associated STA, the brcmfmac driver tries to use an uninitialized P2P vif pointer for sending the IOVAR to firmware. This NULL pointer dereferencing triggers a driver crash. [ 1417.074538] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [...] [ 1417.075188] Hardware name: Raspberry Pi 4 Model B Rev 1.5 (DT) [...] [ 1417.075653] Call trace: [ 1417.075662] brcmf_p2p_send_action_frame+0x23c/0xc58 [brcmfmac] [ 1417.075738] brcmf_cfg80211_mgmt_tx+0x304/0x5c0 [brcmfmac] [ 1417.075810] cfg80211_mlme_mgmt_tx+0x1b0/0x428 [cfg80211] [ 1417.076067] nl80211_tx_mgmt+0x238/0x388 [cfg80211] [ 1417.076281] genl_family_rcv_msg_doit+0xe0/0x158 [ 1417.076302] genl_rcv_msg+0x220/0x2a0 [ 1417.076317] netlink_rcv_skb+0x68/0x140 [ 1417.076330] genl_rcv+0x40/0x60 [ 1417.076343] netlink_unicast+0x330/0x3b8 [ 1417.076357] netlink_sendmsg+0x19c/0x3f8 [ 1417.076370] __sock_sendmsg+0x64/0xc0 [ 1417.076391] ____sys_sendmsg+0x268/0x2a0 [ 1417.076408] ___sys_sendmsg+0xb8/0x118 [ 1417.076427] __sys_sendmsg+0x90/0xf8 [ 1417.076445] __arm64_sys_sendmsg+0x2c/0x40 [ 1417.076465] invoke_syscall+0x50/0x120 [ 1417.076486] el0_svc_common.constprop.0+0x48/0xf0 [ 1417.076506] do_el0_svc+0x24/0x38 [ 1417.076525] el0_svc+0x30/0x100 [ 1417.076548] el0t_64_sync_handler+0x100/0x130 [ 1417.076569] el0t_64_sync+0x190/0x198 [ 1417.076589] Code: f9401e80 aa1603e2 f9403be1 5280e483 (f9400000) Fix this, by always using the vif corresponding to the wdev on which the Action frame Transmission request was initiated by the userspace. This way, even if P2P vif is not available, the IOVAR is sent to firmware on AP vif and the ANQP Query RESP Action frame is transmitted without crashing the driver. Move init_completion() for "send_af_done" from brcmf_p2p_create_p2pdev() to brcmf_p2p_attach(). Because the former function would not get executed when only hostapd is managing wlan interface, and it is not safe to do reinit_completion() later in brcmf_p2p_tx_action_frame(), without any prior init_completion(). And in the brcmf_p2p_tx_action_frame() function, the condition check for P2P Presence response frame is not needed, since the wpa_supplicant is properly sending the P2P Presense Response frame on the P2P-GO vif instead of the P2P-Device vif. [Cc stable]

Published
Dec 8, 2025
Updated
Oct 14, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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.

Follow CVE-2025-40321

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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

    • 3.9affected
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before c863b9c7b4e9af0b7931cb791ec91971a50f1a25affected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before e1fc9afcce9139791260f962541282d47fbb508daffected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before 55f60a72a178909ece4e32987e4c642ba57e1cf4affected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before c2b0f8d3e7358c33d90f0e62765d474f25f26a45affected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before 64e3175d1c8a3bea02032e7c9d1befd5f43786faaffected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before a6eed58249e7d60f856900e682992300f770f64baffected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before dbc7357b6aae686d9404e1dd7e2e6cf92c3a1b5aaffected · git
    • 18e2f61db3b708e0a22ccc403cb6ab2203d6faab and later · before 3776c685ebe5f43e9060af06872661de55e80b9aaffected · git
    • before 3.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40319Dec 8, 2025 · bpf: Sync pending IRQ work before freeing ring buffer
    31Monitor
  • ← EarlierCVE-2025-40320Dec 8, 2025 · smb: client: fix potential cfid UAF in smb2_query_info_compound
    39Monitor
  • Later →CVE-2025-40322Dec 8, 2025 · fbdev: bitblit: bound-check glyph index in bit_putcs*
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3776c685ebe5f43e9060af06872661de55e80b9aVendor (CNA)
Linux Linux55f60a72a178909ece4e32987e4c642ba57e1cf4Vendor (CNA)
Linux Linux64e3175d1c8a3bea02032e7c9d1befd5f43786faVendor (CNA)
Linux Linuxa6eed58249e7d60f856900e682992300f770f64bVendor (CNA)
Linux Linuxc2b0f8d3e7358c33d90f0e62765d474f25f26a45Vendor (CNA)
Linux Linuxc863b9c7b4e9af0b7931cb791ec91971a50f1a25Vendor (CNA)
Linux Linuxdbc7357b6aae686d9404e1dd7e2e6cf92c3a1b5aVendor (CNA)
Linux Linuxe1fc9afcce9139791260f962541282d47fbb508dVendor (CNA)
azl3 kernel 6.6.112.1-2 on Azure Linux 3.06.6.117.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.159-1 · Debian:12Package 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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records