netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: syzbot <syzbot+7a942657a255a9d9b18a@syzkaller.appspotmail.com>
To: davem@davemloft.net, johannes@sipsolutions.net, kuba@kernel.org,
	linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: [syzbot] memory leak in cfg80211_inform_single_bss_frame_data
Date: Wed, 02 Jun 2021 09:37:27 -0700	[thread overview]
Message-ID: <000000000000f632ba05c3cb12c2@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    b90e90f4 Merge branch 'i2c/for-current' of git://git.kerne..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13bd382fd00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=b8c23f7848d1c696
dashboard link: https://syzkaller.appspot.com/bug?extid=7a942657a255a9d9b18a
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=131ce883d00000

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7a942657a255a9d9b18a@syzkaller.appspotmail.com

BUG: memory leak
unreferenced object 0xffff888119584780 (size 96):
  comm "kworker/u4:0", pid 8670, jiffies 4295047890 (age 8.810s)
  hex dump (first 32 bytes):
    fd f0 0a 3d 90 c3 05 00 00 00 00 00 00 00 00 00  ...=............
    00 00 00 00 00 00 00 00 28 00 00 00 01 00 06 10  ........(.......
  backtrace:
    [<ffffffff83e52709>] cfg80211_inform_single_bss_frame_data+0x139/0x640 net/wireless/scan.c:2376
    [<ffffffff83e52c5b>] cfg80211_inform_bss_frame_data+0x4b/0x470 net/wireless/scan.c:2437
    [<ffffffff83ef1d43>] ieee80211_bss_info_update+0x183/0x470 net/mac80211/scan.c:190
    [<ffffffff83eff43b>] ieee80211_rx_bss_info net/mac80211/ibss.c:1126 [inline]
    [<ffffffff83eff43b>] ieee80211_rx_mgmt_probe_beacon+0x60b/0x950 net/mac80211/ibss.c:1615
    [<ffffffff83effe8c>] ieee80211_ibss_rx_queued_mgmt+0x23c/0x6e0 net/mac80211/ibss.c:1642
    [<ffffffff83f01d76>] ieee80211_iface_work+0x476/0x5f0 net/mac80211/iface.c:1437
    [<ffffffff8125f9d9>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2276
    [<ffffffff812602c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2422
    [<ffffffff81267bf8>] kthread+0x178/0x1b0 kernel/kthread.c:313
    [<ffffffff810022ef>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

BUG: memory leak
unreferenced object 0xffff888119584680 (size 96):
  comm "kworker/u4:0", pid 8670, jiffies 4295048012 (age 7.590s)
  hex dump (first 32 bytes):
    f4 b0 1d 3d 90 c3 05 00 00 00 00 00 00 00 00 00  ...=............
    00 00 00 00 00 00 00 00 28 00 00 00 01 00 06 10  ........(.......
  backtrace:
    [<ffffffff83e52709>] cfg80211_inform_single_bss_frame_data+0x139/0x640 net/wireless/scan.c:2376
    [<ffffffff83e52c5b>] cfg80211_inform_bss_frame_data+0x4b/0x470 net/wireless/scan.c:2437
    [<ffffffff83ef1d43>] ieee80211_bss_info_update+0x183/0x470 net/mac80211/scan.c:190
    [<ffffffff83eff43b>] ieee80211_rx_bss_info net/mac80211/ibss.c:1126 [inline]
    [<ffffffff83eff43b>] ieee80211_rx_mgmt_probe_beacon+0x60b/0x950 net/mac80211/ibss.c:1615
    [<ffffffff83effe8c>] ieee80211_ibss_rx_queued_mgmt+0x23c/0x6e0 net/mac80211/ibss.c:1642
    [<ffffffff83f01d76>] ieee80211_iface_work+0x476/0x5f0 net/mac80211/iface.c:1437
    [<ffffffff8125f9d9>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2276
    [<ffffffff812602c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2422
    [<ffffffff81267bf8>] kthread+0x178/0x1b0 kernel/kthread.c:313
    [<ffffffff810022ef>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

BUG: memory leak
unreferenced object 0xffff888119584400 (size 96):
  comm "kworker/u4:0", pid 8670, jiffies 4295048012 (age 7.590s)
  hex dump (first 32 bytes):
    f5 b0 1d 3d 90 c3 05 00 00 00 00 00 00 00 00 00  ...=............
    00 00 00 00 00 00 00 00 28 00 00 00 01 00 06 10  ........(.......
  backtrace:
    [<ffffffff83e52709>] cfg80211_inform_single_bss_frame_data+0x139/0x640 net/wireless/scan.c:2376
    [<ffffffff83e52c5b>] cfg80211_inform_bss_frame_data+0x4b/0x470 net/wireless/scan.c:2437
    [<ffffffff83ef1d43>] ieee80211_bss_info_update+0x183/0x470 net/mac80211/scan.c:190
    [<ffffffff83eff43b>] ieee80211_rx_bss_info net/mac80211/ibss.c:1126 [inline]
    [<ffffffff83eff43b>] ieee80211_rx_mgmt_probe_beacon+0x60b/0x950 net/mac80211/ibss.c:1615
    [<ffffffff83effe8c>] ieee80211_ibss_rx_queued_mgmt+0x23c/0x6e0 net/mac80211/ibss.c:1642
    [<ffffffff83f01d76>] ieee80211_iface_work+0x476/0x5f0 net/mac80211/iface.c:1437
    [<ffffffff8125f9d9>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2276
    [<ffffffff812602c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2422
    [<ffffffff81267bf8>] kthread+0x178/0x1b0 kernel/kthread.c:313
    [<ffffffff810022ef>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294

BUG: memory leak
unreferenced object 0xffff8881196dda80 (size 96):
  comm "kworker/u4:1", pid 8689, jiffies 4295048023 (age 7.480s)
  hex dump (first 32 bytes):
    e4 40 1f 3d 90 c3 05 00 00 00 00 00 00 00 00 00  .@.=............
    00 00 00 00 00 00 00 00 28 00 00 00 01 00 06 10  ........(.......
  backtrace:
    [<ffffffff83e52709>] cfg80211_inform_single_bss_frame_data+0x139/0x640 net/wireless/scan.c:2376
    [<ffffffff83e52c5b>] cfg80211_inform_bss_frame_data+0x4b/0x470 net/wireless/scan.c:2437
    [<ffffffff83ef1d43>] ieee80211_bss_info_update+0x183/0x470 net/mac80211/scan.c:190
    [<ffffffff83eff43b>] ieee80211_rx_bss_info net/mac80211/ibss.c:1126 [inline]
    [<ffffffff83eff43b>] ieee80211_rx_mgmt_probe_beacon+0x60b/0x950 net/mac80211/ibss.c:1615
    [<ffffffff83effe8c>] ieee80211_ibss_rx_queued_mgmt+0x23c/0x6e0 net/mac80211/ibss.c:1642
    [<ffffffff83f01d76>] ieee80211_iface_work+0x476/0x5f0 net/mac80211/iface.c:1437
    [<ffffffff8125f9d9>] process_one_work+0x2c9/0x600 kernel/workqueue.c:2276
    [<ffffffff812602c9>] worker_thread+0x59/0x5d0 kernel/workqueue.c:2422
    [<ffffffff81267bf8>] kthread+0x178/0x1b0 kernel/kthread.c:313
    [<ffffffff810022ef>] ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294



---
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.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches

             reply	other threads:[~2021-06-02 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 16:37 syzbot [this message]
2021-10-25 22:33 ` [syzbot] memory leak in cfg80211_inform_single_bss_frame_data syzbot
2021-10-26  9:27   ` Fabio M. De Francesco
2022-07-13  8:56 ` Siddh Raman Pant
2022-07-13  8:58   ` Siddh Raman Pant
2022-07-13  9:08     ` syzbot
2022-07-13 10:25       ` Siddh Raman Pant
2022-07-13 10:35         ` syzbot

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=000000000000f632ba05c3cb12c2@google.com \
    --to=syzbot+7a942657a255a9d9b18a@syzkaller.appspotmail.com \
    --cc=davem@davemloft.net \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@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 NNTP newsgroup(s).