From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43447: iavf: fix PTP use-after-free during reset
Date: Fri, 8 May 2026 16:22:56 +0200 [thread overview]
Message-ID: <2026050856-CVE-2026-43447-5a2b@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
iavf: fix PTP use-after-free during reset
Commit 7c01dbfc8a1c5f ("iavf: periodically cache PHC time") introduced a
worker to cache PHC time, but failed to stop it during reset or disable.
This creates a race condition where `iavf_reset_task()` or
`iavf_disable_vf()` free adapter resources (AQ) while the worker is still
running. If the worker triggers `iavf_queue_ptp_cmd()` during teardown, it
accesses freed memory/locks, leading to a crash.
Fix this by calling `iavf_ptp_release()` before tearing down the adapter.
This ensures `ptp_clock_unregister()` synchronously cancels the worker and
cleans up the chardev before the backing resources are destroyed.
The Linux kernel CVE team has assigned CVE-2026-43447 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 7c01dbfc8a1c5f8b8e4a7907ab06db1449d478d0 and fixed in 6.18.19 with commit 1b034f2429ce6b45ce74dc266175d277acafc5c4
Issue introduced in 6.15 with commit 7c01dbfc8a1c5f8b8e4a7907ab06db1449d478d0 and fixed in 6.19.9 with commit 90cc8b2add29b57288025b51c70bc647e7cccb12
Issue introduced in 6.15 with commit 7c01dbfc8a1c5f8b8e4a7907ab06db1449d478d0 and fixed in 7.0 with commit efc54fb13d79117a825fef17364315a58682c7ec
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-43447
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/iavf/iavf_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/1b034f2429ce6b45ce74dc266175d277acafc5c4
https://git.kernel.org/stable/c/90cc8b2add29b57288025b51c70bc647e7cccb12
https://git.kernel.org/stable/c/efc54fb13d79117a825fef17364315a58682c7ec
reply other threads:[~2026-05-08 14:26 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=2026050856-CVE-2026-43447-5a2b@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