CVE-2026-23164: rocker: fix memory leak in rocker_world_port_post_fini()
In the Linux kernel, the following vulnerability has been resolved:
rocker: fix memory leak in rocker_world_port_post_fini()
In rocker_world_port_pre_init(), rocker_port->wpriv is allocated with
kzalloc(wops->port_priv_size, GFP_KERNEL). However, in
rocker_world_port_post_fini(), the memory is only freed when
wops->port_post_fini callback is set:
if (!wops->port_post_fini)
return;
wops->port_post_fini(rocker_port);
kfree(rocker_port->wpriv);
Since rocker_ofdpa_ops does not implement port_post_fini callback
(it is NULL), the wpriv memory allocated for each port is never freed
when ports are removed. This leads to a memory leak of
sizeof(struct ofdpa_port) bytes per port on every device removal.
Fix this by always calling kfree(rocker_port->wpriv) regardless of
whether the port_post_fini callback exists.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a memory leak in the rocker network switch driver. When rocker ports are removed, some per-port memory may not be released. Over repeated removals, this could reduce available memory and affect availability. There is no cited evidence of active exploitation or a public exploit.
Executive priority
Low for most organizations. Treat as routine kernel maintenance unless rocker is used in production switching, labs, or environments where repeated device removal could affect availability.
Technical view
rocker_world_port_pre_init() allocates rocker_port->wpriv. rocker_world_port_post_fini() only freed it after calling an optional port_post_fini callback. rocker_ofdpa_ops has that callback set to NULL, causing sizeof(struct ofdpa_port) to leak per port on device removal. Stable kernel commits change cleanup to always kfree rocker_port->wpriv.
Likely exposure
Exposure appears limited to Linux systems using the rocker driver, especially OFDPA-related rocker ports. The source does not indicate broad default exposure, internet-facing attack surface, or affected distributions. Kernel and distribution package status should be checked against vendor advisories.
Exploitation context
The cited sources describe a memory leak triggered by port or device removal paths. They do not claim remote exploitation, privilege escalation, data exposure, or active exploitation. KEV status is false in the provided bundle.
Researcher notes
The record lacks CVSS, CWE, and distribution-specific status. The core bug and fix are clear from kernel commit references, but real-world exploitability depends on rocker availability, device lifecycle control, and local operational context.
Mitigation direction
Update to a vendor kernel containing the referenced stable rocker fix.
Prioritize systems known to load or depend on the rocker driver.
If no vendor package is available, monitor vendor kernel guidance.
Consider reducing unnecessary rocker usage until patched, where operationally safe.
Validation and detection
Inventory Linux kernel versions and distribution security advisories.
Check whether the rocker driver is present or used on systems.
Confirm the deployed kernel includes the referenced stable commit for its branch.
Review system monitoring for memory pressure during rocker device removal testing.
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-2026-23164 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.