CVE-2023-54133: nfp: clean mc addresses in application firmware when closing port
In the Linux kernel, the following vulnerability has been resolved:
nfp: clean mc addresses in application firmware when closing port
When moving devices from one namespace to another, mc addresses are
cleaned in software while not removed from application firmware. Thus
the mc addresses are remained and will cause resource leak.
Now use `__dev_mc_unsync` to clean mc addresses when closing port.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue affects systems using the nfp networking driver. During network namespace moves, multicast addresses are cleared in software but can remain in application firmware, causing a resource leak. The documented impact is availability or stability risk, not data theft. No severity score is provided in the sources.
Executive priority
Treat as a targeted availability issue for specialized Linux networking environments. Prioritize remediation where nfp hardware and network namespaces support production traffic. Broad enterprise emergency action is not supported by the available evidence.
Technical view
The nfp driver failed to remove multicast addresses from application firmware when closing a port after device namespace movement. The kernel fix uses __dev_mc_unsync to clean multicast addresses during port close. Public records list affected Linux kernel versions including 6.2, 6.4.5, and 6.5-era entries.
Likely exposure
Exposure appears limited to Linux hosts using affected kernel versions with the nfp driver and workflows that move devices between network namespaces. Systems without this driver or namespace movement paths are less likely to be affected.
Exploitation context
There is no CISA KEV listing and the provided sources do not report active exploitation. The issue appears to require specific kernel, driver, firmware, and network namespace conditions that lead to firmware resource leakage.
Researcher notes
Public details are limited to kernel commit descriptions and CVE metadata. No CVSS, CWE, proof of exploitation, or broad impact analysis is provided. Validation should focus on patch presence and whether the nfp driver path is in use.
Mitigation direction
Check Linux distribution advisories for CVE-2023-54133 fixes.
Update to a kernel containing the referenced stable commits.
Prioritize affected hosts using the nfp driver in containerized or namespace-heavy environments.
If patching is delayed, reduce unnecessary device namespace moves where operationally feasible.
Validation and detection
Inventory Linux kernel versions on systems using nfp networking.
Confirm whether vendor kernels include the referenced stable fixes.
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-2023-54133 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
3Source 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.
Dec 24, 2025, 13:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.