# CVE-2026-98415: soc: samsung: exynos-pmu: fix use-after-free of interrupt generator node

> A use-after-free vulnerability in the Samsung Exynos PMU driver allows local attackers to potentially execute arbitrary code or escalate privileges.

- **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:** 14 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98415, DEBIAN-CVE-2026-98415, GHSA-x8m9-w5rv-ggmr, UBUNTU-CVE-2026-98415

## What is CVE-2026-98415?

CVE-2026-98415 is an use after free vulnerability in Linux, published on 14 Oct 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:

soc: samsung: exynos-pmu: fix use-after-free of interrupt generator node

The setup_cpuhp_and_cpuidle() parses the device tree node for the
interrupt generation block via of_parse_phandle() and decrements its
reference count using of_node_put() immediately after fetching the resource
address. However, later the intr_gen_node pointer is passed into
of_syscon_register_regmap().

Fix this by declaring intr_gen_node with __free() and removing
of_node_put().

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


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

Apply the vendor's patch.

## Is CVE-2026-98415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98415 is an use after free vulnerability in Linux, published on 14 Oct 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-98415 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-98415/ (Markdown: https://insights.sbomify.com/CVE-2026-98415/index.md)
```

## Sources

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

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