From: Greg KH <gregkh@linuxfoundation.org>
To: Marek Kroemeke <mkroemeke@cloudflare.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, pmladek@suse.com,
kernel-team@cloudflare.com
Subject: Re: Missing patches from kallsyms buildid series in 6.18.y and 6.19.y
Date: Wed, 8 Apr 2026 14:55:34 +0200 [thread overview]
Message-ID: <2026040827-herself-negative-d45b@gregkh> (raw)
In-Reply-To: <zw373rzoyossoqhzvodfzilvomdi2mtljnbakm6bmhv7itwer6@4jcp4l3qvyjv>
On Wed, Apr 08, 2026 at 11:38:51AM +0000, Marek Kroemeke wrote:
> Hi,
>
> Petr Mladek's series "kallsyms: Prevent invalid access when showing
> module buildid" [1] was partially applied to the 6.18.y longterm and
> 6.19.y stable trees. Patches 3, 5, and 6 from the 7-patch series
> landed:
>
> acfdbb4ab291 ("module: add helper function for reading module_buildid()")
> cd6735896d03 ("kallsyms/bpf: rename __bpf_address_lookup() to bpf_address_lookup()")
> e8a1e7eaa19d ("kallsyms/ftrace: set module buildid in ftrace_mod_address_lookup()")
>
> But patches 1, 2, 4, and 7 did not:
> 426295ef18c5 ("kallsyms: clean up @namebuf initialization in kallsyms_lookup_buildid()")
> fda024fb6476 ("kallsyms: clean up modname and modbuildid initialization in kallsyms_lookup_buildid()")
> 8e81dac4cd54 ("kallsyms: cleanup code for appending the module buildid")
> 3b07086444f8 ("kallsyms: prevent module removal when printing module name and buildid")
>
> Without the missing patches, __sprint_symbol() can use an
> uninitialized or dangling mod->build_id pointer during backtrace
> printing. We hit KASAN errors and stack protector failures due to this partial application.
>
>
> Could these four commits please be queued for both trees?
> [1] https://lore.kernel.org/all/20251128135920.217303-1-pmladek@suse.com/
All now queued up thanks.
greg k-h
prev parent reply other threads:[~2026-04-08 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 11:38 Missing patches from kallsyms buildid series in 6.18.y and 6.19.y Marek Kroemeke
2026-04-08 12:55 ` Greg KH [this message]
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=2026040827-herself-negative-d45b@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kernel-team@cloudflare.com \
--cc=mkroemeke@cloudflare.com \
--cc=pmladek@suse.com \
--cc=sashal@kernel.org \
--cc=stable@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.