From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64173: tracing: Do not call map->ops->elt_free() if elt_alloc() fails
Date: Sun, 19 Jul 2026 17:40:35 +0200 [thread overview]
Message-ID: <2026071936-CVE-2026-64173-6ece@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
tracing: Do not call map->ops->elt_free() if elt_alloc() fails
In paths where tracing_map_elt_alloc() failed to allocate objects,
the map->ops->elt_alloc() call was never successful. In this case,
map->ops->elt_free() should not be called.
The Linux kernel CVE team has assigned CVE-2026-64173 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 5.10.258 with commit 49332e49ad5b20262cc719b03d4123b9362de701
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 5.15.209 with commit b559a218eece132de0c58d444877b5627cbee524
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 6.1.175 with commit b427e9f6d81c9341cba23ef92f860f99f830d91d
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 6.6.142 with commit f383cff9fb382139980bac1bcd3f3f5d59f68435
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 6.12.92 with commit 1a150947f8480262a46c860f1acb9c6597ca7097
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 6.18.34 with commit 798183376d9d3e278a270ea0e75a5769c8f145d9
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 7.0.11 with commit b6723339736320b2e1784258ad4490cec7aac11a
Issue introduced in 4.17 with commit 2734b629525a9dae5bf217cbf0a9651da93d2108 and fixed in 7.1 with commit 8f0f5c4fb9df0e19a341e0c6ed8dc4fda9124f03
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-64173
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:
kernel/trace/tracing_map.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/49332e49ad5b20262cc719b03d4123b9362de701
https://git.kernel.org/stable/c/b559a218eece132de0c58d444877b5627cbee524
https://git.kernel.org/stable/c/b427e9f6d81c9341cba23ef92f860f99f830d91d
https://git.kernel.org/stable/c/f383cff9fb382139980bac1bcd3f3f5d59f68435
https://git.kernel.org/stable/c/1a150947f8480262a46c860f1acb9c6597ca7097
https://git.kernel.org/stable/c/798183376d9d3e278a270ea0e75a5769c8f145d9
https://git.kernel.org/stable/c/b6723339736320b2e1784258ad4490cec7aac11a
https://git.kernel.org/stable/c/8f0f5c4fb9df0e19a341e0c6ed8dc4fda9124f03
reply other threads:[~2026-07-19 15:48 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=2026071936-CVE-2026-64173-6ece@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox