# CVE-2026-45989: of: unittest: fix use-after-free in testdrv_probe()

> A use-after-free in the Linux kernel's device tree unit test driver allows attackers to potentially execute code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 14 Jun 2026
- **Also known as:** AZL-88707, BELL-CVE-2026-45989, DEBIAN-CVE-2026-45989, GHSA-26rf-29mw-gf9h, ROOT-OS-UBUNTU-2404-CVE-2026-45989, UBUNTU-CVE-2026-45989

## What is CVE-2026-45989?

CVE-2026-45989 is a high-severity use after free vulnerability in Linux kernel, published on 27 May 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:

of: unittest: fix use-after-free in testdrv_probe()

The function testdrv_probe() retrieves the device_node from the PCI
device, applies an overlay, and then immediately calls of_node_put(dn).
This releases the reference held by the PCI core, potentially freeing
the node if the reference count drops to zero. Later, the same freed
pointer 'dn' is passed to of_platform_default_populate(), leading to a
use-after-free.

The reference to pdev->dev.of_node is owned by the device model and
should not be released by the driver. Remove the erroneous of_node_put()
to prevent premature freeing.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-45989 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45989 is a high-severity use after free vulnerability in Linux kernel, published on 27 May 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-45989 in the wild and no public exploit code.

Affected product: Linux kernel. 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-45989/ (Markdown: https://insights.sbomify.com/CVE-2026-45989/index.md)
```

## Sources

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

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