From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors
Date: Sun, 19 Jul 2026 16:57:38 +0200 [thread overview]
Message-ID: <2026071906-CVE-2026-63998-e5c0@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ethtool: module: call ethnl_ops_complete() on module flash errors
When validate() fails we are skipping over ethnl_ops_complete()
even tho we already called ethnl_ops_begin().
The Linux kernel CVE team has assigned CVE-2026-63998 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.11 with commit 32b4c8b53ee7799e34a2b1634d32d3ce1e36c44e and fixed in 6.18.35 with commit d9defbf8b62bde89e206d74c2a2b445b9ed66108
Issue introduced in 6.11 with commit 32b4c8b53ee7799e34a2b1634d32d3ce1e36c44e and fixed in 7.0.12 with commit e96ef1a40dda5b637b1911cd950b11e9848de939
Issue introduced in 6.11 with commit 32b4c8b53ee7799e34a2b1634d32d3ce1e36c44e and fixed in 7.1 with commit 84371fb58423f997939aacdcbc02d128d76a54e5
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-63998
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:
net/ethtool/module.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/d9defbf8b62bde89e206d74c2a2b445b9ed66108
https://git.kernel.org/stable/c/e96ef1a40dda5b637b1911cd950b11e9848de939
https://git.kernel.org/stable/c/84371fb58423f997939aacdcbc02d128d76a54e5
reply other threads:[~2026-07-19 15: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=2026071906-CVE-2026-63998-e5c0@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.