From: Siddh Raman Pant <siddh.raman.pant@oracle.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"edumazet@google.com" <edumazet@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: CVE-2024-41041: udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().
Date: Tue, 3 Sep 2024 11:56:17 +0000 [thread overview]
Message-ID: <0ab22253fec2b0e65a95a22ceff799f39a2eaa0a.camel@oracle.com> (raw)
In-Reply-To: <2024072924-CVE-2024-41041-ae0c@gregkh>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On Mon, 29 Jul 2024 16:32:36 +0200, Greg Kroah-Hartman wrote:
> In the Linux kernel, the following vulnerability has been resolved:
>
> udp: Set SOCK_RCU_FREE earlier in udp_lib_get_port().
>
> [...]
>
> We had the same bug in TCP and fixed it in commit 871019b22d1b ("net:
> set SOCK_RCU_FREE before inserting socket into hashtable").
>
> Let's apply the same fix for UDP.
>
> [...]
>
> The Linux kernel CVE team has assigned CVE-2024-41041 to this issue.
>
>
> Affected and fixed versions
> ===========================
>
> Issue introduced in 4.20 with commit 6acc9b432e67 and fixed in 5.4.280 with commit 7a67c4e47626
> Issue introduced in 4.20 with commit 6acc9b432e67 and fixed in 5.10.222 with commit 9f965684c57c
These versions don't have the TCP fix backported. Please do so.
Thanks,
Siddh
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2024-09-03 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024072924-CVE-2024-41041-ae0c@gregkh>
2024-09-03 11:56 ` Siddh Raman Pant [this message]
2024-09-03 12:07 ` gregkh
2024-09-03 12:53 ` Eric Dumazet
2024-09-03 12:58 ` gregkh
2024-09-04 11:26 ` Siddh Raman Pant
2024-09-04 11:31 ` gregkh
2024-09-04 13:06 ` [PATCH 5.10, 5.4] net: set SOCK_RCU_FREE before inserting socket into hashtable Siddh Raman Pant
2024-09-05 7:43 ` gregkh
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=0ab22253fec2b0e65a95a22ceff799f39a2eaa0a.camel@oracle.com \
--to=siddh.raman.pant@oracle.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stable@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
all inboxes | Powered by JetHome®