[CVE-2026-64145][LOW] wifi: wilc1000: fix dma_buffer leak on bus acquire failure [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-64145
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: wifi: wilc1000: fix dma_buffer leak on bus acquire failure [ Upstream
Commit: 95c82d498d74c4e587db30021ca1aec90e29b5a5
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95c82d498d74c4e587db30021ca1aec90e29b5a5
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64145
Analysis date: Sun, 19 Jul 2026 11:43:48 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
No one-sentence report phrase was found.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64145 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64145

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-64145	LOW	CHECK WITH IMPACT FROM ORIG NN IMPORTANT	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;CWE-703;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'wilc1000 firmware download can leak a kmalloc allocated dma_buffer when the first acquire_bus call fails and the function returns before the common cleanup path. This is a resource leak on an early error path, not a use after free or out of bounds memory corruption primitive. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver loading, firmware download, device reset, or bus failure conditions. The issue is not network reachable and does not appear triggerable by WiFi traffic alone. Impact is denial of service only through possible memory pressure after repeated failures, with no supported confidentiality or integrity impact.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)  SKIP CVE-2026-64145 UNKNOWN SKIP No affected files built, so skip this CVE NO  - - unknown 	MAYBE	REMOTE SIMPLEFIX LEAK ERRORPATH NETWORK MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS 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
* Availability impact realistic: +1. Repeated firmware download failures could leak kmalloc memory and eventually contribute to memory pressure.
* Requires admin/root/CAP_* in typical deployments: -2. Reliable triggering normally requires control over driver load, firmware download, device reset, or bus failure conditions.
* Rare AND difficult-to-reach subsystem/configuration: -1. This is specific to wilc1000 hardware and the firmware download error path.
* No memory corruption signal. The patch fixes a leaked allocation on an early return path, not UAF, double free, OOB write, type confusion, or refcount misuse.
* No LPE signal. There is no reclaim, overwrite, stale callback, arbitrary write, or security boundary bypass.
* No remote/network signal. WiFi traffic alone does not appear to trigger the failing acquire_bus path.

3. Reachability analysis
The bug is reachable through wilc1000 firmware download handling when acquire_bus() fails after dma_buffer has already been allocated. In realistic deployments, this path is controlled by privileged driver, firmware, probe, reset, or device-management operations. Namespaces are unlikely to lower the requirement because ordinary unprivileged users normally cannot trigger firmware download or force this specific bus acquire failure. The affected driver is hardware-specific and not a broad/default kernel attack surface.

4. Severity interpretation
This behaves like a low-priority resource leak rather than an actionable Moderate or Important kernel vulnerability. The theoretical worst case is memory pressure after repeated privileged triggering, but the patch does not show memory corruption, sensitive data exposure, privilege escalation, or a network-reachable trigger. Conservative and paranoid scoring remain low because the main impact is limited DoS under privileged and hardware-specific conditions.

5. One-sentence report phrase
A wilc1000 firmware download error path leaked a kmalloc allocated dma_buffer when acquire_bus() failed, causing a local privileged resource leak with possible DoS only after repeated failures.

6. Manual review recommendation
NO MANUAL CHECK NEEDED.
This can be auto-closed for security triage purposes unless the evaluated product exposes wilc1000 firmware download/reset control to untrusted users, because the patch shows only a privileged local memory leak without memory corruption or privilege escalation evidence.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: wifi: wilc1000: fix dma_buffer leak on bus acquire failure [ Upstream
Commit: 95c82d498d74c4e587db30021ca1aec90e29b5a5
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=95c82d498d74c4e587db30021ca1aec90e29b5a5

Changed files:
  drivers/net/wireless/microchip/wilc1000/wlan.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=95c82d498d74c4e587db30021ca1aec90e29b5a5

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64145 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64145

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:L/PR:H/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.4

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).