Quick answers
- Is CVE-2026-98415 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98415 being exploited in the wild.
- How severe is CVE-2026-98415?
- Informational severity, published 14 October 2026.
- Which products and versions are affected?
- Linux kernel Kernel versions from the introduction of the affected code (commit 78b72897a5c8) through patched versions.
- Is there a fix for CVE-2026-98415?
- A patch was published on 2026-09-25. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98415 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-98415?
- Check whether you run Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The setup_cpuhp_and_cpuidle() function in drivers/soc/samsung/exynos-pmu.c parses a device tree node via of_parse_phandle(), immediately calls of_node_put() to decrement its reference count, then later passes the now-invalid pointer to of_syscon_register_regmap(). The fix uses automatic cleanup (__free() annotation) to defer node reference release until the function exits. This is a use-after-free in the local scope with local attack vector.
Affected products
- Linux kernel Kernel versions from the introduction of the affected code (commit 78b72897a5c8) through patched versions
Timeline
- 2026-10-14: disclosed
- 2026-09-25: patched