CVE-2026-23160: octeon_ep: Fix memory leak in octep_device_setup()
In the Linux kernel, the following vulnerability has been resolved:
octeon_ep: Fix memory leak in octep_device_setup()
In octep_device_setup(), if octep_ctrl_net_init() fails, the function
returns directly without unmapping the mapped resources and freeing the
allocated configuration memory.
Fix this by jumping to the unsupported_dev label, which performs the
necessary cleanup. This aligns with the error handling logic of other
paths in this function.
Compile tested only. Issue found using a prototype static analysis tool
and code review.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23160 is a Linux kernel cleanup bug in the octeon_ep driver. If device setup reaches a specific failure path, mapped resources and configuration memory may not be released. The public record does not provide CVSS, confirmed impact, or exploitation evidence.
Executive priority
Treat this as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize affected infrastructure using this driver, and fold remediation into the next controlled kernel update unless vendor guidance raises urgency.
Technical view
In octep_device_setup(), failure of octep_ctrl_net_init() returned directly instead of using the existing cleanup path. The fix changes error handling to jump to unsupported_dev, which unmaps resources and frees allocated configuration memory. The issue was found by static analysis and code review, and was compile-tested only.
Likely exposure
Exposure is most likely limited to Linux systems running affected kernel versions where the octeon_ep driver path is present and relevant. The source bundle lists Linux as affected but does not provide distribution package mappings, deployment prevalence, or hardware-specific exposure details.
Exploitation context
No source in the bundle reports active exploitation, public exploit availability, or inclusion in CISA KEV. The record describes a memory leak on an initialization failure path, not a complete attack scenario.
Researcher notes
The public evidence is narrow: root cause, cleanup-path fix, affected Linux record entries, and stable commit references. There is no CVSS, CWE, exploit report, runtime proof, or distribution-specific fixed-version mapping in the provided bundle.
Mitigation direction
Apply Linux kernel or distribution updates that include the referenced stable fixes.
Check vendor or distribution advisories for exact fixed package versions.
Prioritize systems using the octeon_ep driver or related hardware paths.
If updates are delayed, follow vendor guidance for exposure reduction.
Validation and detection
Inventory Linux kernel versions against the CVE record and vendor advisories.
Determine whether octeon_ep support is present or used on affected systems.
Confirm the deployed kernel includes one of the referenced stable fixes.
Track remediation through normal kernel package and reboot validation processes.
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-23160 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
5Source 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.
Feb 14, 2026, 16:01 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.