From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98415: soc: samsung: exynos-pmu: fix use-after-free of interrupt generator node
Date: Wed, 14 Oct 2026 15:30:13 +0200 [thread overview]
Message-ID: <2026101405-CVE-2026-98415-2e86@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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().
The Linux kernel CVE team has assigned CVE-2026-98415 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit 78b72897a5c8bb9d3b51fc6494a1eb09265487a4 and fixed in 6.18.54 with commit 4450102d6aa2a85b1d2d8610920fcbe45eb0ef69
Issue introduced in 6.18 with commit 78b72897a5c8bb9d3b51fc6494a1eb09265487a4 and fixed in 7.2.8 with commit 164313e24cb0f51528bc2099c5564174ead11d8a
Issue introduced in 6.18 with commit 78b72897a5c8bb9d3b51fc6494a1eb09265487a4 and fixed in 7.3-rc4 with commit 4dd1999783d7d12434006289338373e49492dc96
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98415
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/soc/samsung/exynos-pmu.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/4450102d6aa2a85b1d2d8610920fcbe45eb0ef69
https://git.kernel.org/stable/c/164313e24cb0f51528bc2099c5564174ead11d8a
https://git.kernel.org/stable/c/4dd1999783d7d12434006289338373e49492dc96
reply other threads:[~2026-10-14 13:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026101405-CVE-2026-98415-2e86@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.