From: syzbot <syzbot+list6e764589c9e10496560e@syzkaller.appspotmail.com>
To: linux-hams@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly hams report (Jan 2025)
Date: Thu, 16 Jan 2025 02:12:22 -0800 [thread overview]
Message-ID: <6788db86.050a0220.20d369.002c.GAE@google.com> (raw)
Hello hams maintainers/developers,
This is a 31-day syzbot report for the hams subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/hams
During the period, 1 new issues were detected and 0 were fixed.
In total, 9 issues are still open and 36 have already been fixed.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 3145 Yes WARNING: refcount bug in ax25_release (3)
https://syzkaller.appspot.com/bug?extid=33841dc6aa3e1d86b78a
<2> 517 Yes possible deadlock in nr_rt_device_down (3)
https://syzkaller.appspot.com/bug?extid=ccdfb85a561b973219c7
<3> 505 Yes KMSAN: uninit-value in ax25cmp (3)
https://syzkaller.appspot.com/bug?extid=74161d266475935e9c5d
<4> 63 No KASAN: slab-use-after-free Read in rose_get_neigh
https://syzkaller.appspot.com/bug?extid=e04e2c007ba2c80476cb
<5> 50 No possible deadlock in serial8250_handle_irq
https://syzkaller.appspot.com/bug?extid=5fd749c74105b0e1b302
<6> 27 No possible deadlock in nr_remove_neigh (2)
https://syzkaller.appspot.com/bug?extid=8863ad36d31449b4dc17
<7> 7 No KASAN: slab-use-after-free Read in ax25_release
https://syzkaller.appspot.com/bug?extid=a5716c7fb89dcd7205d8
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
To disable reminders for individual bugs, reply with the following command:
#syz set <Ref> no-reminders
To change bug's subsystems, reply with:
#syz set <Ref> subsystems: new-subsystem
You may send multiple commands in a single email message.
reply other threads:[~2025-01-16 10:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6788db86.050a0220.20d369.002c.GAE@google.com \
--to=syzbot+list6e764589c9e10496560e@syzkaller.appspotmail.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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