Linux kernel CVE announcements
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99219: ftrace: Initialize modname and offset in print_rec()
Date: Mon,  2 Nov 2026 17:04:02 +0100	[thread overview]
Message-ID: <2026110202-CVE-2026-99219-efda@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ftrace: Initialize modname and offset in print_rec()

print_rec() leaves 'modname' and 'offset' uninitialized and
kallsyms_lookup() only sets them on success. When the lookup fails like
when a module is being loaded or unloaded, 'modname' holds a garbage
value, passes the 'if (modname)' check, and is dereferenced by
seq_printf().

  Oops: general protection fault
  RIP: 0010:string+0x48/0xe0
  Call Trace:
   vsnprintf+0x1f5/0x650
   seq_printf+0x8e/0xb0
   print_rec+0x6c/0xc0
   t_show+0x4c/0x440
   seq_read_iter+0x119/0x480

This can be triggered by reading available_filter_functions while a
module is being loaded or unloaded.

Initialize both variables so a failed lookup skips the module name.

The Linux kernel CVE team has assigned CVE-2026-99219 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 6.1.191 with commit 753d5cba113a52cb155428f4ea93a4b0148c4bf1
	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 6.6.161 with commit 0e5ff07be834abaf4280e1dca7f9591e339d0960
	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 6.12.115 with commit e2e6fb972bfec4a0551bc7c185bdb17f78f94997
	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 6.18.60 with commit 8932e5a4df110a25578728526bb5a3dbc849d8a2
	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 7.2.14 with commit 7271c064dd60d4456c5b90da757acd9420d06697
	Issue introduced in 5.19 with commit b39181f7c6907dc66ff937b74758671fa6ba430c and fixed in 7.3.1 with commit d97dba9ff13987d1fc415408557a54adde980311

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-99219
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/ftrace.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/753d5cba113a52cb155428f4ea93a4b0148c4bf1
	https://git.kernel.org/stable/c/0e5ff07be834abaf4280e1dca7f9591e339d0960
	https://git.kernel.org/stable/c/e2e6fb972bfec4a0551bc7c185bdb17f78f94997
	https://git.kernel.org/stable/c/8932e5a4df110a25578728526bb5a3dbc849d8a2
	https://git.kernel.org/stable/c/7271c064dd60d4456c5b90da757acd9420d06697
	https://git.kernel.org/stable/c/d97dba9ff13987d1fc415408557a54adde980311
	https://git.kernel.org/stable/c/e1f339ff3b83857b93baf8b88186275a413d445e

                 reply	other threads:[~2026-11-02 16:04 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=2026110202-CVE-2026-99219-efda@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