From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43454: netfilter: nf_tables: Fix for duplicate device in netdev hooks
Date: Fri, 8 May 2026 16:23:03 +0200 [thread overview]
Message-ID: <2026050859-CVE-2026-43454-83f9@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nf_tables: Fix for duplicate device in netdev hooks
When handling NETDEV_REGISTER notification, duplicate device
registration must be avoided since the device may have been added by
nft_netdev_hook_alloc() already when creating the hook.
The Linux kernel CVE team has assigned CVE-2026-43454 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit a331b78a552551d0e404e58e6390b1c828d6af8f and fixed in 6.18.19 with commit 6d2a95c6890577cc3eab2b20018e16850d7fb094
Issue introduced in 6.16 with commit a331b78a552551d0e404e58e6390b1c828d6af8f and fixed in 6.19.9 with commit 2041cdb078041611510fc189410bc70b29f688fb
Issue introduced in 6.16 with commit a331b78a552551d0e404e58e6390b1c828d6af8f and fixed in 7.0 with commit b7cdc5a97d02c943f4bdde4d5767ad0c13cad92b
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-43454
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/netfilter/nf_tables_api.c
net/netfilter/nft_chain_filter.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/6d2a95c6890577cc3eab2b20018e16850d7fb094
https://git.kernel.org/stable/c/2041cdb078041611510fc189410bc70b29f688fb
https://git.kernel.org/stable/c/b7cdc5a97d02c943f4bdde4d5767ad0c13cad92b
reply other threads:[~2026-05-08 14:27 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=2026050859-CVE-2026-43454-83f9@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