From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-27016: netfilter: flowtable: validate pppoe header
Date: Wed, 1 May 2024 07:31:17 +0200 [thread overview]
Message-ID: <2024050149-CVE-2024-27016-5114@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
netfilter: flowtable: validate pppoe header
Ensure there is sufficient room to access the protocol field of the
PPPoe header. Validate it once before the flowtable lookup, then use a
helper function to access protocol field.
The Linux kernel CVE team has assigned CVE-2024-27016 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.13 with commit 72efd585f714 and fixed in 5.15.157 with commit d06977b9a410
Issue introduced in 5.13 with commit 72efd585f714 and fixed in 6.1.88 with commit 8bf7c76a2a20
Issue introduced in 5.13 with commit 72efd585f714 and fixed in 6.6.29 with commit a2471d271042
Issue introduced in 5.13 with commit 72efd585f714 and fixed in 6.8.8 with commit cf366ee3bc1b
Issue introduced in 5.13 with commit 72efd585f714 and fixed in 6.9-rc5 with commit 87b3593bed18
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-27016
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:
include/net/netfilter/nf_flow_table.h
net/netfilter/nf_flow_table_inet.c
net/netfilter/nf_flow_table_ip.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/d06977b9a4109f8738bb276125eb6a0b772bc433
https://git.kernel.org/stable/c/8bf7c76a2a207ca2b4cfda0a279192adf27678d7
https://git.kernel.org/stable/c/a2471d271042ea18e8a6babc132a8716bb2f08b9
https://git.kernel.org/stable/c/cf366ee3bc1b7d1c76a882640ba3b3f8f1039163
https://git.kernel.org/stable/c/87b3593bed1868b2d9fe096c01bcdf0ea86cbebf
reply other threads:[~2024-05-01 5:32 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=2024050149-CVE-2024-27016-5114@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).