From mboxrd@z Thu Jan 1 00:00:00 1970 From: AL-KERNEL To: kernel-cve@kernelcve.org Subject: [CVE-2026-72343][MODERATE 7.0] net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation [ Upstream Date: Sat, 15 Aug 2026 06:14:40 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-AL-KERNEL-CVE: CVE-2026-72343 X-AL-KERNEL-Priority: MODERATE 7.0 X-AL-KERNEL-Severity: MODERATE 7.0 X-AL-KERNEL-Base-Severity: MODERATE X-AL-KERNEL-KPANIC: NO X-AL-KERNEL-ActionableScore: 5 X-AL-KERNEL-ActionableScore-Lower: 3 X-AL-KERNEL-Commit: 3b3a552cf88e10bb7bda88b29cf1fd8267043d50 List-Id: CVE: CVE-2026-72343 Priority: MODERATE 7.0 AL-KERNEL base severity: MODERATE KPANIC flag: NO Patch: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation [ Upstream Commit: 3b3a552cf88e10bb7bda88b29cf1fd8267043d50 Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3b3a552cf88e10bb7bda88b29cf1fd8267043d50 Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72343 Analysis date: Sat, 15 Aug 2026 06:14:40 -0400 ActionableScore: 5 ActionableScore lower bound: 3 Actionable bucket: Strong Important candidate / Actionable Moderate at minimum Manual review required: YES Summary: mlx5e HV VHCA stats can allocate a zero sized buffer before channels are opened, leading to a later ZERO_SIZE_PTR memset crash, with additional patch context indicating possible constrained buffer overrun and stale double-free risks in device lifecycle handling. ====================================================================== ABOUT THIS REPORT ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72343 is available here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72343 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 7.0 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-72343 MODERATE CHECK WITH IMPACT FROM ORIG NN MODERATE Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H';CWE-131;**CWE-476;*CWE-787;CWE-415;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '7';DESCR 'mlx5e HV VHCA stats creation can allocate a zero sized buffer before channels are opened because stats_nch is still 0. kvzalloc(0) returns ZERO_SIZE_PTR rather than NULL, so the later stats worker can call memset on address 0x10 after stats_nch becomes non zero and crash the kernel. The primary practical impact is local or environment dependent denial of service on systems using this mlx5e Hyper-V stats path. The patch context also indicates a possible smaller-buffer overrun when max_nch is recomputed downward while stats_nch persists, and stale pointers could otherwise be freed again after a failed recreate path. For the CVSS the PR:L is used in the paranoid score because delegated CAP_NET_ADMIN, a network management service account, or reduced-capability root may be enough to influence device reset or enable cycles in some deployments. The issue is not directly network reachable from packet traffic. For the paranoid score, choose the highest still-defensible interpretation supported by the bug class and patch context, with preference for manual-review sensitivity over autoclosed false negatives.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 4) SKIP CVE-2026-72343 UNKNOWN SKIP No affected files built, so skip this CVE NO - - unknown MAYBE REMOTE OOB DANGER UAF NETWORK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5 - - checked ====================================================================== ACTIONABLESCORE ANALYSIS ====================================================================== ActionableScore=5 ActionableScoreLower=3 ## 1. ActionableScore * Conservative score: 3 * Paranoid score: 5 * Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**:: Interpretation: handle as **Actionable Moderate with Important-candidate manual review**, not as an auto-closable ordinary Moderate. ## 2. Signal breakdown Triggered signals: * Reliable kernel crash / strong DoS: +1 `kvzalloc(0)` returns `ZERO_SIZE_PTR`, then later `memset()` on address `0x10` can fault and crash the kernel. * Firmware-mediated external influence: +1 The crash path depends on Hyper-V / HV VHCA stats reporting being enabled, so this is not ordinary packet-level remote reachability but is device or hypervisor mediated. * Memory layout invariant restoration: +1 The patch restores consistency between allocation size and later active payload size by allocating from `max(max_nch, stats_nch)` while the worker uses `stats_nch`. * Weak / indirect corruption candidate: +1 The commit explicitly describes a possible smaller-buffer overrun if `max_nch` is recomputed downward while `stats_nch` persists. The primitive is not shown as attacker-controlled, so this is not scored as strong arbitrary corruption. * Real lifetime corruption concern: +1 The patch clears stale `agent` and `buf` pointers after destroy to avoid later double-free after a failed recreate path. * Privileged kernel/device-management memory corruption path: +1 The issue is in a trusted mlx5e device-management / HV stats path, not a normal userspace data parser. Negative or limiting signals: * Corruption primitive constrained / no attacker-controlled payload or target: -1 The overrun and double-free concerns are real enough for manual review, but the patch does not show controlled overwrite data, controlled target selection, reclaim, or callback control. Conservative lowering: * In typical deployments, reliable triggering likely requires specific mlx5e Hyper-V VHCA stats configuration and device lifecycle conditions. This keeps the lower score at 3. ## 3. Reachability analysis This is not directly reachable through ordinary network packet traffic. The affected path is the mlx5e HV VHCA stats agent, with triggering tied to NIC enable/open ordering and later hypervisor-enabled stats reporting. A local unprivileged user normally should not be able to directly trigger the full lifecycle. However, reduced-capability root, a network-management service account, delegated `CAP_NET_ADMIN`, or a virtualization management path may influence reset, enable, disable, or device lifecycle operations in some environments. Namespaces and containers do not automatically make this unprivileged, but container root or delegated network administration should not be treated the same as full host root for practical triage. ## 4. Severity interpretation This is stronger than an ordinary NULL dereference because the commit also addresses a possible buffer overrun and stale double-free cleanup hazard. The most realistic demonstrated impact is kernel crash / DoS in a specific mlx5e Hyper-V stats configuration. Theoretical memory corruption concern exists, but practical privilege escalation is not demonstrated. There is no evidence of arbitrary write, controlled reclaim, object replacement, callback hijack, or direct packet-triggered remote exploitability. Therefore this is best treated as **Actionable Moderate**, with **Important-candidate manual review** due to the overrun and lifetime cleanup aspects. ## 5. One-sentence report phrase mlx5e HV VHCA stats can allocate a zero sized buffer before channels are opened, leading to a later ZERO_SIZE_PTR memset crash, with additional patch context indicating possible constrained buffer overrun and stale double-free risks in device lifecycle handling. ## 6. Manual review recommendation MANUAL CHECK REQUIRED Reason: the primary observed failure is DoS, but the patch also fixes a possible smaller-buffer overrun and stale pointer double-free condition, so this should not be auto-closed without human review. ====================================================================== UPSTREAM PATCH SUMMARY ====================================================================== Patch: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation [ Upstream Commit: 3b3a552cf88e10bb7bda88b29cf1fd8267043d50 Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3b3a552cf88e10bb7bda88b29cf1fd8267043d50 Changed files: drivers/net/ethernet/mellanox/mlx5/core/en/hv_vhca_stats.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=3b3a552cf88e10bb7bda88b29cf1fd8267043d50 ====================================================================== DETAILED REPORT METHODOLOGY ====================================================================== The original Linux kernel CVE announcement for CVE-2026-72343 can be found here: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72343 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:H The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H The Best / paranoid CVSS score: 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: 3 Paranoid ActionableScore: 5 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 7.0 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).