CVE-2026-23164
Memory Leak in Linux Kernel Rocker Port Component Fixed
Publication date: 2026-02-14
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.11 (inc) to 5.15.199 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.162 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.123 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.7 (inc) to 6.12.69 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.9 (exc) |
| linux | linux_kernel | From 4.6 (inc) to 5.10.249 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-401 | The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is a memory leak in the Linux kernel's rocker driver related to the rocker_world_port_post_fini() function.
To mitigate this vulnerability, update your Linux kernel to a version where this issue is fixed. The fix ensures that the allocated memory for rocker_port->wpriv is always freed regardless of whether the port_post_fini callback exists.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
Can you explain this vulnerability to me?
This vulnerability is a memory leak in the Linux kernel's rocker driver. Specifically, in the rocker_world_port_pre_init() function, memory is allocated for rocker_port->wpriv. However, in the rocker_world_port_post_fini() function, this allocated memory is only freed if a certain callback (port_post_fini) is set.
Since the rocker_ofdpa_ops does not implement this port_post_fini callback (it is NULL), the allocated memory for each port is never freed when ports are removed. This causes a memory leak of the size of struct ofdpa_port bytes for every port on every device removal.
The fix involves always freeing the allocated memory regardless of whether the port_post_fini callback exists.
How can this vulnerability impact me? :
This vulnerability can lead to a memory leak in the Linux kernel when ports are removed in the rocker driver. Over time, repeated device removals without freeing the allocated memory can cause increased memory usage, potentially leading to system instability or degraded performance.