From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Ashwin Kamat <ashwin.kamat@broadcom.com>, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, davem@davemloft.net,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, kuba@kernel.org,
netdev@vger.kernel.org, ajay.kaher@broadcom.com,
vasavi.sirnapalli@broadcom.com, tapas.kundu@broadcom.com
Subject: Re: [PATCH v5.15 0/2] Fix for CVE-2024-36901
Date: Fri, 12 Jul 2024 14:19:54 -0700 [thread overview]
Message-ID: <d77be212-8bf5-4ec2-9890-335cd320ea87@broadcom.com> (raw)
In-Reply-To: <1720520384-9690-1-git-send-email-ashwin.kamat@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On 7/9/24 03:19, Ashwin Kamat wrote:
> From: Ashwin Dayanand Kamat <ashwin.kamat@broadcom.com>
>
> net/ipv6: annotate data-races around cnf.disable_ipv6
> disable_ipv6 is read locklessly, add appropriate READ_ONCE() and WRITE_ONCE() annotations.
>
> net/ipv6: prevent NULL dereference in ip6_output()
> Fix for CVE-2024-36901
LGTM!
>
> Ashwin Dayanand Kamat (2):
> net/ipv6: annotate data-races around cnf.disable_ipv6
> net/ipv6: prevent NULL dereference in ip6_output()
>
> net/ipv6/addrconf.c | 9 +++++----
> net/ipv6/ip6_input.c | 2 +-
> net/ipv6/ip6_output.c | 2 +-
> 3 files changed, 7 insertions(+), 6 deletions(-)
>
--
Florian
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]
prev parent reply other threads:[~2024-07-12 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 10:19 [PATCH v5.15 0/2] Fix for CVE-2024-36901 Ashwin Kamat
2024-07-09 10:19 ` [PATCH v5.15 1/2] net/ipv6: annotate data-races around cnf.disable_ipv6 Ashwin Kamat
2024-07-09 10:19 ` [PATCH v5.15 2/2] net/ipv6: prevent NULL dereference in ip6_output() Ashwin Kamat
2024-07-12 21:19 ` Florian Fainelli [this message]
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=d77be212-8bf5-4ec2-9890-335cd320ea87@broadcom.com \
--to=florian.fainelli@broadcom.com \
--cc=ajay.kaher@broadcom.com \
--cc=ashwin.kamat@broadcom.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tapas.kundu@broadcom.com \
--cc=vasavi.sirnapalli@broadcom.com \
--cc=yoshfuji@linux-ipv6.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