From: syzbot <syzbot+list205929fef9983ad8ebbc@syzkaller.appspotmail.com>
To: dccp@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] Monthly dccp report (Dec 2023)
Date: Fri, 08 Dec 2023 05:16:30 -0800 [thread overview]
Message-ID: <00000000000076a6ea060bff64b3@google.com> (raw)
Hello dccp maintainers/developers,
This is a 31-day syzbot report for the dccp subsystem.
All related reports/information can be found at:
https://syzkaller.appspot.com/upstream/s/dccp
During the period, 0 new issues were detected and 0 were fixed.
In total, 5 issues are still open and 6 have been fixed so far.
Some of the still happening issues:
Ref Crashes Repro Title
<1> 102 Yes KASAN: use-after-free Read in ccid2_hc_tx_packet_recv
https://syzkaller.appspot.com/bug?extid=554ccde221001ab5479a
<2> 51 Yes BUG: "hc->tx_t_ipi == NUM" holds (exception!) at net/dccp/ccids/ccid3.c:LINE/ccid3_update_send_interval()
https://syzkaller.appspot.com/bug?extid=94641ba6c1d768b1e35e
<3> 23 Yes general protection fault in dccp_write_xmit (2)
https://syzkaller.appspot.com/bug?extid=c71bc336c5061153b502
<4> 14 Yes BUG: stored value of X_recv is zero at net/dccp/ccids/ccid3.c:LINE/ccid3_first_li() (3)
https://syzkaller.appspot.com/bug?extid=2ad8ef335371014d4dc7
---
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:[~2023-12-08 13:16 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=00000000000076a6ea060bff64b3@google.com \
--to=syzbot+list205929fef9983ad8ebbc@syzkaller.appspotmail.com \
--cc=dccp@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).