From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98842: module: fix lost error code from codetag_load_module()
Date: Sun, 18 Oct 2026 17:46:57 +0200 [thread overview]
Message-ID: <2026101833-CVE-2026-98842-e8d8@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
module: fix lost error code from codetag_load_module()
If codetag_load_module() fails, err is not set to reflect the failure
and load_module() returns 0 after the module has been torn down.
Also, if the module is a livepatch, mod->klp_info allocated by
copy_module_elf() leaks on this error path. Free it via a new
livepatch_cleanup label.
The Linux kernel CVE team has assigned CVE-2026-98842 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit 044d2aee6c575231ed4a24fb3d119bad0937488b and fixed in 6.18.56 with commit 258310d59a82ea4854bfd9138682bbaac1153b19
Issue introduced in 6.16 with commit 044d2aee6c575231ed4a24fb3d119bad0937488b and fixed in 7.2.10 with commit bfc721eef5c13704efe6864c7da2ad4b0d75f60a
Issue introduced in 6.16 with commit 044d2aee6c575231ed4a24fb3d119bad0937488b and fixed in 7.3-rc6 with commit c79cf15eb35a4c703bf18f8c33c47e80dd660f8e
Issue introduced in 6.15.4 with commit b6bbbb8ef48dde09c0dbd77121fa0f09b0237fec
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-98842
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/module/main.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/258310d59a82ea4854bfd9138682bbaac1153b19
https://git.kernel.org/stable/c/bfc721eef5c13704efe6864c7da2ad4b0d75f60a
https://git.kernel.org/stable/c/c79cf15eb35a4c703bf18f8c33c47e80dd660f8e
reply other threads:[~2026-10-18 16:23 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=2026101833-CVE-2026-98842-e8d8@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.