In the Linux kernel, the following vulnerability has been resolved:
wifi: brcm80211: handle pmk_op allocation failure
The kzalloc() in brcmf_pmksa_v3_op() will return null if the
physical memory has run out. As a result, if we dereference
the null value, the null pointer dereference bug will happen.
Return -ENOMEM from brcmf_pmksa_v3_op() if kzalloc() fails
for pmk_op.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi driver reliability flaw. If memory allocation fails in the brcm80211 PMKSA handling path, the kernel may dereference a null pointer instead of returning an error, potentially causing a crash. The source bundle provides no CVSS score, no CWE, and no evidence of active exploitation.
Executive priority
Handle through normal kernel patch management, with higher priority for Wi-Fi-enabled Linux devices using the affected driver path. Current evidence supports reliability and denial-of-service concern, not confirmed active exploitation.
Technical view
brcmf_pmksa_v3_op() allocates pmk_op with kzalloc(). Before the fix, an allocation failure could leave pmk_op null and later dereferenced. The resolved behavior is to return -ENOMEM when allocation fails. The affected area is Linux kernel brcm80211 Wi-Fi code across listed kernel versions and related stable commits.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel builds where the brcm80211 Wi-Fi driver path is present or used. The bundle lists Linux kernel versions and stable commits, but does not provide distro-specific package names, configurations, or device inventories.
Exploitation context
The bundle does not cite active exploitation, public exploit activity, or KEV inclusion. The failure condition depends on memory allocation failure, and the sources do not establish attacker control, remote reachability, or practical exploitation requirements.
Researcher notes
The key uncertainty is reachability: sources confirm a null pointer dereference on kzalloc failure, but not how an attacker could induce the condition. Validation should focus on kernel lineage, brcm80211 presence, and whether vendor kernels have backported the stable commits.
Mitigation direction
Update to a kernel version containing the referenced stable fixes.
Check Linux vendor or distribution advisories for packaged kernel backports.
Prioritize devices using the brcm80211 Wi-Fi driver path.
Monitor kernel logs for Wi-Fi driver crashes or allocation failures.
Avoid treating this as exploitable without vendor evidence.
Validation and detection
Inventory Linux kernel versions across affected devices.
Check whether brcm80211 driver components are present or loaded.
Map installed kernels against the referenced stable commit fixes.
Review distribution changelogs for CVE-2024-27048 backports.
Confirm stability after kernel update on Wi-Fi-enabled systems.
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-2024-27048 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.