CVE-2026-43110: wifi: brcmfmac: validate bsscfg indices in IF events
In the Linux kernel, the following vulnerability has been resolved:
wifi: brcmfmac: validate bsscfg indices in IF events
brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr->iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.
Reject IF events whose bsscfg index does not fit in drvr->iflist[]
before indexing the interface array.
[add missing wifi prefix]
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s Broadcom FullMAC Wi-Fi driver allows a firmware-supplied interface identifier to be used outside the intended array bounds. The published CVSS score is 8.8, indicating potentially severe confidentiality, integrity, and availability impact. Systems not using the brcmfmac driver are unlikely to be exposed.
Executive priority
Treat this as a high-priority patching issue for fleets using affected Broadcom Wi-Fi hardware, especially managed endpoints and embedded devices. First establish whether brcmfmac is present; systems without it should not receive the same urgency. No supplied evidence supports emergency incident-response measures for active exploitation.
Technical view
brcmf_fweh_handle_if_event() checks the firmware-provided interface index but did not similarly validate bsscfgidx before indexing drvr->iflist[]. A malformed IF event could therefore cause an out-of-bounds array access. The referenced stable-kernel changes reject events whose bsscfg index exceeds the interface array.
Likely exposure
Exposure is limited to Linux systems using the brcmfmac Broadcom FullMAC wireless driver and a vulnerable kernel build. The supplied version data spans multiple kernel series but is not sufficiently clear to establish precise vulnerable ranges. Distribution kernels may backport fixes, so version numbers alone are unreliable.
Exploitation context
The CVSS vector describes adjacent-network attack reach, low complexity, no privileges, and no user interaction. However, the supplied evidence provides no public exploit details or confirmed active exploitation, and the CVE is not listed as KEV.
Researcher notes
The vulnerable path trusts bsscfgidx independently of the already-validated interface index, creating an array-bounds failure in firmware event handling. No CWE was assigned in the supplied record. Precise affected and fixed ranges remain ambiguous; validate exposure by checking vendor backports or direct inclusion of the relevant stable commit.
Mitigation direction
Install a vendor-supported kernel update containing the applicable referenced stable-kernel fix.
Prioritize wireless endpoints, appliances, and embedded Linux systems loading the brcmfmac driver.
Consult distribution or device-vendor guidance because backports can make kernel version comparisons misleading.
Apply normal network and endpoint monitoring while updates are tested and deployed.
Validation and detection
Inventory systems for loaded or packaged brcmfmac kernel modules and Broadcom FullMAC wireless hardware.
Map each running kernel build to its distribution or device-vendor security advisory.
Verify the vendor kernel includes the applicable referenced bsscfgidx validation change.
After updating, confirm systems boot normally and wireless interfaces connect without driver errors.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43110 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.