CVE-2024-35858: net: bcmasp: fix memory leak when bringing down interface
In the Linux kernel, the following vulnerability has been resolved:
net: bcmasp: fix memory leak when bringing down interface
When bringing down the TX rings we flush the rings but forget to
reclaimed the flushed packets. This leads to a memory leak since we
do not free the dma mapped buffers. This also leads to tx control
block corruption when bringing down the interface for power
management.
Security readout for executives and security teams
Plain-English summary
A flaw in the Linux Broadcom ASP network driver can leave network-packet memory allocated when an interface is shut down. Repeated interface shutdowns, including power-management transitions, may consume memory and corrupt transmit-control data, potentially destabilizing an affected system. The supplied CVSS score is 7.8 (High).
Executive priority
Prioritize affected appliances and embedded systems that use Broadcom ASP networking and frequently enter power-saving states. Remediate through normal high-severity kernel maintenance, escalating systems showing memory exhaustion or network instability. Broad emergency action is not supported because exposure is driver-specific and no active exploitation evidence is supplied.
Technical view
The bcmasp driver flushes TX rings during interface shutdown but fails to reclaim flushed packets and free their DMA-mapped buffers. This causes a memory leak and can corrupt TX control blocks during interface shutdown for power management. Kernel stable commits are supplied as fixes, but the bundled version data is insufficiently structured to establish exact affected and fixed release ranges confidently.
Likely exposure
Exposure appears limited to Linux systems using the bcmasp Broadcom ASP Ethernet driver on an affected kernel. Systems not using this driver are unlikely to reach the vulnerable path. Risk increases where interfaces are repeatedly brought down or undergo power-management transitions. The source bundle's flattened version list is ambiguous, so package-level verification is required.
Exploitation context
The issue requires local, low-privileged access according to the supplied CVSS vector. The bundle provides no evidence of public exploitation or weaponization, and the CVE is not listed as KEV. Treat active exploitation as unconfirmed. Operational triggering through interface shutdown or power management is documented, but reliable security impact beyond the stated memory leak and control-block corruption is not demonstrated.
Researcher notes
The vulnerable lifecycle is TX-ring teardown: flushed packets retain DMA-mapped buffers because reclamation is omitted. The stated secondary effect is TX control-block corruption during power-management shutdown. Three stable-kernel commits are referenced. Exact vulnerable ranges cannot be reconstructed safely from the flattened version fields, and no CWE or exploit evidence is provided.
Mitigation direction
Identify systems running Linux with the bcmasp driver in use.
Apply a vendor-supported kernel containing the referenced stable fix.
Confirm fixed package versions with the operating-system or appliance vendor.
Limit unnecessary interface cycling until remediation where operationally feasible.
Follow vendor guidance if immediate kernel replacement is unavailable.
Validation and detection
Inventory kernel versions and determine whether the bcmasp driver is active.
Compare deployed kernel packages with vendor advisories and referenced fix commits.
Test legitimate interface shutdown and power-management transitions in a controlled environment.
Check for abnormal memory growth or network instability during those tests.
Confirm updated kernels reclaim flushed TX packets without regression.
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-35858 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.
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.