In the Linux kernel, the following vulnerability has been resolved:
octeontx2-af: Fix mcam entry resource leak
The teardown sequence in FLR handler returns if no NIX LF
is attached to PF/VF because it indicates that graceful
shutdown of resources already happened. But there is a
chance of all allocated MCAM entries not being freed by
PF/VF. Hence free mcam entries even in case of detached LF.
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel cleanup bug in the octeontx2-af driver. Under a specific teardown path, allocated MCAM entries may not be released. The public record does not provide a CVSS score, confirmed impact beyond resource leakage, or evidence of active exploitation.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency, unless your environment relies on affected OcteonTX2 networking hardware. Absence of severity scoring and exploitation evidence lowers urgency, but kernel resource leaks can still affect reliability.
Technical view
The FLR handler returned early when no NIX LF was attached to a PF/VF, assuming graceful resource shutdown had already occurred. The fix ensures MCAM entries are freed even when the LF is detached, preventing a resource leak in octeontx2-af teardown handling.
Likely exposure
Exposure appears limited to Linux systems running affected kernels with relevant octeontx2-af functionality. The source lists Linux kernel versions as affected and stable kernel commits as fixes, but does not identify distributions, appliances, or downstream package versions.
Exploitation context
The source bundle does not report active exploitation, and KEV is false. It also does not describe attacker prerequisites, triggerability, privilege requirements, or exploit impact beyond the resource leak fixed by the kernel patches.
Researcher notes
The evidence is narrow and code-level. Analysis should focus on FLR teardown paths, PF/VF lifecycle handling, NIX LF detached states, and MCAM allocation cleanup. Do not assume broader impact without driver-specific validation.
Mitigation direction
Update to a kernel containing the referenced stable fixes.
Check Linux distribution advisories for packaged kernel backports.
Prioritize systems using octeontx2-af or related Marvell OcteonTX2 hardware.
Track vendor guidance if running customized or appliance kernels.
Validation and detection
Inventory systems for affected Linux kernel versions.
Confirm whether octeontx2-af support is present or in use.
Verify kernel changelogs include the referenced stable commits.
Retest after kernel update or vendor backport installation.
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-2022-50060 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.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
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.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.