LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23030: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe()

In the Linux kernel, the following vulnerability has been resolved: phy: rockchip: inno-usb2: Fix a double free bug in rockchip_usb2phy_probe() The for_each_available_child_of_node() calls of_node_put() to release child_np in each success loop. After breaking from the loop with the child_np has been released, the code will jump to the put_child label and will call the of_node_put() again if the devm_request_threaded_irq() fails. These cause a double free bug. Fix by returning directly to avoid the duplicate of_node_put().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23030 is a Linux kernel bug in a Rockchip USB2 PHY driver. A failure during device setup can cause the same device-tree node to be released twice. The public bundle does not provide a CVSS score, exploit evidence, or broad product impact details.

Executive priority

Treat as a targeted embedded Linux maintenance item, not a confirmed emergency. Prioritize asset owners with Rockchip-based operational technology or appliances, and rely on vendor firmware guidance before scheduling disruptive updates.

Technical view

The bug is in rockchip_usb2phy_probe() in the Linux rockchip inno-usb2 PHY driver. for_each_available_child_of_node() already releases child_np on successful loop iterations; an error path after devm_request_threaded_irq() failure could call of_node_put() again. Stable kernel commits change the flow to avoid the duplicate release.

Likely exposure

Most relevant exposure is Linux-based devices using Rockchip hardware and the inno-usb2 PHY driver in affected kernel versions. General servers are unlikely to be exposed unless they use this hardware/driver path. Siemens is referenced, but the bundle does not include product-specific impact details.

Exploitation context

The source bundle does not report active exploitation, proof-of-concept code, KEV listing, or attacker prerequisites. The described condition is an error path during driver probe, so practical exploitability and business impact remain unclear from the provided evidence.

Researcher notes

Key uncertainty is exploitability. The bug is a double release in a driver probe error path, fixed by avoiding a duplicate of_node_put(). No CWE, CVSS, exploit status, or Siemens product matrix is provided in the bundle.

Mitigation direction

  • Inventory Linux and firmware builds on Rockchip-based devices.
  • Apply vendor kernels or firmware containing the referenced stable fixes.
  • Track Siemens SSA-253495 for product-specific remediation guidance.
  • Ask vendors for status if embedded firmware does not expose kernel commit history.

Validation and detection

  • Confirm whether devices use Rockchip SoCs and the inno-usb2 PHY driver.
  • Map running kernel builds against affected and fixed stable versions.
  • Review firmware SBOMs or vendor release notes for the referenced commits.
  • Check vulnerability scanners for CVE-2026-23030 coverage, but verify manually.
Prepared
Confidence
medium
Sources
8

Public sources used

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-23030 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
1ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxed2b5a8e6b98d042b323afbe177a5dc618921b31, ed2b5a8e6b98d042b323afbe177a5dc618921b31, ed2b5a8e6b98d042b323afbe177a5dc618921b31, ed2b5a8e6b98d042b323afbe177a5dc618921b31, ed2b5a8e6b98d042b323afbe177a5dc618921b31unaffected
LinuxLinux5.17, 0, 6.1.162, 6.6.122, 6.12.67, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.