Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <7f189d22226841168eb46b7be8939e2d06fa476c.camel@redhat.com>
Subject: Re: memory leak in ipv6_sock_ac_join
From:   Paolo Abeni <pabeni@redhat.com>
To:     =?UTF-8?Q?=E8=8C=83=E4=BF=8A=E6=9D=B0?= <junjie2020@iscas.ac.cn>,
        davem@davemloft.net, dsahern@kernel.org, edumazet@google.com,
        kuba@kernel.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org
Cc:     syzkaller-bugs@googlegroups.com
Date:   Fri, 19 May 2023 16:46:42 +0200
In-Reply-To: <13e257b8.6869.18833286427.Coremail.junjie2020@iscas.ac.cn>
References: <13e257b8.6869.18833286427.Coremail.junjie2020@iscas.ac.cn>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Precedence: bulk

hi,

Please use plain-text when sending messages to a kernel devel mailing
list.

On Fri, 2023-05-19 at 16:37 +0800, =E8=8C=83=E4=BF=8A=E6=9D=B0 wrote:
> Our modified=C2=A0tool found a new bug=C2=A0BUG: unable to handle kernel =
NULL
> pointer dereference in scsi_queue_rq=C2=A0

What you mention above is different from what you actually reports
below.

> in=C2=A0Kernel=C2=A0commit v5.14.=C2=A0

That is not exactly new.

> The report is as below and this bug don't have a repro C program
> until now.=C2=A0Please inform me if you confirm this is a=C2=A0reproducib=
le
> bug.

I think the above expectation is quite beyond what you could get. When
you reports a bug _you_ are supposed to try to reproduce it.

> =C2=A0---
> =C2=A0BUG: memory leak
> unreferenced object 0xffff8ad4e16c5760 (size 32):
> =C2=A0 comm "syz-executor.2", pid 17137, jiffies 4295510146 (age 7.862s)
> =C2=A0 hex dump (first 32 bytes):
> =C2=A0 =C2=A0 fe 80 00 00 00 00 00 00 00 00 00 00 00 00 00 bb=C2=A0 .....=
...........
> =C2=A0 =C2=A0 01 00 00 00 d4 8a ff ff 00 00 00 00 00 00 00 00=C2=A0 .....=
...........
> =C2=A0 backtrace:
> =C2=A0 =C2=A0 [<00000000033cd1b4>] kmalloc include/linux/slab.h:605 [inli=
ne]
> =C2=A0 =C2=A0 [<00000000033cd1b4>] sock_kmalloc+0x48/0x80 net/core/sock.c=
:2563
> =C2=A0 =C2=A0 [<00000000724962dc>] ipv6_sock_ac_join+0xf0/0x2d0
> net/ipv6/anycast.c:86
> =C2=A0 =C2=A0 [<0000000027291f90>] do_ipv6_setsockopt.isra.14+0x1e23/0x21=
a0
> net/ipv6/ipv6_sockglue.c:868
> =C2=A0 =C2=A0 [<00000000bb6b5160>] ipv6_setsockopt+0xa9/0xf0
> net/ipv6/ipv6_sockglue.c:1021
> =C2=A0 =C2=A0 [<0000000057fe6cc3>] udpv6_setsockopt+0x53/0xa0
> net/ipv6/udp.c:1652
> =C2=A0 =C2=A0 [<0000000023dcd6bb>] __sys_setsockopt+0xb6/0x160
> net/socket.c:2259
> =C2=A0 =C2=A0 [<0000000081a16a2e>] __do_sys_setsockopt net/socket.c:2270
> [inline]
> =C2=A0 =C2=A0 [<0000000081a16a2e>] __se_sys_setsockopt net/socket.c:2267
> [inline]
> =C2=A0 =C2=A0 [<0000000081a16a2e>] __x64_sys_setsockopt+0x22/0x30
> net/socket.c:2267
> =C2=A0 =C2=A0 [<0000000075aec224>] do_syscall_x64 arch/x86/entry/common.c=
:50
> [inline]
> =C2=A0 =C2=A0 [<0000000075aec224>] do_syscall_64+0x37/0x80
> arch/x86/entry/common.c:80
> =C2=A0 =C2=A0 [<000000006cd4d12f>] entry_SYSCALL_64_after_hwframe+0x46/0x=
b0
>=20
> BUG: leak checking failed

This was probably addressed by:

8c0de6e96c97 ("ipv6: fix memory leaks on IPV6_ADDRFORM path")=C2=A0


Cheers,

Paolo