| Seq | Timestamp | Type | Name | Duration |
|---|---|---|---|---|
| 0/0 | 2026/09/21 08:44 | flow | patch-triage |
9mArgs:null Results: {
"EnableConfigs": [
"CFG80211",
"MAC80211",
"MAC80211_HWSIM"
],
"FocusSymbols": [
"nl80211_set_wiphy"
],
"KMSANReasoning": "The patch resolves a logic bug in nl80211_set_wiphy() where rdev-\u003ewiphy.rts_threshold was not being updated when old_radio_rts_threshold was NULL (i.e. when rdev-\u003ewiphy.n_radio is 0). The change separates updating rdev-\u003ewiphy.rts_threshold from iterating over the per-radio config.\n\nThe variable rts_threshold is always initialized from the netlink attribute NL80211_ATTR_WIPHY_RTS_THRESHOLD whenever WIPHY_PARAM_RTS_THRESHOLD is set in changed. The patch introduces no uninitialized memory, does not alter buffer bounds or memory copying to user space, and does not branch on uninitialized values. Therefore, there are no uninitialized memory risks that require a dedicated KMSAN fuzzing session.",
"NeedsKMSAN": false,
"Reasoning": "The patch modifies state management in nl80211_set_wiphy() by ensuring that rdev-\u003ewiphy.rts_threshold is updated whenever WIPHY_PARAM_RTS_THRESHOLD is specified, regardless of whether old_radio_rts_threshold is allocated (e.g., when n_radio is 0). This modifies reachable generic netlink configuration code in cfg80211 which can be exercised using simulated wireless hardware such as mac80211_hwsim.",
"WorthFuzzing": true
} |
| 1/1 | 2026/09/21 08:44 | action | read-patch-diff |
0mArgs:null Results: {
"PatchDiff": "commit 0829d2d4bbce133b8b5c786a33950875ebeb2b80\nAuthor: syz-cluster \u003ctriage@syzkaller.com\u003e\nDate: Mon Sep 21 08:44:18 2026 +0000\n\n syz-cluster: applied patch under review\n\ndiff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c\nindex 899b6374c5506..f75206332eaac 100644\n--- a/net/wireless/nl80211.c\n+++ b/net/wireless/nl80211.c\n@@ -4563,12 +4563,13 @@ static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)\n \t\t\trdev-\u003ewiphy.retry_long = retry_long;\n \t\tif (changed \u0026 WIPHY_PARAM_FRAG_THRESHOLD)\n \t\t\trdev-\u003ewiphy.frag_threshold = frag_threshold;\n-\t\tif ((changed \u0026 WIPHY_PARAM_RTS_THRESHOLD) \u0026\u0026\n-\t\t old_radio_rts_threshold) {\n+\t\tif (changed \u0026 WIPHY_PARAM_RTS_THRESHOLD) {\n \t\t\trdev-\u003ewiphy.rts_threshold = rts_threshold;\n-\t\t\tfor (i = 0 ; i \u003c rdev-\u003ewiphy.n_radio; i++)\n-\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n-\t\t\t\t\trdev-\u003ewiphy.rts_threshold;\n+\t\t\tif (old_radio_rts_threshold) {\n+\t\t\t\tfor (i = 0; i \u003c rdev-\u003ewiphy.n_radio; i++)\n+\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n+\t\t\t\t\t\trdev-\u003ewiphy.rts_threshold;\n+\t\t\t}\n \t\t}\n \t\tif (changed \u0026 WIPHY_PARAM_COVERAGE_CLASS)\n \t\t\trdev-\u003ewiphy.coverage_class = coverage_class;\n"
} |
| 2/1 | 2026/09/21 08:44 | agent | patch-evaluator |
8mModel:core Args: null Results: {
"EnableConfigs": [
"CFG80211",
"MAC80211",
"MAC80211_HWSIM"
],
"FocusSymbols": [
"nl80211_set_wiphy"
],
"Reasoning": "The patch modifies state management in nl80211_set_wiphy() by ensuring that rdev-\u003ewiphy.rts_threshold is updated whenever WIPHY_PARAM_RTS_THRESHOLD is specified, regardless of whether old_radio_rts_threshold is allocated (e.g., when n_radio is 0). This modifies reachable generic netlink configuration code in cfg80211 which can be exercised using simulated wireless hardware such as mac80211_hwsim.",
"WorthFuzzing": true
}Instruction: You are an expert Linux kernel maintainer and security engineer.
Your job is to review a provided patch series and evaluate whether it warrants fuzzing with syzkaller.
IMPORTANT: The changes have ALREADY been applied and committed as the HEAD commit in
your workspace. Do NOT rely on internal assumptions. You must actively use your code access
tools to inspect the actual source code, callers, and surrounding context.
================================================================================
1. CORE TRIAGE PHILOSOPHY
================================================================================
The goal of patch fuzzing is to discover crashes, regressions, exposed latent bugs,
and newly triggered assertions introduced by the patch series.
- REACHABILITY IS THE PRIMARY GATE:
Fuzzing can only discover bugs in code that can actually execute in standard virtualized
environments (GCE or QEMU, utilizing software-emulated devices like USB gadgets, netdev, tun/tap).
If the modified code is structurally unreachable (see Section 2), it MUST NOT be fuzzed,
regardless of whether it adds assertions or complex logic.
- DO NOT BLINDLY TRUST "NO FUNCTIONAL CHANGE" (NFCI) OR "REFACTORING" CLAIMS:
Patch authors routinely label changes as "cleanups", "refactorings", or state
"No functional change intended". Do NOT take these claims at face value.
Code refactorings that rearrange logic, introduce helper functions, or alter state management
in core subsystems frequently introduce subtle semantic shifts or uncover latent kernel bugs.
If reachable executable code is modified or refactored, it MUST be fuzzed.
- NEW OR MODIFIED ASSERTIONS IN REACHABLE CODE MUST BE FUZZED:
When a patch introduces or modifies runtime checks or assertions (e.g., WARN_ON*, VM_WARN_ON*,
BUG_ON*, lockdep_assert*) in reachable code paths, it enforces new or stricter invariants.
Even if the author believes the invariant always holds, fuzzing is essential to verify whether
an unusual sequence of operations can violate it.
================================================================================
2. WHEN TO RETURN WorthFuzzing=false (NEGATIVE CRITERIA)
================================================================================
Return WorthFuzzing=false ONLY IF all modified code falls strictly into one or more of these categories:
- Non-kernel and non-executable changes:
* Modifications to Documentation/, comments, or spelling fixes.
* User-space directories, self-tests, samples, or scripts (e.g., tools/, samples/, scripts/, usr/)
that do not affect the compiled kernel image (vmlinux) or kernel modules.
* Purely decorative logging (e.g., message strings in pr_err, printk, dev_info) or tracepoints
that do not alter control flow or data structures.
* Build system or Kconfig changes that do not alter compiled C logic.
- Structurally unreachable hardware:
* Vendor-specific PCIe switches, SmartNICs, or GPU drivers (e.g., mlxsw, pds_core, qed,
ionic, amdgpu) requiring physical ASIC/PCIe cards not emulated in standard QEMU.
- Unreachable execution paths:
* Driver teardown callbacks (.remove, .shutdown, pci_unregister_driver) executed only during
physical PCI hot-unplug or manual sysfs driver unbinding.
* Code paths exclusive to architectures other than the target architecture.
================================================================================
3. WHEN TO RETURN WorthFuzzing=true (POSITIVE CRITERIA)
================================================================================
Return WorthFuzzing=true whenever the patch touches reachable executable code, including:
- Core Subsystems:
* Any logic modifications in memory management (mm/), synchronization/locking (kernel/locking/),
BPF, scheduler, core networking, VFS, or syscall handling.
- Refactorings and Code Cleanups:
* Any restructuring of reachable data structures, helper abstractions, or algorithm flows.
- Runtime Assertions and Defensive Checks:
* Any introduction or alteration of assertions (WARN_ON*, VM_WARN_ON*, BUG_ON*, etc.) in reachable paths.
- Reachable Drivers and Protocols:
* Drivers accessible via virtual buses (virtio, USB gadget, loopback, netlink, binder, sockets, etc.).
================================================================================
4. EXTRACTING FocusSymbols (PREVENTING DILUTION)
================================================================================
When WorthFuzzing=true, you must extract specific kernel functions into FocusSymbols to guide the fuzzer:
- AVOID UBIQUITOUS LIFECYCLE HOT-PATHS:
Do NOT list generic, ubiquitous functions called by almost every program in the corpus
(including, but not limited to: general memory allocators and deallocators, page fault
and trap handlers, or core synchronization primitives; this is not an exhaustive list).
Listing ubiquitous functions causes the fuzzer to classify thousands of unrelated tests as "focused",
which severely dilutes fuzzing effort away from the actual changes.
- TARGET SPECIFIC FEATURE LOGIC AND ENTRYPOINTS:
List functions that specifically implement the logic being added or altered, or direct API entrypoints
for the subsystem feature under review.
- HANDLING STATIC INLINE FUNCTIONS IN HEADERS (.h):
Compiler-inlined static functions (such as static inlines in mm/*.h or include/linux/*.h) lack
distinct symbol addresses in vmlinux and cannot be targeted directly by symbol coverage filters.
If the changes are primarily in static inline helpers, identify non-static, feature-specific caller
functions in .c files that exercise them (avoiding ubiquitous lifecycle wrappers).
================================================================================
5. IDENTIFYING EnableConfigs
================================================================================
Identify any specific CONFIG_ options required to properly compile and reach the modified code:
- Inspect Kconfig files and #ifdef guards; do not make assumptions.
- Check "depends on" lines in Kconfig to include any non-standard parent subsystem configs needed.
- Strip any 'CONFIG_' prefix (e.g., return "NET_IPV4" instead of "CONFIG_NET_IPV4").
Prefer calling several tools at the same time to save round-trips.
Use set-results tool to provide results of the analysis.
It must be called exactly once before the final reply.
Ignore results of this tool.
Prompt: Target architecture: amd64
For your convenience, here is the diff of the changes:
commit 0829d2d4bbce133b8b5c786a33950875ebeb2b80
Author: syz-cluster <triage@syzkaller.com>
Date: Mon Sep 21 08:44:18 2026 +0000
syz-cluster: applied patch under review
diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 899b6374c5506..f75206332eaac 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@ -4563,12 +4563,13 @@ static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)
rdev->wiphy.retry_long = retry_long;
if (changed & WIPHY_PARAM_FRAG_THRESHOLD)
rdev->wiphy.frag_threshold = frag_threshold;
- if ((changed & WIPHY_PARAM_RTS_THRESHOLD) &&
- old_radio_rts_threshold) {
+ if (changed & WIPHY_PARAM_RTS_THRESHOLD) {
rdev->wiphy.rts_threshold = rts_threshold;
- for (i = 0 ; i < rdev->wiphy.n_radio; i++)
- rdev->wiphy.radio_cfg[i].rts_threshold =
- rdev->wiphy.rts_threshold;
+ if (old_radio_rts_threshold) {
+ for (i = 0; i < rdev->wiphy.n_radio; i++)
+ rdev->wiphy.radio_cfg[i].rts_threshold =
+ rdev->wiphy.rts_threshold;
+ }
}
if (changed & WIPHY_PARAM_COVERAGE_CLASS)
rdev->wiphy.coverage_class = coverage_class;
|
| 3/2 | 2026/09/21 08:44 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 3103 output: 41 thoughts: 506 Thoughts: **Analyzing the NL80211 Patch** Okay, let's dive into this. First, I need to understand what's being changed, so I'll start by reviewing the patch itself. It looks like we're modifying `net/wireless/nl80211.c`, specifically around line 4563. The `diff` shows additions and subtractions related to setting Wi-Fi parameters. It's a fairly focused change, which is good. Let me take a closer look at the key part. It looks like it's addressing how we handle the `RTS_THRESHOLD` parameter. There's a conditional change around the `rdev->wiphy.rts_threshold` setting and the subsequent iteration through `rdev->wiphy.radio_cfg[i].rts_threshold`. The original code appears to only update the radio configuration if `old_radio_rts_threshold` was non-zero. The patch slightly changes the conditional logic. Interesting. I see that `old_radio_rts_threshold` isn't used as a check for whether to *set* the `rts_threshold` itself, which could be an issue. However, the patch seems to have moved the condition to *only* iterate and configure the individual radios, which, depending on how this driver works, is likely the desired behavior. I'll need to double check the context here. To get the full picture, I should probably read the surrounding code in `net/wireless/nl80211.c` around line 4563 to understand the exact flow and data structures involved. Specifically, I'll examine how these Wi-Fi parameters are set and how the `rdev` struct is initialized and used. I'll need to know the implications of updating `rts_threshold` and how it's linked to the radio configuration. Time to pull that file and check the relevant functions. |
| 4/2 | 2026/09/21 08:44 | tool | read-file |
0mArgs:{
"File": "net/wireless/nl80211.c",
"FirstLine": 4520,
"LineCount": 80
}Results: {
"Contents": "4520:\t\t\t\t\t\t NL80211_EXT_FEATURE_TXQS))\n4521:\t\t\t\treturn -EOPNOTSUPP;\n4522:\t\n4523:\t\t\ttxq_quantum = nla_get_u32(\n4524:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_TXQ_QUANTUM]);\n4525:\t\t\tchanged |= WIPHY_PARAM_TXQ_QUANTUM;\n4526:\t\t}\n4527:\t\n4528:\t\tif (changed) {\n4529:\t\t\tu8 old_retry_short, old_retry_long;\n4530:\t\t\tu32 old_frag_threshold, old_rts_threshold;\n4531:\t\t\tu8 old_coverage_class, i;\n4532:\t\t\tu32 old_txq_limit, old_txq_memory_limit, old_txq_quantum;\n4533:\t\t\tu32 *old_radio_rts_threshold = NULL;\n4534:\t\n4535:\t\t\tif (!rdev-\u003eops-\u003eset_wiphy_params)\n4536:\t\t\t\treturn -EOPNOTSUPP;\n4537:\t\n4538:\t\t\tif (rdev-\u003ewiphy.n_radio) {\n4539:\t\t\t\told_radio_rts_threshold = kcalloc(rdev-\u003ewiphy.n_radio,\n4540:\t\t\t\t\t\t\t\t sizeof(u32),\n4541:\t\t\t\t\t\t\t\t GFP_KERNEL);\n4542:\t\t\t\tif (!old_radio_rts_threshold)\n4543:\t\t\t\t\treturn -ENOMEM;\n4544:\t\t\t}\n4545:\t\n4546:\t\t\told_retry_short = rdev-\u003ewiphy.retry_short;\n4547:\t\t\told_retry_long = rdev-\u003ewiphy.retry_long;\n4548:\t\t\told_frag_threshold = rdev-\u003ewiphy.frag_threshold;\n4549:\t\t\told_rts_threshold = rdev-\u003ewiphy.rts_threshold;\n4550:\t\t\tif (old_radio_rts_threshold) {\n4551:\t\t\t\tfor (i = 0 ; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4552:\t\t\t\t\told_radio_rts_threshold[i] =\n4553:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold;\n4554:\t\t\t}\n4555:\t\t\told_coverage_class = rdev-\u003ewiphy.coverage_class;\n4556:\t\t\told_txq_limit = rdev-\u003ewiphy.txq_limit;\n4557:\t\t\told_txq_memory_limit = rdev-\u003ewiphy.txq_memory_limit;\n4558:\t\t\told_txq_quantum = rdev-\u003ewiphy.txq_quantum;\n4559:\t\n4560:\t\t\tif (changed \u0026 WIPHY_PARAM_RETRY_SHORT)\n4561:\t\t\t\trdev-\u003ewiphy.retry_short = retry_short;\n4562:\t\t\tif (changed \u0026 WIPHY_PARAM_RETRY_LONG)\n4563:\t\t\t\trdev-\u003ewiphy.retry_long = retry_long;\n4564:\t\t\tif (changed \u0026 WIPHY_PARAM_FRAG_THRESHOLD)\n4565:\t\t\t\trdev-\u003ewiphy.frag_threshold = frag_threshold;\n4566:\t\t\tif (changed \u0026 WIPHY_PARAM_RTS_THRESHOLD) {\n4567:\t\t\t\trdev-\u003ewiphy.rts_threshold = rts_threshold;\n4568:\t\t\t\tif (old_radio_rts_threshold) {\n4569:\t\t\t\t\tfor (i = 0; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4570:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n4571:\t\t\t\t\t\t\trdev-\u003ewiphy.rts_threshold;\n4572:\t\t\t\t}\n4573:\t\t\t}\n4574:\t\t\tif (changed \u0026 WIPHY_PARAM_COVERAGE_CLASS)\n4575:\t\t\t\trdev-\u003ewiphy.coverage_class = coverage_class;\n4576:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_LIMIT)\n4577:\t\t\t\trdev-\u003ewiphy.txq_limit = txq_limit;\n4578:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_MEMORY_LIMIT)\n4579:\t\t\t\trdev-\u003ewiphy.txq_memory_limit = txq_memory_limit;\n4580:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_QUANTUM)\n4581:\t\t\t\trdev-\u003ewiphy.txq_quantum = txq_quantum;\n4582:\t\n4583:\t\t\tresult = rdev_set_wiphy_params(rdev, radio_idx, changed);\n4584:\t\t\tif (result) {\n4585:\t\t\t\trdev-\u003ewiphy.retry_short = old_retry_short;\n4586:\t\t\t\trdev-\u003ewiphy.retry_long = old_retry_long;\n4587:\t\t\t\trdev-\u003ewiphy.frag_threshold = old_frag_threshold;\n4588:\t\t\t\trdev-\u003ewiphy.rts_threshold = old_rts_threshold;\n4589:\t\t\t\tif (old_radio_rts_threshold) {\n4590:\t\t\t\t\tfor (i = 0 ; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4591:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n4592:\t\t\t\t\t\t\told_radio_rts_threshold[i];\n4593:\t\t\t\t}\n4594:\t\t\t\trdev-\u003ewiphy.coverage_class = old_coverage_class;\n4595:\t\t\t\trdev-\u003ewiphy.txq_limit = old_txq_limit;\n4596:\t\t\t\trdev-\u003ewiphy.txq_memory_limit = old_txq_memory_limit;\n4597:\t\t\t\trdev-\u003ewiphy.txq_quantum = old_txq_quantum;\n4598:\t\t\t}\n4599:\t\n"
} |
| 5/2 | 2026/09/21 08:44 | llm | patch-evaluator |
7mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 5616 output: 31 thoughts: 751 Thoughts: **Analyzing the RTS Threshold Bug and its Implications** Okay, so I've been looking closely at this code and how it handles the RTS threshold setting. Before the patch, I can see that if `rdev->wiphy.n_radio` was zero – meaning either a single radio, no multi-radio support, or a virtual/simulated device without separate radio configurations – the `old_radio_rts_threshold` pointer would be NULL. The crucial thing here is that under those circumstances, the line setting the overall `rdev->wiphy.rts_threshold = rts_threshold;` was *never* executed. Effectively, setting the RTS threshold wouldn't actually change the value. The patch corrects this by ensuring that the `rts_threshold` is always set, regardless of `n_radio`. I also noticed the rollback logic. When an error occurs (`result != 0`), the code reverts the `rts_threshold` to its old value. This rollback uses `old_rts_threshold` and, if available, `old_radio_rts_threshold`. So, the previous behavior meant the old threshold was never properly restored in the cases where the main threshold was not initially set. Now, a key question for me is reachability. Is `nl80211_set_wiphy` accessible in common fuzzing setups like QEMU or GCE? The answer is a resounding yes. `nl80211` is the standard Netlink interface for 802.11 configuration. Devices like `mac80211_hwsim`, `virt_wifi`, or even dummy wiphy devices are often used in fuzzing environments. Syzkaller, in particular, heavily fuzzed `NL80211_CMD_SET_WIPHY`, so this area is clearly exposed to fuzzing. It's a prime target for vulnerability detection. Finally, I'm going to take a look at the kernel configuration options to confirm the minimum requirements to make sure I am accounting for everything. I will examine `net/wireless/Kconfig` to see if there are any subtle dependencies that need to be accounted for. |
| 6/2 | 2026/09/21 08:52 | tool | grepper |
0mArgs:{
"Expression": "config NL80211",
"PathPrefix": "net/wireless/"
}Results: {
"Output": "net/wireless/Kconfig=36=if CFG80211\nnet/wireless/Kconfig-37-\nnet/wireless/Kconfig:38:config NL80211_TESTMODE\nnet/wireless/Kconfig-39-\tbool \"nl80211 testmode command\"\n"
} |
| 7/2 | 2026/09/21 08:52 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 6954 output: 31 thoughts: 27 Thoughts: Here's my take on those thoughts, tailored for an expert audience: **Diving into the Build Process of `nl80211.c`** Okay, so I need to understand how `nl80211.c` is integrated into the kernel's wireless subsystem. The most logical place to start digging is the `net/wireless/Makefile`. This is the central repository for the build instructions related to that part of the kernel, and it's where I can likely trace the dependencies and compilation flags that bring `nl80211.c` to life. I need to figure out the specific targets, object file dependencies, and any conditional compilation that might be going on, especially in relation to other wireless drivers or features. It's time to fire up my editor and see what the Makefile reveals. I expect to see the standard object file inclusion and linking, but I'm also interested in any more specific build parameters; and how this module relates to the larger wireless networking framework. |
| 8/2 | 2026/09/21 08:52 | tool | read-file |
0mArgs:{
"File": "net/wireless/Makefile",
"FirstLine": 1,
"LineCount": 40
}Results: {
"Contents": " 1:\t# SPDX-License-Identifier: GPL-2.0\n 2:\tobj-$(CONFIG_CFG80211) += cfg80211.o\n 3:\tobj-y += tests/\n 4:\t\n 5:\tobj-$(CONFIG_WEXT_CORE) += wext-core.o\n 6:\tobj-$(CONFIG_WEXT_PROC) += wext-proc.o\n 7:\tobj-$(CONFIG_WEXT_PRIV) += wext-priv.o\n 8:\t\n 9:\tcfg80211-y += core.o sysfs.o radiotap.o util.o reg.o scan.o nl80211.o\n 10:\tcfg80211-y += mlme.o ibss.o sme.o chan.o ethtool.o mesh.o ap.o trace.o ocb.o\n 11:\tcfg80211-y += michael-mic.o pmsr.o\n 12:\tcfg80211-$(CONFIG_OF) += of.o\n 13:\tcfg80211-$(CONFIG_CFG80211_DEBUGFS) += debugfs.o\n 14:\tcfg80211-$(CONFIG_CFG80211_WEXT) += wext-compat.o wext-sme.o\n 15:\t\n 16:\tCFLAGS_trace.o := -I$(src)\n 17:\t\n 18:\tcfg80211-$(CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS) += shipped-certs.o\n 19:\tifneq ($(CONFIG_CFG80211_EXTRA_REGDB_KEYDIR),)\n 20:\tcfg80211-y += extra-certs.o\n 21:\tendif\n 22:\t\n 23:\t$(obj)/shipped-certs.c: $(sort $(wildcard $(src)/certs/*.hex))\n 24:\t\t@$(kecho) \" GEN $@\"\n 25:\t\t$(Q)(echo '#include \"reg.h\"'; \\\n 26:\t\t echo 'const u8 shipped_regdb_certs[] = {'; \\\n 27:\t\t echo | cat - $^ ; \\\n 28:\t\t echo '};'; \\\n 29:\t\t echo 'unsigned int shipped_regdb_certs_len = sizeof(shipped_regdb_certs);'; \\\n 30:\t\t ) \u003e $@\n 31:\t\n 32:\t$(obj)/extra-certs.c: $(CONFIG_CFG80211_EXTRA_REGDB_KEYDIR) \\\n 33:\t\t\t $(sort $(wildcard $(CONFIG_CFG80211_EXTRA_REGDB_KEYDIR)/*.x509))\n 34:\t\t@$(kecho) \" GEN $@\"\n 35:\t\t$(Q)(set -e; \\\n 36:\t\t allf=\"\"; \\\n 37:\t\t for f in $^ ; do \\\n 38:\t\t test -f $$f || continue;\\\n 39:\t\t # similar to hexdump -v -e '1/1 \"0x%.2x,\" \"\\n\"' \\\n 40:\t\t thisf=$$(od -An -v -tx1 \u003c $$f | \\\n"
} |
| 9/2 | 2026/09/21 08:52 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 8068 output: 32 thoughts: 49 Thoughts: Okay, here's my interpretation of that thought process, tailored for an expert audience: **Kernel Module Investigation: `nl80211.o` and `CONFIG_CFG80211`** Right, so I'm looking at `nl80211.o`. My gut tells me that's probably tied into `CONFIG_CFG80211`. That's the go-to for wireless configuration, so it makes sense. I need to confirm that relationship, though. Time to pop open `net/wireless/Kconfig`. That's where I'll find the configuration options. I'll quickly check if `CONFIG_CFG80211` is defined there and how `nl80211.o` factors into it. This is a pretty standard debugging step - tracing dependencies to understand the build configuration. |
| 10/2 | 2026/09/21 08:52 | tool | read-file |
0mArgs:{
"File": "net/wireless/Kconfig",
"FirstLine": 1,
"LineCount": 40
}Results: {
"Contents": " 1:\t# SPDX-License-Identifier: GPL-2.0-only\n 2:\tconfig WIRELESS_EXT\n 3:\t\tbool\n 4:\t\n 5:\tconfig WEXT_CORE\n 6:\t\tdef_bool y\n 7:\t\tdepends on CFG80211_WEXT || WIRELESS_EXT\n 8:\t\n 9:\tconfig WEXT_PROC\n 10:\t\tdef_bool y\n 11:\t\tdepends on PROC_FS\n 12:\t\tdepends on WEXT_CORE\n 13:\t\n 14:\tconfig WEXT_PRIV\n 15:\t\tbool\n 16:\t\n 17:\tconfig CFG80211\n 18:\t\ttristate \"cfg80211 - wireless configuration API\"\n 19:\t\tdepends on RFKILL || !RFKILL\n 20:\t\tselect FW_LOADER\n 21:\t\tselect CRC32\n 22:\t\t# may need to update this when certificates are changed and are\n 23:\t\t# using a different algorithm, though right now they shouldn't\n 24:\t\t# (this is here rather than below to allow it to be a module)\n 25:\t\tselect CRYPTO_SHA256 if CFG80211_USE_KERNEL_REGDB_KEYS\n 26:\t\thelp\n 27:\t\t cfg80211 is the Linux wireless LAN (802.11) configuration API.\n 28:\t\t Enable this if you have a wireless device.\n 29:\t\n 30:\t\t For more information refer to documentation on the wireless wiki:\n 31:\t\n 32:\t\t https://wireless.wiki.kernel.org/en/developers/Documentation/cfg80211\n 33:\t\n 34:\t\t When built as a module it will be called cfg80211.\n 35:\t\n 36:\tif CFG80211\n 37:\t\n 38:\tconfig NL80211_TESTMODE\n 39:\t\tbool \"nl80211 testmode command\"\n 40:\t\thelp\n"
} |
| 11/2 | 2026/09/21 08:52 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 8877 output: 37 thoughts: 86 Thoughts: Here's my thought process, as an expert in this area: **Investigating the Configuration for Simulated Wireless Devices** Okay, so I'm dealing with simulated wireless devices, and I need to figure out the right configuration. From my experience, both `CFG80211` and `MAC80211_HWSIM` are likely candidates. In this context, `CFG80211` is the core configuration framework to look at. However, the simulation part usually involves `MAC80211_HWSIM`. I'll need to check the interactions between those two. To get the specifics, my next step is clear: I'll dive into the driver code for the hardware simulation. That would be `drivers/net/wireless/virtual/mac80211_hwsim.c`, or something closely related if the file name has been altered. I'll need to understand how the simulation layer hooks into the broader wireless stack. That's where the magic, or potential issues, will probably reside. |
| 12/2 | 2026/09/21 08:52 | tool | grepper |
0mArgs:{
"Expression": "config MAC80211_HWSIM",
"PathPrefix": "drivers/net/wireless/"
}Results: {
"Output": "drivers/net/wireless/virtual/Kconfig:1:config MAC80211_HWSIM\ndrivers/net/wireless/virtual/Kconfig-2-\ttristate \"Simulated radio testing tool for mac80211\"\n"
} |
| 13/2 | 2026/09/21 08:52 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 9295 output: 43 thoughts: 112 Thoughts: **Analyzing Syzkaller's nl80211 Coverage** Okay, so I'm diving into the `nl80211` coverage within Syzkaller. My initial thought is to confirm whether the `nl80211` commands have been explicitly defined in syzlang. It looks like Syzkaller has a pretty good handle on describing the `nl80211` generic netlink family which is a relief. Specifically, I see that `nl80211_set_wiphy` is used, and it's associated with `NL80211_CMD_SET_WIPHY`. Now, my next move is to crack open `nl80211.c`. I need to cross-reference this function call to confirm the way it's used. By looking at where `nl80211_set_wiphy` is called, I can verify the syzkaller description and get a better understanding of how syzkaller can reach it. |
| 14/2 | 2026/09/21 08:52 | tool | grepper |
0mArgs:{
"Expression": "nl80211_set_wiphy",
"PathPrefix": "net/wireless/nl80211.c"
}Results: {
"Output": "net/wireless/nl80211.c=4209=static int nl80211_set_channel(struct sk_buff *skb, struct genl_info *info)\n--\nnet/wireless/nl80211.c-4217-\nnet/wireless/nl80211.c:4218:static int nl80211_set_wiphy_radio(struct genl_info *info,\nnet/wireless/nl80211.c-4219-\t\t\t\t struct cfg80211_registered_device *rdev,\n--\nnet/wireless/nl80211.c-4244-\nnet/wireless/nl80211.c:4245:static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)\nnet/wireless/nl80211.c-4246-{\n--\nnet/wireless/nl80211.c-4317-\nnet/wireless/nl80211.c:4318:\t\treturn nl80211_set_wiphy_radio(info, rdev, radio_idx);\nnet/wireless/nl80211.c-4319-\t}\n--\nnet/wireless/nl80211.c=19731=static const struct genl_small_ops nl80211_small_ops[] = {\n--\nnet/wireless/nl80211.c-19734-\t\t.validate = GENL_DONT_VALIDATE_STRICT | GENL_DONT_VALIDATE_DUMP,\nnet/wireless/nl80211.c:19735:\t\t.doit = nl80211_set_wiphy,\nnet/wireless/nl80211.c-19736-\t\t.flags = GENL_UNS_ADMIN_PERM,\n"
} |
| 15/2 | 2026/09/21 08:52 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 10169 output: 33 thoughts: 655 Thoughts: **Fuzzing Target: `nl80211_set_wiphy` - A Promising Candidate** Okay, so here's the breakdown. `nl80211_set_wiphy` is the `.doit` callback for `NL80211_CMD_SET_WIPHY`, making it a key entry point. And yes, it's definitely reachable. The `GENL_UNS_ADMIN_PERM` permission means any unprivileged user in a new namespace, or root in the default namespace, can trigger it, which is exactly how syzkaller operates with its netlink and `unshare` use. My immediate thought is, "This is good. This is *fuzzable*." The key is that the code modification touches the assignment of `rdev->wiphy.rts_threshold = rts_threshold;`. This only matters when `old_radio_rts_threshold` is NULL, which is the case for single-radio devices. Previously, this RTS threshold setting for devices with only one radio wasn't even *doing* anything! Now, this patch *does* update `rdev->wiphy.rts_threshold` when `changed & WIPHY_PARAM_RTS_THRESHOLD` is set. This fundamentally alters state management within `cfg80211` and the `nl80211` netlink interface. That's a huge flag for fuzzing! It's executable code, directly reachable through netlink operations, and we can test it with virtual devices, specifically `mac80211_hwsim`. Let's double-check the details. The verdict is "WorthFuzzing: True". The reasoning is concise: It's a code modification with a state change in the core wireless configuration netlink API. My initial thought was correct: It's good to fuzz. Now, let's look at the instructions. The "FocusSymbols" instruction is clear: `nl80211_set_wiphy`. But are there any other functions to also watch? Let's check callers or related functions in `nl80211`. `nl80211_set_wiphy` is the modified function. And ah, yes, `rdev_set_wiphy_params`: ```c result = rdev_set_wiphy_params(rdev, radio_idx, changed); ``` While `rdev_set_wiphy_params` is a driver wrapper, the bug fix occurs specifically in `nl80211_set_wiphy`. So, should we look for `rdev_set_wiphy_params` as well? I'd say no. It's the entry point that's interesting. Finally, can we *include* `nl80211_set_wiphy`? Yes. It's a static function in `net/wireless/nl80211.c`, but it's *not* inlined because it's pointed to by `nl80211_small_ops.doit` function pointer! So, it exists as a symbol in either `vmlinux` or `cfg80211.ko`. That's perfect. Let's start fuzzing `nl80211_set_wiphy`! |
| 16/2 | 2026/09/21 08:53 | tool | grepper |
0mArgs:{
"Expression": "rdev_set_wiphy_params",
"PathPrefix": "net/wireless/"
}Results: {
"Output": "net/wireless/nl80211.c=4218=static int nl80211_set_wiphy_radio(struct genl_info *info,\n--\nnet/wireless/nl80211.c-4237-\nnet/wireless/nl80211.c:4238:\tresult = rdev_set_wiphy_params(rdev, radio_idx, changed);\nnet/wireless/nl80211.c-4239-\tif (result)\n--\nnet/wireless/nl80211.c=4245=static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)\n--\nnet/wireless/nl80211.c-4582-\nnet/wireless/nl80211.c:4583:\t\tresult = rdev_set_wiphy_params(rdev, radio_idx, changed);\nnet/wireless/nl80211.c-4584-\t\tif (result) {\n--\nnet/wireless/rdev-ops.h=579=static inline int\nnet/wireless/rdev-ops.h:580:rdev_set_wiphy_params(struct cfg80211_registered_device *rdev, int radio_idx,\nnet/wireless/rdev-ops.h-581-\t\t u32 changed)\n--\nnet/wireless/rdev-ops.h-584-\nnet/wireless/rdev-ops.h:585:\ttrace_rdev_set_wiphy_params(\u0026rdev-\u003ewiphy, radio_idx, changed);\nnet/wireless/rdev-ops.h-586-\tif (rdev-\u003eops-\u003eset_wiphy_params)\n--\nnet/wireless/trace.h=1723=TRACE_EVENT(rdev_join_ocb,\n--\nnet/wireless/trace.h-1738-\nnet/wireless/trace.h:1739:TRACE_EVENT(rdev_set_wiphy_params,\nnet/wireless/trace.h-1740-\tTP_PROTO(struct wiphy *wiphy, int radio_idx, u32 changed),\n--\nnet/wireless/wext-compat.c=249=int cfg80211_wext_siwrts(struct net_device *dev,\n--\nnet/wireless/wext-compat.c-266-\nnet/wireless/wext-compat.c:267:\terr = rdev_set_wiphy_params(rdev, -1, WIPHY_PARAM_RTS_THRESHOLD);\nnet/wireless/wext-compat.c-268-\tif (err)\n--\nnet/wireless/wext-compat.c=287=int cfg80211_wext_siwfrag(struct net_device *dev,\n--\nnet/wireless/wext-compat.c-307-\nnet/wireless/wext-compat.c:308:\terr = rdev_set_wiphy_params(rdev, -1, WIPHY_PARAM_FRAG_THRESHOLD);\nnet/wireless/wext-compat.c-309-\tif (err)\n--\nnet/wireless/wext-compat.c=328=static int cfg80211_wext_siwretry(struct net_device *dev,\n--\nnet/wireless/wext-compat.c-358-\nnet/wireless/wext-compat.c:359:\terr = rdev_set_wiphy_params(rdev, -1, changed);\nnet/wireless/wext-compat.c-360-\tif (err) {\n"
} |
| 17/2 | 2026/09/21 08:53 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 12532 output: 38 thoughts: 204 Thoughts: **Analyzing the `nl80211_set_wiphy` Function** Okay, so I'm looking at `nl80211_set_wiphy`. The fact that `rdev_set_wiphy_params` is a static inline in `rdev-ops.h` makes `nl80211_set_wiphy` the entry point. I need to figure out what configurations are critical to its operation. Naturally, `CFG80211` is the obvious starting point. That one's the foundation. But I also need to consider the related subsystems. Does it depend on `MAC80211`, or perhaps `MAC80211_HWSIM`? Since `MAC80211_HWSIM` lets me simulate Wi-Fi hardware—essentially giving `nl80211_set_wiphy` devices to play with in a QEMU environment for testing—it's worth investigating. I need to confirm if `MAC80211_HWSIM` has dependencies on both `CFG80211` and `MAC80211`. That would certainly influence my analysis of the function's broader behavior. |
| 18/2 | 2026/09/21 08:53 | tool | grepper |
0mArgs:{
"Expression": "MAC80211_HWSIM",
"PathPrefix": "drivers/net/wireless/virtual/"
}Results: {
"Output": "drivers/net/wireless/virtual/Kconfig:1:config MAC80211_HWSIM\ndrivers/net/wireless/virtual/Kconfig-2-\ttristate \"Simulated radio testing tool for mac80211\"\n--\ndrivers/net/wireless/virtual/Makefile:1:obj-$(CONFIG_MAC80211_HWSIM)\t+= mac80211_hwsim.o\ndrivers/net/wireless/virtual/Makefile-2-mac80211_hwsim-objs\t\t+= mac80211_hwsim_main.o\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h-8-\ndrivers/net/wireless/virtual/mac80211_hwsim.h:9:#ifndef __MAC80211_HWSIM_H\ndrivers/net/wireless/virtual/mac80211_hwsim.h:10:#define __MAC80211_HWSIM_H\ndrivers/net/wireless/virtual/mac80211_hwsim.h-11-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h=217=struct hwsim_tx_rate {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h-230- *\ndrivers/net/wireless/virtual/mac80211_hwsim.h:231: * @MAC80211_HWSIM_TX_RC_USE_RTS_CTS: Use RTS/CTS exchange for this rate.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:232: * @MAC80211_HWSIM_TX_RC_USE_CTS_PROTECT: CTS-to-self protection is required.\ndrivers/net/wireless/virtual/mac80211_hwsim.h-233- *\tThis is set if the current BSS requires ERP protection.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:234: * @MAC80211_HWSIM_TX_RC_USE_SHORT_PREAMBLE: Use short preamble.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:235: * @MAC80211_HWSIM_TX_RC_MCS: HT rate.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:236: * @MAC80211_HWSIM_TX_RC_VHT_MCS: VHT MCS rate, in this case the idx field is\ndrivers/net/wireless/virtual/mac80211_hwsim.h-237- *\tsplit into a higher 4 bits (Nss) and lower 4 bits (MCS number)\ndrivers/net/wireless/virtual/mac80211_hwsim.h:238: * @MAC80211_HWSIM_TX_RC_GREEN_FIELD: Indicates whether this rate should be used\ndrivers/net/wireless/virtual/mac80211_hwsim.h-239- *\tin Greenfield mode.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:240: * @MAC80211_HWSIM_TX_RC_40_MHZ_WIDTH: Indicates if the Channel Width should be\ndrivers/net/wireless/virtual/mac80211_hwsim.h-241- *\t40 MHz.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:242: * @MAC80211_HWSIM_TX_RC_80_MHZ_WIDTH: Indicates 80 MHz transmission\ndrivers/net/wireless/virtual/mac80211_hwsim.h:243: * @MAC80211_HWSIM_TX_RC_160_MHZ_WIDTH: Indicates 160 MHz transmission\ndrivers/net/wireless/virtual/mac80211_hwsim.h-244- *\t(80+80 isn't supported yet)\ndrivers/net/wireless/virtual/mac80211_hwsim.h:245: * @MAC80211_HWSIM_TX_RC_DUP_DATA: The frame should be transmitted on both of\ndrivers/net/wireless/virtual/mac80211_hwsim.h-246- *\tthe adjacent 20 MHz channels, if the current channel type is\ndrivers/net/wireless/virtual/mac80211_hwsim.h-247- *\tNL80211_CHAN_HT40MINUS or NL80211_CHAN_HT40PLUS.\ndrivers/net/wireless/virtual/mac80211_hwsim.h:248: * @MAC80211_HWSIM_TX_RC_SHORT_GI: Short Guard interval should be used for this\ndrivers/net/wireless/virtual/mac80211_hwsim.h-249- *\trate.\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h=251=enum hwsim_tx_rate_flags {\ndrivers/net/wireless/virtual/mac80211_hwsim.h:252:\tMAC80211_HWSIM_TX_RC_USE_RTS_CTS\t\t= BIT(0),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:253:\tMAC80211_HWSIM_TX_RC_USE_CTS_PROTECT\t\t= BIT(1),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:254:\tMAC80211_HWSIM_TX_RC_USE_SHORT_PREAMBLE\t= BIT(2),\ndrivers/net/wireless/virtual/mac80211_hwsim.h-255-\ndrivers/net/wireless/virtual/mac80211_hwsim.h-256-\t/* rate index is an HT/VHT MCS instead of an index */\ndrivers/net/wireless/virtual/mac80211_hwsim.h:257:\tMAC80211_HWSIM_TX_RC_MCS\t\t\t= BIT(3),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:258:\tMAC80211_HWSIM_TX_RC_GREEN_FIELD\t\t= BIT(4),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:259:\tMAC80211_HWSIM_TX_RC_40_MHZ_WIDTH\t\t= BIT(5),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:260:\tMAC80211_HWSIM_TX_RC_DUP_DATA\t\t= BIT(6),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:261:\tMAC80211_HWSIM_TX_RC_SHORT_GI\t\t= BIT(7),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:262:\tMAC80211_HWSIM_TX_RC_VHT_MCS\t\t\t= BIT(8),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:263:\tMAC80211_HWSIM_TX_RC_80_MHZ_WIDTH\t\t= BIT(9),\ndrivers/net/wireless/virtual/mac80211_hwsim.h:264:\tMAC80211_HWSIM_TX_RC_160_MHZ_WIDTH\t\t= BIT(10),\ndrivers/net/wireless/virtual/mac80211_hwsim.h-265-};\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h=328=enum hwsim_rate_info_attributes {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim.h-347-\ndrivers/net/wireless/virtual/mac80211_hwsim.h:348:#endif /* __MAC80211_HWSIM_H */\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h-9-\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h:10:#ifndef __MAC80211_HWSIM_I_H\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h:11:#define __MAC80211_HWSIM_I_H\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h-12-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h=165=void ieee80211_hwsim_wake_tx_queue(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h-167-\ndrivers/net/wireless/virtual/mac80211_hwsim_i.h:168:#endif /* __MAC80211_HWSIM_I_H */\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=712=static struct mac80211_hwsim_data *get_hwsim_data_ref_from_addr(const u8 *addr)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-716-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:717:/* MAC80211_HWSIM netlink family */\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-718-static struct genl_family hwsim_genl_family;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=724=static const struct genl_multicast_group hwsim_mcgrps[] = {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-727-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:728:/* MAC80211_HWSIM netlink policy */\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-729-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=865=static const struct nla_policy hwsim_genl_policy[HWSIM_ATTR_MAX + 1] = {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-901-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:902:/* MAC80211_HWSIM virtio queues */\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-903-static struct virtqueue *hwsim_vqs[HWSIM_NUM_VQS];\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=1575=static inline u16 trans_tx_rate_flags_ieee2hwsim(struct ieee80211_tx_rate *rate)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1579-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_USE_RTS_CTS)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1580:\t\tresult |= MAC80211_HWSIM_TX_RC_USE_RTS_CTS;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1581-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_USE_CTS_PROTECT)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1582:\t\tresult |= MAC80211_HWSIM_TX_RC_USE_CTS_PROTECT;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1583-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_USE_SHORT_PREAMBLE)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1584:\t\tresult |= MAC80211_HWSIM_TX_RC_USE_SHORT_PREAMBLE;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1585-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_MCS)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1586:\t\tresult |= MAC80211_HWSIM_TX_RC_MCS;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1587-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_GREEN_FIELD)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1588:\t\tresult |= MAC80211_HWSIM_TX_RC_GREEN_FIELD;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1589-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_40_MHZ_WIDTH)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1590:\t\tresult |= MAC80211_HWSIM_TX_RC_40_MHZ_WIDTH;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1591-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_DUP_DATA)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1592:\t\tresult |= MAC80211_HWSIM_TX_RC_DUP_DATA;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1593-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_SHORT_GI)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1594:\t\tresult |= MAC80211_HWSIM_TX_RC_SHORT_GI;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1595-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_VHT_MCS)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1596:\t\tresult |= MAC80211_HWSIM_TX_RC_VHT_MCS;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1597-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_80_MHZ_WIDTH)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1598:\t\tresult |= MAC80211_HWSIM_TX_RC_80_MHZ_WIDTH;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1599-\tif (rate-\u003eflags \u0026 IEEE80211_TX_RC_160_MHZ_WIDTH)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:1600:\t\tresult |= MAC80211_HWSIM_TX_RC_160_MHZ_WIDTH;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-1601-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=3484=static const char mac80211_hwsim_gstrings_stats[][ETH_GSTRING_LEN] = {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3494-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:3495:#define MAC80211_HWSIM_SSTATS_LEN ARRAY_SIZE(mac80211_hwsim_gstrings_stats)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3496-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=3506=static int mac80211_hwsim_get_et_sset_count(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3509-\tif (sset == ETH_SS_STATS)\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:3510:\t\treturn MAC80211_HWSIM_SSTATS_LEN;\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3511-\treturn 0;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=3514=static void mac80211_hwsim_get_et_stats(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3529-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:3530:\tWARN_ON(i != MAC80211_HWSIM_SSTATS_LEN);\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-3531-}\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=5647=static const u8 iftypes_ext_capa_ap[] = {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-5655-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:5656:#define MAC80211_HWSIM_MLD_CAPA_OPS\t\t\t\t\\\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-5657-\tFIELD_PREP_CONST(IEEE80211_MLD_CAP_OP_TID_TO_LINK_MAP_NEG_SUPP, \\\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=5662=static const struct wiphy_iftype_ext_capab mac80211_hwsim_iftypes_ext_capa[] = {\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-5669-\t\t\t\t IEEE80211_EML_CAP_EMLMR_SUPPORT,\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:5670:\t\t.mld_capa_and_ops = MAC80211_HWSIM_MLD_CAPA_OPS,\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-5671-\t},\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=7147=static struct genl_family hwsim_genl_family __ro_after_init = {\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:7148:\t.name = \"MAC80211_HWSIM\",\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-7149-\t.version = 1,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c=7467=static void hwsim_virtio_remove(struct virtio_device *vdev)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-7475-\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:7476:/* MAC80211_HWSIM virtio device id table */\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-7477-static const struct virtio_device_id id_table[] = {\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c:7478:\t{ VIRTIO_ID_MAC80211_HWSIM, VIRTIO_DEV_ANY_ID },\ndrivers/net/wireless/virtual/mac80211_hwsim_main.c-7479-\t{ 0 }\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=78=static u64 hwsim_nan_get_master_rank(struct mac80211_hwsim_data *data)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-82-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:83:\tif (data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_UP) {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-84-\t\tmaster_pref = data-\u003enan.master_pref;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=216=void mac80211_hwsim_nan_rx(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-273-\tif ((slot != SLOT_24GHZ_DW \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:274:\t data-\u003enan.phase != MAC80211_HWSIM_NAN_PHASE_SCAN) ||\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-275-\t rx_status.freq != 2437)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-436-\t\t (cg == own_cg \u0026\u0026 frame_amr \u003e curr_amr) ||\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:437:\t\t data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_SCAN) {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-438-\t\t\t/* Avoid a state transition */\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-468-\t\t\t */\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:469:\t\t\tdata-\u003enan.phase = MAC80211_HWSIM_NAN_PHASE_UP;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-470-\t\t\tdata-\u003enan.random_factor_valid_dwst = 0;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=612=mac80211_hwsim_nan_exec_state_transitions(struct mac80211_hwsim_data *data)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-625-\tif (data-\u003enan.master_transition_score \u003c 3)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:626:\t\tdata-\u003enan.role = MAC80211_HWSIM_NAN_ROLE_MASTER;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:627:\telse if (data-\u003enan.role == MAC80211_HWSIM_NAN_ROLE_MASTER \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-628-\t\t data-\u003enan.master_transition_score \u003e= 3)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:629:\t\tdata-\u003enan.role = MAC80211_HWSIM_NAN_ROLE_SYNC;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:630:\telse if (data-\u003enan.role == MAC80211_HWSIM_NAN_ROLE_SYNC \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-631-\t\t data-\u003enan.sync_transition_score \u003e= 3)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:632:\t\tdata-\u003enan.role = MAC80211_HWSIM_NAN_ROLE_NON_SYNC;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:633:\telse if (data-\u003enan.role == MAC80211_HWSIM_NAN_ROLE_NON_SYNC \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-634-\t\t data-\u003enan.sync_transition_score \u003c 3)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:635:\t\tdata-\u003enan.role = MAC80211_HWSIM_NAN_ROLE_SYNC;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-636-\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-641-\t */\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:642:\tif (data-\u003enan.role == MAC80211_HWSIM_NAN_ROLE_MASTER \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-643-\t !hrtimer_active(\u0026data-\u003enan.discovery_beacon_timer))\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-653-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:654:\t\tif (data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_SCAN) {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:655:\t\t\tdata-\u003enan.phase = MAC80211_HWSIM_NAN_PHASE_WARMUP;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-656-\t\t\tdata-\u003enan.random_factor_valid_dwst = NAN_WARMUP_DWST;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-659-\t\t} else {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:660:\t\t\tdata-\u003enan.phase = MAC80211_HWSIM_NAN_PHASE_UP;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-661-\t\t\tdata-\u003enan.random_factor_valid_dwst =\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=695=mac80211_hwsim_nan_tx_beacon(struct mac80211_hwsim_data *data,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-750-\tnan_attr.length = cpu_to_le16(sizeof(master_indication));\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:751:\tif (data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_UP) {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-752-\t\tmaster_indication.master_pref = data-\u003enan.master_pref;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=774=mac80211_hwsim_nan_slot_timer(struct hrtimer *timer)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-807-\t\ttx_sync_beacon =\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:808:\t\t\tdata-\u003enan.phase != MAC80211_HWSIM_NAN_PHASE_SCAN \u0026\u0026\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:809:\t\t\tdata-\u003enan.role != MAC80211_HWSIM_NAN_ROLE_NON_SYNC;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-810-\t}\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=867=mac80211_hwsim_nan_discovery_beacon_timer(struct hrtimer *timer)\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-879-\tscoped_guard(spinlock, \u0026data-\u003enan.state_lock) {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:880:\t\tif (data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_SCAN ||\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:881:\t\t data-\u003enan.role != MAC80211_HWSIM_NAN_ROLE_MASTER)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-882-\t\t\treturn HRTIMER_NORESTART;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=909=int mac80211_hwsim_nan_start(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-926-\t\t/* Start in the \"scan\" phase and stay there for a little bit */\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:927:\t\tdata-\u003enan.phase = MAC80211_HWSIM_NAN_PHASE_SCAN;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-928-\t\tdata-\u003enan.random_factor_valid_dwst = 1;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-930-\t\tdata-\u003enan.master_pref = conf-\u003emaster_pref;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:931:\t\tdata-\u003enan.role = MAC80211_HWSIM_NAN_ROLE_MASTER;\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-932-\t\tmemset(\u0026data-\u003enan.current_ami, 0,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c=1226=bool mac80211_hwsim_nan_receive(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-1235-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c:1236:\tif (data-\u003enan.phase == MAC80211_HWSIM_NAN_PHASE_SCAN)\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.c-1237-\t\treturn channel-\u003ecenter_freq == 2437;\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h-6-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:7:#ifndef __MAC80211_HWSIM_NAN_H\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:8:#define __MAC80211_HWSIM_NAN_H\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h-9-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h=10=enum mac80211_hwsim_nan_phase {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:11:\tMAC80211_HWSIM_NAN_PHASE_SCAN,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:12:\tMAC80211_HWSIM_NAN_PHASE_WARMUP,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:13:\tMAC80211_HWSIM_NAN_PHASE_UP,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h-14-};\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h=16=enum mac80211_hwsim_nan_role {\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:17:\tMAC80211_HWSIM_NAN_ROLE_MASTER,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:18:\tMAC80211_HWSIM_NAN_ROLE_SYNC,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:19:\tMAC80211_HWSIM_NAN_ROLE_NON_SYNC,\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h-20-};\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h=99=void mac80211_hwsim_nan_local_sched_changed(struct ieee80211_hw *hw,\n--\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h-101-\ndrivers/net/wireless/virtual/mac80211_hwsim_nan.h:102:#endif /* __MAC80211_HWSIM_NAN_H */\n"
} |
| 19/2 | 2026/09/21 08:53 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 22001 output: 36 thoughts: 16 Thoughts: Here's my take on the thought process, as if I were the one thinking it: **Diving into Virtual Wireless Configuration** Okay, time to get my hands dirty. I need to understand the configuration options available for the virtual wireless network driver. My first instinct, as always, is to head straight to the source. Specifically, I need to check the Kconfig file for that driver. Let's start with `drivers/net/wireless/virtual/Kconfig`. This is where all the juicy details about feature flags, dependencies, and default settings are kept. That's the first stop to understand how this module fits into the broader wireless landscape and what's configurable. Let's see what we can find. |
| 20/2 | 2026/09/21 08:53 | tool | read-file |
0mArgs:{
"File": "drivers/net/wireless/virtual/Kconfig",
"FirstLine": 1,
"LineCount": 40
}Results: {
"Contents": " 1:\tconfig MAC80211_HWSIM\n 2:\t\ttristate \"Simulated radio testing tool for mac80211\"\n 3:\t\tdepends on MAC80211\n 4:\t\thelp\n 5:\t\t This driver is a developer testing tool that can be used to test\n 6:\t\t IEEE 802.11 networking stack (mac80211) functionality. This is not\n 7:\t\t needed for normal wireless LAN usage and is only for testing. See\n 8:\t\t Documentation/networking/mac80211_hwsim for more information on how\n 9:\t\t to use this tool.\n 10:\t\n 11:\t\t To compile this driver as a module, choose M here: the module will be\n 12:\t\t called mac80211_hwsim. If unsure, say N.\n 13:\t\n 14:\tconfig VIRT_WIFI\n 15:\t\ttristate \"Wifi wrapper for ethernet drivers\"\n 16:\t\tdepends on CFG80211\n 17:\t\thelp\n 18:\t\t This option adds support for ethernet connections to appear as if they\n 19:\t\t are wifi connections through a special rtnetlink device.\n 20:\t\n"
} |
| 21/2 | 2026/09/21 08:53 | llm | patch-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 22529 output: 182 thoughts: 647 Thoughts: **Analyzing a Potential Fuzzing Target: `nl80211_set_wiphy`** Okay, so I see we need `CFG80211` to build `net/wireless/nl80211.c`, which is a key indicator. Let's make sure we have all our ducks in a row – `CFG80211` hinges on `RFKILL || !RFKILL`, which is pretty standard. Now, looking at the syzkaller kernel configs, I see that `CFG80211`, `MAC80211`, and `MAC80211_HWSIM` are all typical configurations. Let me make a mental note to explicitly include those – `CFG80211`, `MAC80211`, and `MAC80211_HWSIM` – and keep `nl80211_set_wiphy` front and center as our focus symbol. Right, time for a deep dive. I've got to confirm this is indeed a juicy target. The patch specifically tweaks `nl80211_set_wiphy()` in `net/wireless/nl80211.c`. The before and after code snippets highlight a critical change related to how `rdev->wiphy.rts_threshold` is handled when `WIPHY_PARAM_RTS_THRESHOLD` is modified. It looks like the fix ensures the `rts_threshold` gets updated even when `old_radio_rts_threshold` is NULL, basically covering the case where `wiphy.n_radio` is zero. That's a classic race condition and state management issue in `cfg80211`, a core wireless netlink subsystem. And this is a reachable subsystem. The netlink `nl80211` interface can be accessed by unprivileged users in user namespaces or by root in the default namespace, which is great for fuzzing. Also, emulated wireless devices like `mac80211_hwsim` are pretty common in our virtualized fuzzing setups. That's fantastic – easy to get the target built into the environment and reachable! So, taking all this into account, I'm pretty confident. This looks like a solid fuzzing target. **Verdict:** WorthFuzzing: true **FocusSymbols:** ["nl80211_set_wiphy"] **EnableConfigs:** ["CFG80211", "MAC80211", "MAC80211_HWSIM"] Time to call `set-results`. Let's get this thing fuzzed! |
| 22/2 | 2026/09/21 08:53 | tool | set-results |
0mArgs:{
"EnableConfigs": [
"CFG80211",
"MAC80211",
"MAC80211_HWSIM"
],
"FocusSymbols": [
"nl80211_set_wiphy"
],
"Reasoning": "The patch modifies state management in nl80211_set_wiphy() by ensuring that rdev-\u003ewiphy.rts_threshold is updated whenever WIPHY_PARAM_RTS_THRESHOLD is specified, regardless of whether old_radio_rts_threshold is allocated (e.g., when n_radio is 0). This modifies reachable generic netlink configuration code in cfg80211 which can be exercised using simulated wireless hardware such as mac80211_hwsim.",
"WorthFuzzing": true
}Results: {
"EnableConfigs": [
"CFG80211",
"MAC80211",
"MAC80211_HWSIM"
],
"FocusSymbols": [
"nl80211_set_wiphy"
],
"Reasoning": "The patch modifies state management in nl80211_set_wiphy() by ensuring that rdev-\u003ewiphy.rts_threshold is updated whenever WIPHY_PARAM_RTS_THRESHOLD is specified, regardless of whether old_radio_rts_threshold is allocated (e.g., when n_radio is 0). This modifies reachable generic netlink configuration code in cfg80211 which can be exercised using simulated wireless hardware such as mac80211_hwsim.",
"WorthFuzzing": true
} |
| 23/1 | 2026/09/21 08:53 | action | If |
0mArgs:{
"WorthFuzzing": true
}Results: null |
| 24/2 | 2026/09/21 08:53 | agent | kmsan-evaluator |
0mModel:core Args: null Results: {
"KMSANReasoning": "The patch resolves a logic bug in nl80211_set_wiphy() where rdev-\u003ewiphy.rts_threshold was not being updated when old_radio_rts_threshold was NULL (i.e. when rdev-\u003ewiphy.n_radio is 0). The change separates updating rdev-\u003ewiphy.rts_threshold from iterating over the per-radio config.\n\nThe variable rts_threshold is always initialized from the netlink attribute NL80211_ATTR_WIPHY_RTS_THRESHOLD whenever WIPHY_PARAM_RTS_THRESHOLD is set in changed. The patch introduces no uninitialized memory, does not alter buffer bounds or memory copying to user space, and does not branch on uninitialized values. Therefore, there are no uninitialized memory risks that require a dedicated KMSAN fuzzing session.",
"NeedsKMSAN": false
}Instruction: You are an expert Linux kernel security engineer specializing in kernel memory
error detectors (KASAN and KMSAN). Your job is to review the provided patch series and
determine if the code changes justify spawning a dedicated KMSAN (KernelMemorySanitizer)
fuzzing session in addition to standard KASAN fuzzing.
CRITICAL DISTINCTION BETWEEN KASAN AND KMSAN:
- Standard KASAN kernel builds (upstream-apparmor-kasan.config) already enable
a comprehensive suite of debugging tools and sanitizers, including KASAN
(out-of-bounds accesses, use-after-free, double free, invalid free), LOCKDEP
(locking bugs and deadlocks), UB-sanitizers, and memory corruption checks.
- KMSAN (KernelMemorySanitizer) detects reads of UNINITIALIZED memory (stack, heap,
or page allocations) and kernel-to-user memory info-leaks.
Rule: THERE IS NO SENSE IN RUNNING A KMSAN SESSION IF A BUG CAN BE CAUGHT BY KASAN,
LOCKDEP, OR OTHER STANDARD BUG DETECTORS.
A dedicated KMSAN fuzzing session incurs significant resource costs. You must ONLY
set NeedsKMSAN=true if the code changes introduce or expose UNINITIALIZED MEMORY risks
that are detected ONLY by KMSAN.
Look holistically at the patch series and surrounding code. Even if no direct
uninitialized field accesses or new buffer allocations are added in the diff itself,
a patch may alter control flow, bounds checking, or data length calculations in ways
that change how the rest of the code operates on existing buffers (e.g. allowing
uninitialized stack/heap memory to be read, copied to user space, or used in control
flow). Do not hesitate to use your code access tools to inspect the surrounding code,
called functions, and callers.
Set NeedsKMSAN=true ONLY IF the patch introduces or modifies:
1. Kernel structures sent to user space (via copy_to_user, put_user, netlink skb
attributes, ioctl output arguments, socket options, or BPF buffers) where fields
or structure padding might not be fully initialized/zeroed.
2. Conditional logic or branching that depends on potentially uninitialized variables
or struct fields.
3. Allocation or initialization of complex data structures where uninitialized fields
could be read later in reachable code paths.
4. Bounds checks, lengths, or logic in a way that allows surrounding code to access
uninitialized bytes of existing buffers.
Set NeedsKMSAN=false IF:
- The code changes primarily risk out-of-bounds access, array overflows, NULL pointer
dereferences, locking deadlocks, or use-after-free bugs (these are already caught
by KASAN, LOCKDEP, or standard bug detectors).
- All stack/heap structures touched or introduced by the patch are fully zeroed
or initialized (e.g. using = {0}, memset, kzalloc) before being read or copied.
- The patch does not introduce any risk of uninitialized memory usage or info-leaks.
Use your code access tools to inspect the surrounding code if necessary, then provide
detailed KMSANReasoning contrasting KASAN vs KMSAN applicability for this patch.
Prefer calling several tools at the same time to save round-trips.
Use set-results tool to provide results of the analysis.
It must be called exactly once before the final reply.
Ignore results of this tool.
Prompt: Target architecture: amd64
For your convenience, here is the diff of the changes:
commit 0829d2d4bbce133b8b5c786a33950875ebeb2b80
Author: syz-cluster <triage@syzkaller.com>
Date: Mon Sep 21 08:44:18 2026 +0000
syz-cluster: applied patch under review
diff --git a/net/wireless/nl80211.c b/net/wireless/nl80211.c
index 899b6374c5506..f75206332eaac 100644
--- a/net/wireless/nl80211.c
+++ b/net/wireless/nl80211.c
@@ -4563,12 +4563,13 @@ static int nl80211_set_wiphy(struct sk_buff *skb, struct genl_info *info)
rdev->wiphy.retry_long = retry_long;
if (changed & WIPHY_PARAM_FRAG_THRESHOLD)
rdev->wiphy.frag_threshold = frag_threshold;
- if ((changed & WIPHY_PARAM_RTS_THRESHOLD) &&
- old_radio_rts_threshold) {
+ if (changed & WIPHY_PARAM_RTS_THRESHOLD) {
rdev->wiphy.rts_threshold = rts_threshold;
- for (i = 0 ; i < rdev->wiphy.n_radio; i++)
- rdev->wiphy.radio_cfg[i].rts_threshold =
- rdev->wiphy.rts_threshold;
+ if (old_radio_rts_threshold) {
+ for (i = 0; i < rdev->wiphy.n_radio; i++)
+ rdev->wiphy.radio_cfg[i].rts_threshold =
+ rdev->wiphy.rts_threshold;
+ }
}
if (changed & WIPHY_PARAM_COVERAGE_CLASS)
rdev->wiphy.coverage_class = coverage_class;
|
| 25/3 | 2026/09/21 08:53 | llm | kmsan-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 2315 output: 42 thoughts: 512 Thoughts: **Reviewing the nl80211 Patch: Wiphy Parameter Updates** Okay, so I'm looking at this patch within `nl80211.c`, specifically the `nl80211_set_wiphy` function. The diff focuses on how we handle setting various Wi-Fi PHY (Wiphy) parameters. Seems like there's been a change around the RTS threshold update logic. It looks like the author is addressing a potential issue with how the RTS threshold is being propagated to the radio configurations. Previously, the conditional `old_radio_rts_threshold` was present, and the loop to update `radio_cfg` would only execute if this flag was true, but now that logic seems to be gone. The change now checks `changed & WIPHY_PARAM_RTS_THRESHOLD`, and then the logic to propagate to the `radio_cfg` is only done when `old_radio_rts_threshold` is true. Need to understand why the conditional was removed - what scenario is this addressing? I'll have to delve deeper into why the previous conditional might have been there in the first place, or if the commit log justifies it. The rest of the parameter updates (retry_long, frag_threshold, coverage_class) seem straightforward, updating the corresponding fields in the `rdev->wiphy` struct if the relevant `WIPHY_PARAM_*` flag is set. The core logic of updating those parameters looks sound, based on a quick glance, but I need to focus on this RTS threshold change. Seems like the intent is to streamline the update process, but this could be a regression if that conditional was there for a reason. Definitely worth a closer look, especially how `old_radio_rts_threshold` is set and used elsewhere. |
| 26/3 | 2026/09/21 08:53 | tool | read-file |
0mArgs:{
"File": "net/wireless/nl80211.c",
"FirstLine": 4500,
"LineCount": 100
}Results: {
"Contents": "4500:\t\t\t\t\t\t NL80211_EXT_FEATURE_TXQS))\n4501:\t\t\t\treturn -EOPNOTSUPP;\n4502:\t\n4503:\t\t\ttxq_limit = nla_get_u32(\n4504:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_TXQ_LIMIT]);\n4505:\t\t\tchanged |= WIPHY_PARAM_TXQ_LIMIT;\n4506:\t\t}\n4507:\t\n4508:\t\tif (info-\u003eattrs[NL80211_ATTR_TXQ_MEMORY_LIMIT]) {\n4509:\t\t\tif (!wiphy_ext_feature_isset(\u0026rdev-\u003ewiphy,\n4510:\t\t\t\t\t\t NL80211_EXT_FEATURE_TXQS))\n4511:\t\t\t\treturn -EOPNOTSUPP;\n4512:\t\n4513:\t\t\ttxq_memory_limit = nla_get_u32(\n4514:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_TXQ_MEMORY_LIMIT]);\n4515:\t\t\tchanged |= WIPHY_PARAM_TXQ_MEMORY_LIMIT;\n4516:\t\t}\n4517:\t\n4518:\t\tif (info-\u003eattrs[NL80211_ATTR_TXQ_QUANTUM]) {\n4519:\t\t\tif (!wiphy_ext_feature_isset(\u0026rdev-\u003ewiphy,\n4520:\t\t\t\t\t\t NL80211_EXT_FEATURE_TXQS))\n4521:\t\t\t\treturn -EOPNOTSUPP;\n4522:\t\n4523:\t\t\ttxq_quantum = nla_get_u32(\n4524:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_TXQ_QUANTUM]);\n4525:\t\t\tchanged |= WIPHY_PARAM_TXQ_QUANTUM;\n4526:\t\t}\n4527:\t\n4528:\t\tif (changed) {\n4529:\t\t\tu8 old_retry_short, old_retry_long;\n4530:\t\t\tu32 old_frag_threshold, old_rts_threshold;\n4531:\t\t\tu8 old_coverage_class, i;\n4532:\t\t\tu32 old_txq_limit, old_txq_memory_limit, old_txq_quantum;\n4533:\t\t\tu32 *old_radio_rts_threshold = NULL;\n4534:\t\n4535:\t\t\tif (!rdev-\u003eops-\u003eset_wiphy_params)\n4536:\t\t\t\treturn -EOPNOTSUPP;\n4537:\t\n4538:\t\t\tif (rdev-\u003ewiphy.n_radio) {\n4539:\t\t\t\told_radio_rts_threshold = kcalloc(rdev-\u003ewiphy.n_radio,\n4540:\t\t\t\t\t\t\t\t sizeof(u32),\n4541:\t\t\t\t\t\t\t\t GFP_KERNEL);\n4542:\t\t\t\tif (!old_radio_rts_threshold)\n4543:\t\t\t\t\treturn -ENOMEM;\n4544:\t\t\t}\n4545:\t\n4546:\t\t\told_retry_short = rdev-\u003ewiphy.retry_short;\n4547:\t\t\told_retry_long = rdev-\u003ewiphy.retry_long;\n4548:\t\t\told_frag_threshold = rdev-\u003ewiphy.frag_threshold;\n4549:\t\t\told_rts_threshold = rdev-\u003ewiphy.rts_threshold;\n4550:\t\t\tif (old_radio_rts_threshold) {\n4551:\t\t\t\tfor (i = 0 ; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4552:\t\t\t\t\told_radio_rts_threshold[i] =\n4553:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold;\n4554:\t\t\t}\n4555:\t\t\told_coverage_class = rdev-\u003ewiphy.coverage_class;\n4556:\t\t\told_txq_limit = rdev-\u003ewiphy.txq_limit;\n4557:\t\t\told_txq_memory_limit = rdev-\u003ewiphy.txq_memory_limit;\n4558:\t\t\told_txq_quantum = rdev-\u003ewiphy.txq_quantum;\n4559:\t\n4560:\t\t\tif (changed \u0026 WIPHY_PARAM_RETRY_SHORT)\n4561:\t\t\t\trdev-\u003ewiphy.retry_short = retry_short;\n4562:\t\t\tif (changed \u0026 WIPHY_PARAM_RETRY_LONG)\n4563:\t\t\t\trdev-\u003ewiphy.retry_long = retry_long;\n4564:\t\t\tif (changed \u0026 WIPHY_PARAM_FRAG_THRESHOLD)\n4565:\t\t\t\trdev-\u003ewiphy.frag_threshold = frag_threshold;\n4566:\t\t\tif (changed \u0026 WIPHY_PARAM_RTS_THRESHOLD) {\n4567:\t\t\t\trdev-\u003ewiphy.rts_threshold = rts_threshold;\n4568:\t\t\t\tif (old_radio_rts_threshold) {\n4569:\t\t\t\t\tfor (i = 0; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4570:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n4571:\t\t\t\t\t\t\trdev-\u003ewiphy.rts_threshold;\n4572:\t\t\t\t}\n4573:\t\t\t}\n4574:\t\t\tif (changed \u0026 WIPHY_PARAM_COVERAGE_CLASS)\n4575:\t\t\t\trdev-\u003ewiphy.coverage_class = coverage_class;\n4576:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_LIMIT)\n4577:\t\t\t\trdev-\u003ewiphy.txq_limit = txq_limit;\n4578:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_MEMORY_LIMIT)\n4579:\t\t\t\trdev-\u003ewiphy.txq_memory_limit = txq_memory_limit;\n4580:\t\t\tif (changed \u0026 WIPHY_PARAM_TXQ_QUANTUM)\n4581:\t\t\t\trdev-\u003ewiphy.txq_quantum = txq_quantum;\n4582:\t\n4583:\t\t\tresult = rdev_set_wiphy_params(rdev, radio_idx, changed);\n4584:\t\t\tif (result) {\n4585:\t\t\t\trdev-\u003ewiphy.retry_short = old_retry_short;\n4586:\t\t\t\trdev-\u003ewiphy.retry_long = old_retry_long;\n4587:\t\t\t\trdev-\u003ewiphy.frag_threshold = old_frag_threshold;\n4588:\t\t\t\trdev-\u003ewiphy.rts_threshold = old_rts_threshold;\n4589:\t\t\t\tif (old_radio_rts_threshold) {\n4590:\t\t\t\t\tfor (i = 0 ; i \u003c rdev-\u003ewiphy.n_radio; i++)\n4591:\t\t\t\t\t\trdev-\u003ewiphy.radio_cfg[i].rts_threshold =\n4592:\t\t\t\t\t\t\told_radio_rts_threshold[i];\n4593:\t\t\t\t}\n4594:\t\t\t\trdev-\u003ewiphy.coverage_class = old_coverage_class;\n4595:\t\t\t\trdev-\u003ewiphy.txq_limit = old_txq_limit;\n4596:\t\t\t\trdev-\u003ewiphy.txq_memory_limit = old_txq_memory_limit;\n4597:\t\t\t\trdev-\u003ewiphy.txq_quantum = old_txq_quantum;\n4598:\t\t\t}\n4599:\t\n"
} |
| 27/3 | 2026/09/21 08:53 | llm | kmsan-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 5160 output: 41 thoughts: 378 Thoughts: **Analyzing the RTS Threshold Update in Wireless Driver Code** Okay, let's break this down. I'm looking at this code and immediately see a potential issue with how the RTS threshold is being updated. In the original version, the conditional statement is structured in a way that, if the number of radios (`rdev->wiphy.n_radio`) is zero and therefore `old_radio_rts_threshold` is NULL, the main `rdev->wiphy.rts_threshold` isn't updated, even if the `WIPHY_PARAM_RTS_THRESHOLD` bit is set in `changed`. That's the core of it – the global threshold isn't set, which seems like a significant oversight. The patch corrects this by modifying the conditional. Now, the `rdev->wiphy.rts_threshold` is set directly, and then, only if `old_radio_rts_threshold` is valid (i.e., not NULL, which implies `n_radio > 0`), it iterates through the radio configurations to update the per-radio values. This ensures the main threshold is always updated when the parameter is changed, regardless of the radio count. Now I need to check the definition of `rts_threshold` and where it's read before that line, to ensure this fix doesn't introduce any new issues with how that value is being used downstream. Let's trace it back through `nl80211_set_wiphy` to get a complete picture of the parameter's lifecycle and dependencies. |
| 28/3 | 2026/09/21 08:53 | tool | read-file |
0mArgs:{
"File": "net/wireless/nl80211.c",
"FirstLine": 4440,
"LineCount": 65
}Results: {
"Contents": "4440:\t\t}\n4441:\t\n4442:\t\tchanged = 0;\n4443:\t\n4444:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_RETRY_SHORT]) {\n4445:\t\t\tretry_short = nla_get_u8(\n4446:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_WIPHY_RETRY_SHORT]);\n4447:\t\n4448:\t\t\tchanged |= WIPHY_PARAM_RETRY_SHORT;\n4449:\t\t}\n4450:\t\n4451:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_RETRY_LONG]) {\n4452:\t\t\tretry_long = nla_get_u8(\n4453:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_WIPHY_RETRY_LONG]);\n4454:\t\n4455:\t\t\tchanged |= WIPHY_PARAM_RETRY_LONG;\n4456:\t\t}\n4457:\t\n4458:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_FRAG_THRESHOLD]) {\n4459:\t\t\tfrag_threshold = nla_get_u32(\n4460:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_WIPHY_FRAG_THRESHOLD]);\n4461:\t\t\tif (frag_threshold \u003c 256)\n4462:\t\t\t\treturn -EINVAL;\n4463:\t\n4464:\t\t\tif (frag_threshold != (u32) -1) {\n4465:\t\t\t\t/*\n4466:\t\t\t\t * Fragments (apart from the last one) are required to\n4467:\t\t\t\t * have even length. Make the fragmentation code\n4468:\t\t\t\t * simpler by stripping LSB should someone try to use\n4469:\t\t\t\t * odd threshold value.\n4470:\t\t\t\t */\n4471:\t\t\t\tfrag_threshold \u0026= ~0x1;\n4472:\t\t\t}\n4473:\t\t\tchanged |= WIPHY_PARAM_FRAG_THRESHOLD;\n4474:\t\t}\n4475:\t\n4476:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_RTS_THRESHOLD]) {\n4477:\t\t\trts_threshold = nla_get_u32(\n4478:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_WIPHY_RTS_THRESHOLD]);\n4479:\t\t\tchanged |= WIPHY_PARAM_RTS_THRESHOLD;\n4480:\t\t}\n4481:\t\n4482:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_COVERAGE_CLASS]) {\n4483:\t\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_DYN_ACK])\n4484:\t\t\t\treturn -EINVAL;\n4485:\t\n4486:\t\t\tcoverage_class = nla_get_u8(\n4487:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_WIPHY_COVERAGE_CLASS]);\n4488:\t\t\tchanged |= WIPHY_PARAM_COVERAGE_CLASS;\n4489:\t\t}\n4490:\t\n4491:\t\tif (info-\u003eattrs[NL80211_ATTR_WIPHY_DYN_ACK]) {\n4492:\t\t\tif (!(rdev-\u003ewiphy.features \u0026 NL80211_FEATURE_ACKTO_ESTIMATION))\n4493:\t\t\t\treturn -EOPNOTSUPP;\n4494:\t\n4495:\t\t\tchanged |= WIPHY_PARAM_DYN_ACK;\n4496:\t\t}\n4497:\t\n4498:\t\tif (info-\u003eattrs[NL80211_ATTR_TXQ_LIMIT]) {\n4499:\t\t\tif (!wiphy_ext_feature_isset(\u0026rdev-\u003ewiphy,\n4500:\t\t\t\t\t\t NL80211_EXT_FEATURE_TXQS))\n4501:\t\t\t\treturn -EOPNOTSUPP;\n4502:\t\n4503:\t\t\ttxq_limit = nla_get_u32(\n4504:\t\t\t\tinfo-\u003eattrs[NL80211_ATTR_TXQ_LIMIT]);\n"
} |
| 29/3 | 2026/09/21 08:53 | llm | kmsan-evaluator |
0mModel:gemini-3.8-flash Args: null Results: null Tokens: input: 7023 output: 208 thoughts: 1206 Thoughts: **KMSAN Assessment: Examining the RTS Threshold Update**
Alright, let's break this down. My initial scan focused on lines 4476-4480 and 4566. From my perspective, it's clear that the `rts_threshold` variable is only read and assigned to `rdev->wiphy.rts_threshold` if `changed & WIPHY_PARAM_RTS_THRESHOLD` is set. This, in turn, only happens when the `NL80211_ATTR_WIPHY_RTS_THRESHOLD` attribute is present in the netlink message, and the `rts_threshold` is properly initialized via `nla_get_u32(...)`. There's also some restoration logic via `old_rts_threshold` if the operation somehow fails. The core of this is about handling the RTS threshold, and making sure the change is reflected correctly in the underlying device.
My primary concern, as always, is uninitialized memory. Let's make sure there isn't any:
* `rts_threshold` gets initialized only when `changed & WIPHY_PARAM_RTS_THRESHOLD` is set.
* `rdev->wiphy.rts_threshold` is assigned a u32 value from the netlink attribute, making sure there's no garbage.
* If `old_radio_rts_threshold` is non-NULL, it seems to have been allocated using `kcalloc` and populated from the current values.
* The code doesn't do any kernel-to-user copies or reads from uninitialized memory.
* So it looks like the memory is good.
The key insight is that this commit fixes a bug. The old code only updated `rdev->wiphy.rts_threshold` if `old_radio_rts_threshold` was non-null, which implicitly means that the device must have `n_radio > 0`. This prevented updates to `rts_threshold` for wiphys with `n_radio == 0`.
Now, let's rigorously check the KMSAN criteria. My expert eyes tell me, looking at the criteria, that "NeedsKMSAN" is *definitely* false here.
Here's why:
* This code doesn't introduce kernel structures that are sent to user space (nothing gets copied, put to user space, sent via netlink skb attributes, ioctl output arguments, socket options, or BPF buffers).
* No conditional logic or branching relies on uninitialized variables or struct fields.
* We're not allocating or initializing any complex data structures in a way that risks uninitialized fields being read later.
* There's no funny business with bounds checks or lengths that would expose uninitialized bytes.
So, according to this, "NeedsKMSAN = false" because the code *only* changes a logic bug. The changes primarily involve ensuring the RTS threshold is correctly set, regardless of the number of radios. The risks involve out-of-bounds access, array overflows, NULL pointer dereferences, locking deadlocks, or use-after-free bugs. The changed code:
```c
- if ((changed & WIPHY_PARAM_RTS_THRESHOLD) &&
- old_radio_rts_threshold) {
+ if (changed & WIPHY_PARAM_RTS_THRESHOLD) {
rdev->wiphy.rts_threshold = rts_threshold;
- for (i = 0 ; i < rdev->wiphy.n_radio; i++)
- rdev->wiphy.radio_cfg[i].rts_threshold =
- rdev->wiphy.rts_threshold;
+ if (old_radio_rts_threshold) {
+ for (i = 0; i < rdev->wiphy.n_radio; i++)
+ rdev->wiphy.radio_cfg[i].rts_threshold =
+ rdev->wiphy.rts_threshold;
+ }
}
```
The old code had an extra check that prevented the thresholds from being updated correctly. The new code does not. Thus, there is no risk of uninitialized memory usage, and so "NeedsKMSAN = false".
|
| 30/3 | 2026/09/21 08:53 | tool | set-results |
0mArgs:{
"KMSANReasoning": "The patch resolves a logic bug in nl80211_set_wiphy() where rdev-\u003ewiphy.rts_threshold was not being updated when old_radio_rts_threshold was NULL (i.e. when rdev-\u003ewiphy.n_radio is 0). The change separates updating rdev-\u003ewiphy.rts_threshold from iterating over the per-radio config.\n\nThe variable rts_threshold is always initialized from the netlink attribute NL80211_ATTR_WIPHY_RTS_THRESHOLD whenever WIPHY_PARAM_RTS_THRESHOLD is set in changed. The patch introduces no uninitialized memory, does not alter buffer bounds or memory copying to user space, and does not branch on uninitialized values. Therefore, there are no uninitialized memory risks that require a dedicated KMSAN fuzzing session.",
"NeedsKMSAN": false
}Results: {
"KMSANReasoning": "The patch resolves a logic bug in nl80211_set_wiphy() where rdev-\u003ewiphy.rts_threshold was not being updated when old_radio_rts_threshold was NULL (i.e. when rdev-\u003ewiphy.n_radio is 0). The change separates updating rdev-\u003ewiphy.rts_threshold from iterating over the per-radio config.\n\nThe variable rts_threshold is always initialized from the netlink attribute NL80211_ATTR_WIPHY_RTS_THRESHOLD whenever WIPHY_PARAM_RTS_THRESHOLD is set in changed. The patch introduces no uninitialized memory, does not alter buffer bounds or memory copying to user space, and does not branch on uninitialized values. Therefore, there are no uninitialized memory risks that require a dedicated KMSAN fuzzing session.",
"NeedsKMSAN": false
} |
| Total Calls | Total Tokens | Avg Tokens | Total Duration (Seconds) | Avg Duration (Seconds) |
|---|
| Total Calls | Total Duration (Seconds) | Avg Duration (Seconds) |
|---|