Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a missing error check in the brcmstb USB pinmap driver. If a required platform resource lookup fails, the kernel can dereference a NULL pointer. The public record does not provide CVSS, confirmed impact scope, or evidence of exploitation.
Executive priority
Treat this as a targeted kernel maintenance issue, not an emergency based on available evidence. Prioritize patching where affected kernels and the brcmstb USB pinmap driver are relevant.
Technical view
CVE-2021-47279 fixes brcmstb-usb-pinmap by checking the return value from platform_get_resource(). Without that check, a NULL return can cause a NULL pointer dereference. Sources identify Linux kernel versions around 5.11 through 5.13 and reference two stable kernel commits.
Likely exposure
Exposure appears limited to Linux systems running affected kernels where the brcmstb USB pinmap driver is present or loaded. The source bundle does not identify specific distributions, devices, or deployment patterns.
Exploitation context
No KEV listing is present, and the supplied sources do not claim active exploitation or provide exploit details. The public evidence supports a stability or denial-of-service concern, but not remote exploitation or privilege escalation.
Researcher notes
The record is sparse: no CVSS, no CWE, and no detailed attack preconditions. The safest assessment is source-level NULL pointer dereference fixed upstream, with exposure dependent on driver reachability and kernel build configuration.
Mitigation direction
- Apply Linux kernel or distribution updates containing the referenced stable fixes.
- For custom kernels, backport the NULL return check from the stable commits.
- Check vendor advisories for distribution-specific fixed package versions.
- Prioritize systems that include or load the brcmstb USB pinmap driver.
Validation and detection
- Inventory Linux kernel versions on systems that may use this driver.
- Check whether brcmstb-usb-pinmap is built, available, or loaded.
- Confirm installed kernel includes one of the referenced stable commits or equivalent patch.
- Review kernel logs for USB pinmap driver crashes or NULL pointer dereferences.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2021-47279 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/2147684be1ebdaf845783139b9bc4eba3fecd9e4CVE reference, Linux
- https://git.kernel.org/stable/c/fbf649cd6d64d40c03c5397ecd6b1ae922ba7afcCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.