From: syzbot <syzbot+b3c08bda38b11fb7a6a0@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING: `SYZ.NUM.NUM' USES NUM-BIT CAPABILITIES (LEGACY SUPPORT IN USE)
Date: Thu, 05 Dec 2024 00:38:29 -0800 [thread overview]
Message-ID: <67516685.050a0220.17bd51.008c.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: feffde684ac2 Merge tag 'for-6.13-rc1-tag' of git://git.ker..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=125da330580000
kernel config: https://syzkaller.appspot.com/x/.config?x=6851fe4f61792030
dashboard link: https://syzkaller.appspot.com/bug?extid=b3c08bda38b11fb7a6a0
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/7feb34a89c2a/non_bootable_disk-feffde68.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e9751e7030ea/vmlinux-feffde68.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f7bf928b44d6/bzImage-feffde68.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b3c08bda38b11fb7a6a0@syzkaller.appspotmail.com
DEC 4 15:29:08 SYZKALLER KERN.INFO KERNEL: [ 77.863093][ T8] IPVS: STARTING ESTIMATOR THREAD 0...
DEC 4 15:29:08 SYZKALLER KERN.INFO KERNEL: [ 77.897775][ T8011] CAPABILITY: WARNING: `SYZ.2.644' USES 32-BIT CAPABILITIES (LEGACY SUPPORT IN USE)
DEC 4 15:29:08 SYZKALLER KERN.INFO KERNEL: [ 77.956610][ T8007] IPVS: USING MAX 39 ESTS PER CHAIN, 93600 PER KTHREAD
DEC 4 15:29:09 SYZKALLER KERN.WARN KERNEL: [ 77.991570][ T8023] SELINUX: UNRECOGNIZED NETLINK MESSAGE: PROTOCOL=0 NLMSG_TYPE=0 SCLASS=NETLINK_ROUTE_SOCKET PID=8023 COMM=SYZ.0.647
DEC 4 15:29:14 SYZKALLER DAEMON.ERR DHCPCD[8024]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:14 SYZKALLER DAEMON.ERR DHCPCD[8024]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:14 SYZKALLER KERN.WARN KERNEL: [ 83.080206][ T39] KAUDITD_PRINTK_SKB: 1103 CALLBACKS SUPPRESSED
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.080219][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.083:3132): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.105246][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.103:3133): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.124798][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.123:3134): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.147813][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.143:3135): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.196065][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.193:3136): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.239782][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.243:3137): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.291565][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.293:3138): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.332978][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.333:3139): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.373209][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.373:3140): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:14 SYZKALLER KERN.NOTICE KERNEL: [ 83.411641][ T39] AUDIT: TYPE=1400 AUDIT(1733326154.413:3141): AVC: DENIED { READ } FOR PID=5331 COMM="SYSLOGD" NAME="LOG" DEV="SDA1" INO=1915 SCONTEXT=SYSTEM_U:SYSTEM_R:SYSLOGD_T TCONTEXT=SYSTEM_U:OBJECT_R:VAR_T TCLASS=
DEC 4 15:29:15 SYZKALLER DAEMON.ERR DHCPCD[8025]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:15 SYZKALLER DAEMON.ERR DHCPCD[8025]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:16 SYZKALLER DAEMON.ERR DHCPCD[8026]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:16 SYZKALLER DAEMON.ERR DHCPCD[8026]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8027]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8027]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8028]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8028]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8029]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8029]: PS_ROOT_RECVMSG: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8030]: PS_BPF_START_BPF: BPF_OPEN: INVALID ARGUMENT
DEC 4 15:29:17 SYZKALLER DAEMON.ERR DHCPCD[8030]: PS_ROOT_RECVMSG: INVALID ARGUMENT
---
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.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-12-05 8:38 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=67516685.050a0220.17bd51.008c.GAE@google.com \
--to=syzbot+b3c08bda38b11fb7a6a0@syzkaller.appspotmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®