CVE-2025-21744

wifi: brcmfmac: fix NULL pointer dereference in brcmf_txfinalize()

MEDIUM
5.5
CVSS Score
Published: February 27, 2025 at 02:12 AM UTC
Updated: October 15, 2026 at 02:17 AM UTC
2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix NULL pointer dereference in brcmf_txfinalize() On removal of the device or unloading of the kernel module a potential NULL pointer dereference occurs. The following sequence deletes the interface: brcmf_detach() brcmf_remove_interface() brcmf_del_if() Inside the brcmf_del_if() function the drvr->if2bss[ifidx] is updated to BRCMF_BSSIDX_INVALID (-1) if the bsscfgidx matches. After brcmf_remove_interface() call the brcmf_proto_detach() function is called providing the following sequence: brcmf_detach() brcmf_proto_detach() brcmf_proto_msgbuf_detach() brcmf_flowring_detach() brcmf_msgbuf_delete_flowring() brcmf_msgbuf_remove_flowring() brcmf_flowring_delete() brcmf_get_ifp() brcmf_txfinalize() Since brcmf_get_ip() can and actually will return NULL in this case the call to brcmf_txfinalize() will result in a NULL pointer dereference inside brcmf_txfinalize() when trying to update ifp->ndev->stats.tx_errors. This will only happen if a flowring still has an skb. Although the NULL pointer dereference has only been seen when trying to update the tx statistic, all other uses of the ifp pointer have been guarded as well with an early return if ifp is NULL.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.1.1296.13 ≤ v < 6.13.36.2 ≤ v < 6.6.786.7 ≤ v < 6.12.144.7.104.8.44.96faa698c35a43b9e74ea24e90fe37471d08d00d07f00ee2bbc630900ba16fc2690473f3e2db0e2649119232cc92a269d7860b4aa51f07d3923a3cc10
Vendor states this is fixed in 2326e19190e176fd72bb542b837a9d2b7fcb8693 (fixed)
Vendor states this is fixed in 3877fc67bd3d5566cc12763bce39710ceb74a97d (fixed)
Vendor states this is fixed in 4e51d6d093e763348916e69d06d87e0a5593661b (fixed)
Vendor states this is fixed in 59ff4fa653ff6db07c61152516ffba79c2a74bda (fixed)
Vendor states this is fixed in 61541d9b5a23df33934fcc620a3a81f246b1b240 (fixed)
Vendor states this is fixed in 68abd0c4ebf24cd499841a488b97a6873d5efabb (fixed)
Vendor states this is fixed in a2beefc4fa49ebc22e664dc6b39dbd054f8488f9 (fixed)
Vendor states this is fixed in fbbfef2a5b858eab55741a58b2ac9a0cc8d53c58 (fixed)
Affected range stops below 4.8, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.9 (unaffected)
Vendor states this is fixed in 5.10.235 (unaffected)
Vendor states this is fixed in 5.15.179 (unaffected)
Vendor states this is fixed in 5.4.291 (unaffected)
Vendor states this is fixed in 6.1.129 (unaffected)
Vendor states this is fixed in 6.12.14 (unaffected)
Vendor states this is fixed in 6.13.3 (unaffected)
Vendor states this is fixed in 6.14 (unaffected)
Vendor states this is fixed in 6.6.78 (unaffected)

References (12)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card