CVE-2024-50170: net: bcmasp: fix potential memory leak in bcmasp_xmit()
In the Linux kernel, the following vulnerability has been resolved:
net: bcmasp: fix potential memory leak in bcmasp_xmit()
The bcmasp_xmit() returns NETDEV_TX_OK without freeing skb
in case of mapping fails, add dev_kfree_skb() to fix it.
Security readout for executives and security teams
Plain-English summary
A Linux Broadcom ASP network driver can leak packet memory when transmission mapping fails. Repeated failures may consume memory and reduce availability or crash affected systems. The supplied CVSS score is 7.5, driven by availability impact; no confidentiality or integrity impact is identified.
Executive priority
Treat as high priority for exposed or operationally critical devices using bcmasp because successful triggering could exhaust memory and interrupt service. Systems without this driver are unlikely to be exposed. Require evidence of driver use and vendor-fixed kernel deployment before closing remediation.
Technical view
In bcmasp_xmit(), a mapping-failure path returns NETDEV_TX_OK without freeing the socket buffer. The upstream correction adds dev_kfree_skb() on that path, preventing accumulation of leaked packet buffers. The record classifies this as CWE-401.
Likely exposure
Exposure is limited to systems running an affected Linux kernel with the bcmasp network driver present and in use. The bundle identifies affected 6.6-related and 6.11.6/6.12 entries, but its version list is ambiguous; confirm distribution backports rather than relying only on version strings.
Exploitation context
The CVSS vector describes network-reachable, low-complexity availability impact without privileges or user interaction. However, the supplied sources do not establish a practical remote trigger, public exploit, or active exploitation. This CVE is not listed as KEV in the bundle.
Researcher notes
The vulnerable condition is a transmit mapping failure followed by an unfreed skb. The sources establish the faulty path and correction but do not document trigger reliability, leak rate, affected hardware breadth, or exploitation in the wild. Distribution kernels may backport fixes without changing their apparent upstream version.
Mitigation direction
Install a vendor kernel containing the applicable upstream stable fix or documented backport.
Consult the Linux distribution or appliance vendor for exact fixed package versions.
Prioritize internet-facing or availability-critical systems that actively use the bcmasp driver.
If patching is delayed, disable the affected interface or driver where operationally safe and unnecessary.
Validation and detection
Inventory running kernel versions and identify systems using the bcmasp driver.
Confirm the installed kernel contains the relevant fix commit or vendor backport.
Reboot into the corrected kernel after installation and verify the running version.
Monitor affected systems for abnormal memory growth and network-interface instability.
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.
cwe · low confidence lookup
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-401 · source CWE mapping
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.