Menu

Star on GitHub · 3.4k

CVE-2026-98415

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 n…

Published Oct 14, 2026EPSS 0.21%

Overview

CVE-2026-98415 is a known-severity vulnerability. It was published on October 14, 2026.

Technical 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().

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-98415?

CVE-2026-98415 is a known-severity vulnerability. It was published on October 14, 2026.

How severe is CVE-2026-98415?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-98415?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-98415?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-98415 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Watch the demo →