CVE-2023-53638: octeon_ep: cancel queued works in probe error path
In the Linux kernel, the following vulnerability has been resolved:
octeon_ep: cancel queued works in probe error path
If it fails to get the devices's MAC address, octep_probe exits while
leaving the delayed work intr_poll_task queued. When the work later
runs, it's a use after free.
Move the cancelation of intr_poll_task from octep_remove into
octep_device_cleanup. This does not change anything in the octep_remove
flow, but octep_device_cleanup is called also in the octep_probe error
path, where the cancelation is needed.
Note that the cancelation of ctrl_mbox_task has to follow
intr_poll_task's, because the ctrl_mbox_task may be queued by
intr_poll_task.
Security readout for executives and security teams
Plain-English summary
This CVE is a Linux kernel driver cleanup bug. If the octeon_ep driver probe fails while reading a device MAC address, delayed work can run after related memory is freed, causing a use-after-free. Business urgency depends on whether affected kernels and this hardware/driver are present.
Executive priority
Treat as a targeted kernel maintenance issue, not a broad emergency based on current evidence. Prioritize validation on Linux hosts with matching driver or hardware exposure, then apply vendor kernel updates through normal urgent patch channels.
Technical view
The flaw is in the Linux octeon_ep driver probe error path. intr_poll_task remained queued after octep_probe exited on MAC address retrieval failure. Later execution could touch freed state. The fix moves intr_poll_task cancellation into octep_device_cleanup, with ctrl_mbox_task cancellation ordered afterward because intr_poll_task may queue it.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the octeon_ep driver and relevant hardware or probe paths. The supplied data names Linux 6.4, 6.4.12, and 6.5 related affected version information, but distribution backport status is not provided.
Exploitation context
No active exploitation is supported by the supplied sources, and the CVE is not marked KEV. The source bundle describes a use-after-free triggered by a probe failure path, but does not provide exploitability, impact, or privilege requirements.
Researcher notes
The key behavior is delayed work surviving the probe error path. Review the referenced stable commits for exact code movement and cancellation ordering. Evidence does not establish practical exploitability, remote reachability, or post-fix affected ranges for downstream distributions.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution advisories for CVE-2023-53638 backport status.
Prioritize systems using the octeon_ep driver or matching hardware.
If exposed, test updated kernels before production rollout.
Validation and detection
Inventory kernel versions across Linux hosts.
Check whether the octeon_ep driver is built, loaded, or required.
Confirm installed kernel includes one of the referenced fixes or a vendor backport.
Review fleet hardware for devices using this driver path.
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-53638 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.
Oct 7, 2025, 15:19 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.