From: patchwork-bot+netdevbpf@kernel.org
To: Deepanshu Kartikey <kartikey406@gmail.com>
Cc: duncan.sands@free.fr, 3chas3@gmail.com,
gregkh@linuxfoundation.org, edumazet@google.com,
horms@kernel.org, linux-usb@vger.kernel.org,
linux-atm-general@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+6665d3db5fef15914802@syzkaller.appspotmail.com
Subject: Re: [PATCH v2] usb: atm: usbatm: fix invalid ci_range initialization
Date: Thu, 27 Aug 2026 19:50:10 +0000 [thread overview]
Message-ID: <178786021064.1820029.761555165031523021.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260826133258.8306-1-kartikey406@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 26 Aug 2026 19:02:58 +0530 you wrote:
> syzbot reported a shift-out-of-bounds in __vcc_connect():
>
> UBSAN: shift-out-of-bounds in net/atm/common.c:382:32
> shift exponent -1 is negative
> CPU: 0 UID: 0 PID: 5987 Comm: syz.0.18 Not tainted syzkaller #0 PREEMPT(full)
> Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 08/05/2026
> Call Trace:
> <TASK>
> dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120
> ubsan_epilogue+0xa/0x30 lib/ubsan.c:233
> __ubsan_handle_shift_out_of_bounds+0x36d/0x400 lib/ubsan.c:494
> __vcc_connect+0x14b4/0x19c0 net/atm/common.c:382
> vcc_connect+0x328/0x8f0 net/atm/common.c:498
> pvc_bind+0x272/0x380 net/atm/pvc.c:52
> __sys_bind+0x2e3/0x410 net/socket.c:1976
> __x64_sys_bind+0x7a/0x90 net/socket.c:1979
> ...
>
> [...]
Here is the summary with links:
- [v2] usb: atm: usbatm: fix invalid ci_range initialization
https://git.kernel.org/netdev/net/c/a60fd8c6dbaa
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-27 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 13:32 [PATCH v2] usb: atm: usbatm: fix invalid ci_range initialization Deepanshu Kartikey
2026-08-27 19:50 ` patchwork-bot+netdevbpf [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=178786021064.1820029.761555165031523021.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=3chas3@gmail.com \
--cc=duncan.sands@free.fr \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=kartikey406@gmail.com \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+6665d3db5fef15914802@syzkaller.appspotmail.com \
/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