[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220713063204.6294-1-khalid.masum.92@gmail.com>
Date: Wed, 13 Jul 2022 12:32:03 +0600
From: Khalid Masum <khalid.masum.92@...il.com>
To: linux-kernel-mentees@...ts.linuxfoundation.org,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
"David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Cc: Shuah Khan <skhan@...uxfoundation.org>,
Pavel Skripkin <paskripkin@...il.com>,
khalid.masum.92@...il.com, Marc Kleine-Budde <mkl@...gutronix.de>,
Stefano Garzarella <sgarzare@...hat.com>,
Alexei Starovoitov <ast@...nel.org>,
Florian Fainelli <f.fainelli@...il.com>,
Nikolay Aleksandrov <nikolay@...dia.com>,
syzbot+1fa91bcd05206ff8cbb5@...kaller.appspotmail.com
Subject: [RFC PATCH 0/1] Fix KASAN: slab-out-of-bounds Read in sk_psock_get
Using size of sk_psock as the size for kcm_psock_cache size no longer
reproduces the issue. There might be a better way to solve this issue
though so I would like to ask for feedback.
Reported-and-tested-by: syzbot+1fa91bcd05206ff8cbb5@...kaller.appspotmail.com
Link: https://syzkaller.appspot.com/bug?extid=1fa91bcd05206ff8cbb5
Khalid Masum (1):
net: kcm: Use sk_psock size for kcm_psock_cache
net/kcm/kcmsock.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.36.1
Powered by blists - more mailing lists