BCM5820X: Release of Invalid Pointer or Reference
CVE-2025-25215 is a high-severity release of invalid pointer or reference vulnerability in BCM5820X from Broadcom, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.58% chance of exploitation within 30 days, higher than 85% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update ControlVault3 to 5.15.10.14 or a later version.
- Update ControlVault3 Plus to 6.2.26.36 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Broadcom | BCM5820X | Not specified in the record | Not stated |
| Dell | ControlVault3 | before 5.15.10.14 | 5.15.10.14 |
| Dell | ControlVault3 Plus | before 6.2.26.36 | 6.2.26.36 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (cisco.com).
Official description
An arbitrary free vulnerability exists in the cv_close functionality of Dell ControlVault3 prior to 5.15.10.14 and Dell ControlVault3 Plus prior to 6.2.26.36. A specially crafted ControlVault API call can lead to an arbitrary free. An attacker can forge a fake session to trigger this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Release of Invalid Pointer or Reference
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
How developers prevent this class of flaw
- Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
- When programming in C++, consider using smart pointers provided by the boost library to help correctly and consistently manage memory.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, glibc in Linux provides protection against free of invalid pointers.
More Release of Invalid Pointer or Reference vulnerabilities (CWE-763)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in BCM5820X
- 8.8 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 8.8 High severity
Recent Release of Invalid Pointer or Reference vulnerabilities
- 7.8 High severity
- 9.8 Critical severity
- 7.1 High severity
- 8.8 High severity
- 7.4 High severity
- 8.2 High severity
Spotted an error? Tell us.