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

> A double free bug in the Rockchip USB2 PHY driver allows local attackers to cause a denial of service or potentially execute code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Jan 2026
- **Updated:** 2 Jun 2026
- **Also known as:** BELL-CVE-2026-23030, DEBIAN-CVE-2026-23030, GHSA-p937-325h-2j2f, ROOT-OS-DEBIAN-12-CVE-2026-23030, ROOT-OS-DEBIAN-13-CVE-2026-23030, ROOT-OS-UBUNTU-2404-CVE-2026-23030, UBUNTU-CVE-2026-23030

## What is CVE-2026-23030?

CVE-2026-23030 is an use after free vulnerability in Linux, published on 31 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

## Which versions are affected by CVE-2026-23030?


## How do I fix CVE-2026-23030?

Apply the vendor's patch.

## Is CVE-2026-23030 being exploited?

There is no known exploitation of CVE-2026-23030 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23030 and fix it if it is affected.

What it is: CVE-2026-23030 is an use after free vulnerability in Linux, published on 31 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23030 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23030/ (Markdown: https://insights.sbomify.com/CVE-2026-23030/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23030
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23030
- OSV: https://osv.dev/vulnerability/CVE-2026-23030

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23030/
Summaries are generated and may contain mistakes; the official description above is the record.