From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-53113][LOW] wifi: ath11k: fix memory leaks in beacon template setup [ Upstream Date: Fri, 26 Jun 2026 09:03:31 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-53113 X-AL-KERNEL-Priority: LOW X-AL-KERNEL-Severity: LOW X-AL-KERNEL-Base-Severity: LOW X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 0 X-AL-KERNEL-ActionableScore-Lower: unknown X-AL-KERNEL-Commit: 5d63aa38d5ca85206d9699ffdd616b58780dba07 List-Id: CVE: CVE-2026-53113 Priority: LOW AL-KERNEL base severity: LOW KPANIC flag: NO Patch: wifi: ath11k: fix memory leaks in beacon template setup [ Upstream Commit: 5d63aa38d5ca85206d9699ffdd616b58780dba07 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5d63aa38d5ca85206d9699ffdd616b58780dba07 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53113 Analysis date: Fri, 26 Jun 2026 09:03:31 -0400 ActionableScore: 0 ActionableScore lower bound: unknown Actionable bucket: Ordinary Moderate / Low-like Manual review required: NO Summary: ath11k beacon template setup may leak allocated skb or EMA beacon-list memory on parameter setup errors, but triggering normally requires privileged WiFi AP configuration and the impact is limited to gradual resource exhaustion. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53113 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53113 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: LOW Manual review required: NO A detailed explanation of the methodology and priority rules is included at the end of this message. ====================================================================== AL-KERNEL CLASSIFICATION RESULT ====================================================================== CVE-2026-53113 LOW CHECK Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;**CWE-400;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'ath11k beacon template setup can leak allocated skb or EMA beacon list memory when parameter setup returns an error before the normal release path. A local attacker cannot trigger this through ordinary WiFi traffic alone because the affected path is part of AP beacon template configuration and driver control. For the CVSS the PR:L paranoid case covers environments where untrusted local users have delegated wireless administration or CAP_NET_ADMIN through a container or service account. Typical systems may be closer to PR:H because AP configuration is administrator controlled. Impact is denial of service through gradual kernel memory exhaustion after repeated failing configuration attempts. There is no evidence of a UAF, OOB access, information disclosure, or privilege escalation primitive in this patch context.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0) MAYBE REMOTE INIT SIMPLEFIX LEAK ERRORPATH NETWORK SKB LINUS TEST LOWERED_FROM_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=0 ## 1. ActionableScore * Conservative score: 0 * Paranoid score: 0 * Final recommended bucket: **Ordinary Moderate / Low-like**:: ## 2. Signal breakdown Positive signals: * Availability impact realistic: +1 The bug is a memory leak in ath11k beacon template setup error paths. Repeated failing AP configuration attempts could gradually consume kernel memory. Negative signals: * Requires admin or CAP_NET_ADMIN in typical deployments: -2 The affected path is WiFi AP beacon template configuration and driver control, not ordinary WiFi packet reception. * Rare and configuration-dependent subsystem path: -1 Requires ath11k hardware and AP or MBSSID/EMA beacon template setup paths. Not applied: * No generic memory corruption. The patch fixes missing frees, not UAF, double free, OOB write, or type confusion. * No privilege escalation plausible from the diff. * No remote/network-triggerable path. Ordinary WiFi traffic does not appear sufficient to trigger this path. * No strong DoS signal. Exhaustion would require repeated failing configuration attempts, not a single reliable crash. ## 3. Reachability analysis The bug is triggerable through local WiFi configuration paths that set up ath11k beacon templates. In normal deployments this requires administrator-controlled network management or CAP_NET_ADMIN. A delegated container or service account with wireless administration rights could lower the practical privilege barrier, but this is still not an unprivileged local interface. The path is hardware-specific and depends on ath11k AP beacon template setup behavior. Realistic exploitation would require repeated attempts to hit the error paths and accumulate leaked skb or EMA beacon-list allocations. ## 4. Severity interpretation This behaves like a Low-like or ordinary Moderate resource leak, not an Important-class vulnerability. The theoretical impact is denial of service through gradual memory exhaustion, but there is no evidence of memory corruption, object lifetime misuse, information disclosure, privilege escalation, or a remote trigger. The issue should not be treated as Actionable Moderate unless an external report demonstrates that unprivileged users can repeatedly trigger the failing configuration path at scale. ## 5. One-sentence report phrase ath11k beacon template setup may leak allocated skb or EMA beacon-list memory on parameter setup errors, but triggering normally requires privileged WiFi AP configuration and the impact is limited to gradual resource exhaustion. ## 6. Manual review recommendation NO MANUAL CHECK NEEDED This is a constrained resource leak in a driver configuration path with admin-level triggering in typical deployments and no supported memory-corruption or privilege-escalation primitive. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: wifi: ath11k: fix memory leaks in beacon template setup [ Upstream Commit: 5d63aa38d5ca85206d9699ffdd616b58780dba07 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5d63aa38d5ca85206d9699ffdd616b58780dba07 Changed files: drivers/net/wireless/ath/ath11k/mac.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=5d63aa38d5ca85206d9699ffdd616b58780dba07 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-53113 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-53113 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:H/UI:N/S:U/C:N/I:N/A:L The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H The Best / paranoid CVSS score: 4.7 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: unknown Paranoid ActionableScore: 0 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: LOW KPANIC detected for this report: NO Published priority for this report (same as in Subject): LOW 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).