# CVE-2026-89504: regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer

> A use-after-free vulnerability in the Linux kernel's as3722 regulator driver allows attackers to cause denial of service or execute arbitrary code via a dangling pointer.

- **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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100187, BELL-CVE-2026-89504, DEBIAN-CVE-2026-89504, GHSA-w8c6-qh9v-m8g2, UBUNTU-CVE-2026-89504

## What is CVE-2026-89504?

CVE-2026-89504 is a high-severity use after free vulnerability in Linux, published on 11 Sep 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:

regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer

In as3722_get_regulator_dt_data(), of_get_child_by_name() acquires a
reference on np, which is then assigned to pdev->dev.of_node. The
function immediately calls of_node_put(np), releasing the reference and
leaving pdev->dev.of_node as a dangling pointer.

Remove the of_node_put(np) call to let the device hold the reference.

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


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

Apply the vendor's patch.

## Is CVE-2026-89504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89504 is a high-severity use after free vulnerability in Linux, published on 11 Sep 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-89504 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-89504/ (Markdown: https://insights.sbomify.com/CVE-2026-89504/index.md)
```

## Sources

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

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