From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26808: netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
Date: Thu, 4 Apr 2024 11:51:59 +0200 [thread overview]
Message-ID: <2024040458-CVE-2024-26808-2df2@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: nft_chain_filter: handle NETDEV_UNREGISTER for inet/ingress basechain
Remove netdevice from inet/ingress basechain in case NETDEV_UNREGISTER
event is reported, otherwise a stale reference to netdevice remains in
the hook list.
The Linux kernel CVE team has assigned CVE-2024-26808 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 5.10.210 with commit 9489e214ea8f
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 5.15.149 with commit 70f17b48c866
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 6.1.76 with commit af149a46890e
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 6.6.15 with commit e5888acbf1a3
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 6.7.3 with commit 36a0a80f3220
Issue introduced in 5.10 with commit 60a3815da702 and fixed in 6.8 with commit 01acb2e8666a
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-2024-26808
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/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/9489e214ea8f2a90345516016aa51f2db3a8cc2f
https://git.kernel.org/stable/c/70f17b48c86622217a58d5099d29242fc9adac58
https://git.kernel.org/stable/c/af149a46890e8285d1618bd68b8d159bdb87fdb3
https://git.kernel.org/stable/c/e5888acbf1a3d8d021990ce6c6061fd5b2bb21b4
https://git.kernel.org/stable/c/36a0a80f32209238469deb481967d777a3d539ee
https://git.kernel.org/stable/c/01acb2e8666a6529697141a6017edbf206921913
reply other threads:[~2024-04-04 9:52 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=2024040458-CVE-2024-26808-2df2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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;
as well as URLs for NNTP newsgroup(s).