The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+30754ca335e6fb7e3092@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [wireless?] KASAN: slab-use-after-free Read in cmp_bss
Date: Tue, 12 Aug 2025 13:08:28 +0800	[thread overview]
Message-ID: <20250812050829.4213-1-hdanton@sina.com> (raw)
In-Reply-To: <689a3d93.050a0220.7f033.0100.GAE@google.com>

> Date: Mon, 11 Aug 2025 11:59:31 -0700	[thread overview]
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:    c30a13538d9f Merge tag 'bpf-fixes' of git://git.kernel.org..
> git tree:       upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17840842580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=e143c1cd9dadd720
> dashboard link: https://syzkaller.appspot.com/bug?extid=30754ca335e6fb7e3092
> syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=1766fea2580000
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15e709a2580000

#syz test

--- x/net/wireless/scan.c
+++ y/net/wireless/scan.c
@@ -1904,19 +1904,6 @@ cfg80211_update_known_bss(struct cfg8021
 
 		if (known->pub.hidden_beacon_bss &&
 		    !list_empty(&known->hidden_list)) {
-			const struct cfg80211_bss_ies *f;
-
-			/* The known BSS struct is one of the probe
-			 * response members of a group, but we're
-			 * receiving a beacon (beacon_ies in the new
-			 * bss is used). This can only mean that the
-			 * AP changed its beacon from not having an
-			 * SSID to showing it, which is confusing so
-			 * drop this information.
-			 */
-
-			f = rcu_access_pointer(new->pub.beacon_ies);
-			kfree_rcu((struct cfg80211_bss_ies *)f, rcu_head);
 			return false;
 		}
 
--

  parent reply	other threads:[~2025-08-12  5:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 18:59 [syzbot] [wireless?] KASAN: slab-use-after-free Read in cmp_bss syzbot
2025-08-12  1:16 ` Edward Adam Davis
2025-08-12  1:39   ` syzbot
2025-08-12  5:08 ` Hillf Danton [this message]
2025-08-12  5:31   ` syzbot
2025-08-12  8:49 ` Forwarded: #syz test https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 53e760d8949895390e256e723e7ee46618310361 syzbot
2025-08-12 11:53 ` syzbot
     [not found] <d4f0bd47-06b1-4841-924d-607386e733d4@yandex.ru>
2025-08-12  9:11 ` [syzbot] [wireless?] KASAN: slab-use-after-free Read in cmp_bss syzbot
     [not found] <0d6fdeba-3bdc-4b23-bc60-eb639e628947@yandex.ru>
2025-08-12 12:19 ` 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=20250812050829.4213-1-hdanton@sina.com \
    --to=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=syzbot+30754ca335e6fb7e3092@syzkaller.appspotmail.com \
    --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