From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-53103][MODERATE REGULAR] wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync [ Upstream Date: Fri, 26 Jun 2026 15:21:37 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-53103 X-AL-KERNEL-Priority: MODERATE REGULAR X-AL-KERNEL-Severity: MODERATE REGULAR X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 3 X-AL-KERNEL-ActionableScore-Lower: 1 X-AL-KERNEL-Commit: 153bcba36c87a1ba555b57b6c49028d5812f895b List-Id: CVE: CVE-2026-53103 Priority: MODERATE REGULAR AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync [ Upstream Commit: 153bcba36c87a1ba555b57b6c49028d5812f895b Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=153bcba36c87a1ba555b57b6c49028d5812f895b Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53103 Analysis date: Fri, 26 Jun 2026 15:21:37 -0400 ActionableScore: 3 ActionableScore lower bound: 1 Actionable bucket: Borderline, manual review recommended Manual review required: YES Summary: A deadlock in `mt7925_roc_abort_sync()` can occur when synchronous cancellation waits for `roc_work()` while the same mt76 mutex is involved, potentially causing a timing-dependent WiFi driver denial of service during station removal. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53103 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53103 The original announcement does not normally provide a security severity estimate, CVSS assessment, or enough information to determine whether the reported kernel bug represents a practically relevant security issue. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. It combines an autonomous classifier with LLM-assisted technical analysis and a separate ActionableScore mechanism. The purpose of this report is to prioritize Linux kernel CVEs before manual review, identify cases that require prompt investigation, and support automatic closure of issues that are unlikely to have meaningful security impact. Published priority for this report: MODERATE REGULAR Manual review required: YES A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-53103 MODERATE CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H';CWE-667;*CWE-833;**CWE-400;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '5.3';DESCR 'A deadlock in mt7925_roc_abort_sync() can occur when cancel_work_sync() waits for roc_work while the caller already owns the same dev mt76 mutex that roc_work needs. This can happen during station removal and can block progress in the mt7925 WiFi driver, causing a denial of service for the wireless device or the related kernel work path. For the CVSS the PR:N is used in the paranoid score because a nearby attacker or malicious AP may be able to influence station removal without local account access, although reliable triggering still depends on timing with roc_work. The issue is adjacent network plausible rather than Internet reachable. Impact is denial of service only, with no evidence of memory corruption, information disclosure, or privilege escalation.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 2) MAYBE REMOTE DEADLOCK DANGER INIT SIMPLEFIX NETWORK DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=3 ActionableScoreLower=1 ## 1. ActionableScore * Conservative score: 1 * Paranoid score: 3 * Final recommended bucket: **Borderline, manual review recommended** ## 2. Signal breakdown Conservative signals: * Local unprivileged trigger: +1. A local user or desktop network manager path may be able to trigger station removal or reconnect operations on systems where WiFi control is delegated. * Reliable kernel crash / strong DoS: +1. The bug can deadlock the mt7925 driver work path and block progress. * Hard or unreliable race / special timing required: -1. The deadlock requires overlap between `mt7925_roc_abort_sync()` and `roc_work()`. * Rare AND difficult-to-reach subsystem/configuration: -1. This is limited to mt7925 hardware and a specific ROC station-removal path. Paranoid additions: * Adjacent wireless influence treated as practical external trigger concern: +1. A nearby malicious AP or wireless environment may influence disconnect or station removal timing, but this is not Internet-reachable. * Availability impact realistic: +1. In the paranoid case, a stuck WiFi driver path can cause a persistent wireless device DoS until recovery or reboot. No memory corruption, UAF, OOB write, info leak, privilege escalation, Dirty-Pipe-like primitive, or security-boundary bypass is supported by the patch. ## 3. Reachability analysis The direct trigger is in the mt7925 WiFi driver during station removal while ROC work is active. Locally, this may be reachable through WiFi management actions depending on policy and desktop or service configuration. Remotely, this is not network-reachable over IP, but an adjacent wireless attacker or malicious AP may plausibly influence disconnect or station state transitions. The path is hardware-specific and timing-dependent, so reliable exploitation is not established. ## 4. Severity interpretation This behaves like a DoS-only driver deadlock, not an Important-class memory-safety issue. Theoretical impact is limited to availability of the WiFi device or related kernel work path. There is no realistic evidence of confidentiality impact, integrity impact, or privilege escalation. The paranoid score is only elevated because adjacent wireless influence may make the trigger worth manual review. ## 5. One-sentence report phrase A deadlock in `mt7925_roc_abort_sync()` can occur when synchronous cancellation waits for `roc_work()` while the same mt76 mutex is involved, potentially causing a timing-dependent WiFi driver denial of service during station removal. ## 6. Manual review recommendation MANUAL CHECK RECOMMENDED Manual review is recommended to confirm whether adjacent wireless conditions can reliably trigger station removal together with active ROC work on affected mt7925 deployments. This should not be treated as Strong Important without further evidence of memory corruption or privilege escalation. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: wifi: mt76: mt7925: fix potential deadlock in mt7925_roc_abort_sync [ Upstream Commit: 153bcba36c87a1ba555b57b6c49028d5812f895b Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=153bcba36c87a1ba555b57b6c49028d5812f895b Changed files: drivers/net/wireless/mediatek/mt76/mt7925/main.c Diff excerpt: Not included in this email. See the upstream URL for the full patch. Full patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=153bcba36c87a1ba555b57b6c49028d5812f895b ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53103 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53103 The original CVE announcement normally does not include a security-level estimate. In particular, it may not contain a CVSS assessment, an impact level, or enough information to determine whether the reported bug is a practically relevant security issue. One purpose of this parallel CVE list is to provide that missing technical and prioritization information. The original goal of the AL-KERNEL project was to prioritize Linux kernel CVE analysis automatically before manual review. The system can also help identify non-security issues that may be suitable for automatic closure. This report was generated by AL-KERNEL, an AI-assisted Linux kernel vulnerability analysis system developed by Alexander Larkin. The first analysis stage combines an autonomous classifier with additional LLM-based analysis. The autonomous classifier runs locally on a CPU and is based on a backpropagation neural network. Together, these mechanisms produce a technical vulnerability description, identify likely weakness types, estimate CVSS severity, and provide input for ActionableScore. Two CVSS estimates are retained because incomplete kernel vulnerability information often permits more than one defensible interpretation: Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 5.3 The conservative vector represents a lower-impact interpretation. The Best/paranoid vector intentionally represents a plausible upper-bound interpretation and should not automatically be treated as demonstrated real-world impact. CVSS may also need to be adjusted for a particular Linux deployment, because actual reachability, privileges, enabled kernel configuration, hardware, namespaces, exposed device nodes, and other environmental conditions can differ significantly between systems. A separate ActionableScore mechanism evaluates practical remediation urgency. Its analysis may include reachability, attack prerequisites, subsystem exposure, memory-corruption characteristics, denial-of-service reliability, and possible confidentiality, integrity, or privilege-escalation impact. Conservative ActionableScore: 1 Paranoid ActionableScore: 3 The final base severity is taken directly from the second tab-separated field of the AL-KERNEL classification result. ActionableScore does not replace or independently override that final AL-KERNEL decision, and if ActionableScore adjusted impact level of ALKERNEL, then you would see self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7. For an AL-KERNEL result of MODERATE, this report uses the following additional presentation split: ActionableScore below 5 -> MODERATE REGULAR ActionableScore 5 or more -> MODERATE 7.0 The distinction between MODERATE REGULAR and MODERATE 7.0 makes it possible to identify Moderate issues that should receive manual analysis and fixes before lower-priority MODERATE REGULAR issues. In many cases, MODERATE REGULAR fixes may wait for a later rebase or routine update. There is one override in which MODERATE REGULAR becomes MODERATE 7.0 even when the ActionableScore is below 5. When the AL-KERNEL result contains the KPANIC flag, a MODERATE result is always presented as MODERATE 7.0. The KPANIC flag selected with few regexps without usage of AI at all, so it helps to detect cases when Kernel Crash happens and similar (to filter False-Negative results from the LLM usage). KPANIC indicates that a reliable kernel crash, kernel panic, or similarly serious kernel availability impact was identified by the classification workflow. AL-KERNEL base severity for this report: MODERATE KPANIC detected for this report: NO Published priority for this report (same as in Subject): MODERATE REGULAR These results are intended to support engineering triage. They are machine-generated estimates, and cases marked for manual review should be validated by a human security engineer before final disposition. For more info read docs linked from here: https://kernelcve.org/ (and you can submit you own patch there to generate such a report for non-existant CVE-id yet). Note that in many cases this AI tool selects higher severity, than real is (means you can expect Importants instead of Moderate 7.0 or Moderates 7.0 instead of regular Moderates). If you see such cases, please use reply email interface to add additional manual analyses info to this particular CVE. And please, please, let me know when you see Lows instead of Importants or Important instead of Low (because particular for such cases I need to tune this AI tool to make it better for this one and next similar). My contact email for such notifications is alexanjelausa@gmail.com (and both send reply to CVE record itself too and see "reply" button below for howto reply).