# CVE-2026-68371: usb: musb: omap2430: Do not put borrowed of_node in probe

> A reference counting error in the Linux kernel USB driver can cause a null pointer dereference, leading to a system crash.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 10 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** AZL-94964, BELL-CVE-2026-68371, DEBIAN-CVE-2026-68371, GHSA-prp8-g9xx-pr9j, UBUNTU-CVE-2026-68371

## What is CVE-2026-68371?

CVE-2026-68371 is a high-severity vulnerability in Linux, published on 10 Aug 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:

usb: musb: omap2430: Do not put borrowed of_node in probe

omap2430_probe() stores pdev->dev.of_node in a local np variable. This is
a borrowed pointer and the probe function does not take a reference to
it.

The success and error paths nevertheless call of_node_put(np). This drops
a reference that is owned by the platform device, and can leave
pdev->dev.of_node with an unbalanced reference count.

Do not put the borrowed platform device node from omap2430_probe().
References taken for the child MUSB device are handled by the device core,
and the ctrl-module phandle reference is still released separately.

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


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

Apply the vendor's patch.

## Is CVE-2026-68371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68371 is a high-severity vulnerability in Linux, published on 10 Aug 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-68371 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-68371/ (Markdown: https://insights.sbomify.com/CVE-2026-68371/index.md)
```

## Sources

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

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