From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68133: ice: fix PTP Call Trace during PTP release
Date: Mon, 10 Aug 2026 13:57:30 +0200 [thread overview]
Message-ID: <2026081058-CVE-2026-68133-2a7c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ice: fix PTP Call Trace during PTP release
If a PF reset occurs when the PTP state is ICE_PTP_UNINIT, then
ice_ptp_rebuild() will update the state to ICE_PTP_ERROR. This will
result in the following PTP release call trace during driver unload:
kernel BUG at lib/list_debug.c:52!
ice_ptp_release+0x332/0x3c0 [ice]
ice_deinit_features.part.0+0x10e/0x120 [ice]
ice_remove+0x100/0x220 [ice]
This was observed when passing PF1 through to a VM. ice_ptp_init()
fails because ctrl_pf is NULL and sets the state to ICE_PTP_UNINIT.
Fix by detecting the ICE_PTP_UNINIT state in ice_ptp_rebuild() and
returning without error, preventing the invalid state transition to
ICE_PTP_ERROR. The only valid path to ICE_PTP_ERROR is from
ICE_PTP_RESETTING after a failed rebuild.
The Linux kernel CVE team has assigned CVE-2026-68133 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.9 with commit 8293e4cb2ff54b1ec4f7206dcb74c908f62a3fb8 and fixed in 6.12.101 with commit 7d517b255f669cedd09830214d55f2f413b34481
Issue introduced in 6.9 with commit 8293e4cb2ff54b1ec4f7206dcb74c908f62a3fb8 and fixed in 6.18.42 with commit e4406cbdd915f702d2ed9ee8b30683a16b06c6ac
Issue introduced in 6.9 with commit 8293e4cb2ff54b1ec4f7206dcb74c908f62a3fb8 and fixed in 7.1.6 with commit 14fceda28069fdbe1bb49cdb6e1774892b583348
Issue introduced in 6.9 with commit 8293e4cb2ff54b1ec4f7206dcb74c908f62a3fb8 and fixed in 7.2-rc5 with commit f6a7e00b81e35ef1325234925f2fe1e53b466f92
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-68133
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:
drivers/net/ethernet/intel/ice/ice_ptp.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/7d517b255f669cedd09830214d55f2f413b34481
https://git.kernel.org/stable/c/e4406cbdd915f702d2ed9ee8b30683a16b06c6ac
https://git.kernel.org/stable/c/14fceda28069fdbe1bb49cdb6e1774892b583348
https://git.kernel.org/stable/c/f6a7e00b81e35ef1325234925f2fe1e53b466f92
reply other threads:[~2026-08-10 12:02 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=2026081058-CVE-2026-68133-2a7c@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.