public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+878ddc3962f792e9af59@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: Re: [syzbot] [wireless?] KMSAN: uninit-value in cfg80211_classify8021d
Date: Wed, 12 Nov 2025 09:32:07 -0800	[thread overview]
Message-ID: <6914c497.a70a0220.3124cb.000a.GAE@google.com> (raw)
In-Reply-To: <68f6a48f.050a0220.91a22.0453.GAE@google.com>

For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.

***

Subject: Re: [syzbot] [wireless?] KMSAN: uninit-value in cfg80211_classify8021d
Author: vnranganath.20@gmail.com

#syz test
diff --git a/net/wireless/util.c b/net/wireless/util.c
index 56724b33af04..f2a6644d854e 100644
--- a/net/wireless/util.c
+++ b/net/wireless/util.c
@@ -963,9 +963,23 @@ unsigned int cfg80211_classify8021d(struct sk_buff *skb,

        switch (skb->protocol) {
        case htons(ETH_P_IP):
+               struct iphdr iph, *ip;
+
+               ip = skb_header_pointer(skb, sizeof(struct ethhdr),
+                                       sizeof(*ip), &iph);
+               if (!ip)
+                       return 0;
+
                dscp = ipv4_get_dsfield(ip_hdr(skb)) & 0xfc;
                break;
        case htons(ETH_P_IPV6):
+               struct ipv6hdr ip6h, *ip6;
+
+               ip6 = skb_header_pointer(skb, sizeof(struct ethhdr),
+                                        sizeof(*ip6), &ip6h);
+               if (!ip6)
+                       return 0;
+
                dscp = ipv6_get_dsfield(ipv6_hdr(skb)) & 0xfc;
                break;
        case htons(ETH_P_MPLS_UC):

On Wed, Nov 12, 2025 at 9:52 PM syzbot
<syzbot+878ddc3962f792e9af59@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot tried to test the proposed patch but the build/boot failed:
>
> failed to apply patch:
> checking file net/wireless/util.c
> Hunk #1 FAILED at 963.
> 1 out of 1 hunk FAILED
>
>
>
> Tested on:
>
> commit:         24172e0d Merge tag 'arm64-fixes' of git://git.kernel.o..
> git tree:       upstream
> kernel config:  https://syzkaller.appspot.com/x/.config?x=bbd3e7f3c2e28265
> dashboard link: https://syzkaller.appspot.com/bug?extid=878ddc3962f792e9af59
> compiler:
> patch:          https://syzkaller.appspot.com/x/patch.diff?x=15358692580000
>
> --
> You received this message because you are subscribed to the Google Groups "syzkaller-bugs" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to syzkaller-bugs+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/syzkaller-bugs/6914b42d.a70a0220.3124cb.0008.GAE%40google.com.

      parent reply	other threads:[~2025-11-12 17:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 21:07 [syzbot] [wireless?] KMSAN: uninit-value in cfg80211_classify8021d syzbot
2025-10-21 11:57 ` Forwarded: " syzbot
2025-10-21 17:14 ` syzbot
2025-11-01 17:41 ` Forwarded: " syzbot
2025-11-11 19:18 ` Forwarded: test " syzbot
2025-11-12 13:09 ` Forwarded: " syzbot
2025-11-12 15:51 ` Forwarded: Re: [syzbot] [wireless?] " syzbot
2025-11-12 17:32 ` syzbot [this message]

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=6914c497.a70a0220.3124cb.000a.GAE@google.com \
    --to=syzbot+878ddc3962f792e9af59@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