[CVE-2026-90330][LOW] HID: logitech-hidpp: Fix FF device cleanup on init failure [ Upstream

[CVE-2026-90330][LOW] HID: logitech-hidpp: Fix FF device cleanup on init failure [ Upstream

[AL-KERNEL]

CVE: CVE-2026-90330
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: HID: logitech-hidpp: Fix FF device cleanup on init failure [ Upstream
Commit: 13378c9ac0a1bcdf49ba158e4199594aafb589cd
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13378c9ac0a1bcdf49ba158e4199594aafb589cd
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90330
Analysis date: Thu, 17 Sep 2026 18:05:23 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
No one-sentence report phrase was found.

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

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

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-90330	LOW	https://www.kernelcve.org/list/?q=CVE-2026-90330 CHECK WITH IMPACT FROM ORIG NN NONE	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-404;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A cleanup bug in hidpp_ff_init can leave a force feedback input device allocated when input_ff_create() succeeds but later private allocations or workqueue creation fail. This is a resource leak on an initialization failure path rather than a memory corruption primitive. For the CVSS the PR:L is used for the conservative case because a local user may be able to contribute to memory pressure or repeated device initialization only in environments where the HID device path is exposed. The issue is not network reachable and depends on a local Logitech HIDPP force feedback device or repeated driver probe conditions. Impact is denial of service through resource leakage only, with no supported path to information disclosure or privilege escalation.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 2)	YES	USB INIT NOMEMCHK SIMPLEFIX HARDWARE LINUS 	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: 1
* Conservative score: 1. No floor or cap applied.
* Raw paranoid score: 2
* Paranoid score: 2. No floor or cap applied.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 conservative. Concrete persistent kernel resource/reference leak: `input_ff_create()` succeeds, but later allocation failures return without `input_ff_destroy(dev)`, leaving the force feedback input resources allocated.
* +1 paranoid additional. Sustained repeated init failures could theoretically accumulate leaked FF resources and contribute to local resource exhaustion, but this remains constrained and DoS-only.
* RealUAF not awarded. No stale post-free dereference, double release, or post-lifetime object use is established.
* Reliable kernel crash not awarded. The patch documents a leak on init failure, not a direct panic or fatal fault.
* Confidentiality and integrity not awarded. No disclosure, overwrite, authorization bypass, or memory corruption primitive is shown.
* Controlled reclaim, arbitrary write, callback control, and privilege escalation are not demonstrated.
* Remote reachability not awarded. This is a local HID driver initialization path.
* No race or timing penalty applied. This is an ordered error-unwind bug, not a timing race.

3. Reachability analysis

The vulnerable path is reached during initialization of Logitech HID++ force feedback support, after `input_ff_create()` succeeds and later private allocation or workqueue creation fails. A practical trigger depends on a compatible Logitech HIDPP force feedback device and on causing allocation failure or repeated probe failure conditions. Host administrator privilege is not positively established as required, but a complete ordinary unprivileged trigger is also not established from the supplied evidence. Namespace-scoped privilege is not relevant. There is no network vector, no sysctl or boot-only prerequisite shown, and no special race requirement.

4. Primitive and severity interpretation

The exact primitive is a cleanup/unwind resource leak: an FF input device is created and ownership is partially transferred, but failure paths after that point do not destroy the FF device. This is not an active structured UAF and not fixed stale storage being accessed after free. There is no concrete repeated release/refcount operation. The demonstrated consequence is persistent resource leakage during initialization failure. The speculative consequence is local resource exhaustion if the failure can be repeated many times. PrimitiveClass is NONE because no corruption, UAF, authorization bypass, ownership violation, or meaningful exploitation primitive is established. ImportantCandidate is NO because the issue is DoS/resource-leak-only and lacks unresolved memory corruption or security-boundary leverage. AutoDowngradeAllowed is YES because automatic downgrade would not discard a meaningful unresolved kernel exploitation primitive.

5. One-sentence report phrase

A cleanup bug in `hidpp_ff_init()` can leak a force feedback input device when initialization fails after `input_ff_create()`, causing a local resource leak with only potential DoS impact under repeated failure conditions.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a low-severity resource leak on an initialization failure path, with no UAF, memory corruption, authorization bypass, or privilege-escalation primitive established.

7. Call-site confidence

Call-site confidence: high

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

Patch: HID: logitech-hidpp: Fix FF device cleanup on init failure [ Upstream
Commit: 13378c9ac0a1bcdf49ba158e4199594aafb589cd
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=13378c9ac0a1bcdf49ba158e4199594aafb589cd

Changed files:
  drivers/hid/hid-logitech-hidpp.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=13378c9ac0a1bcdf49ba158e4199594aafb589cd

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

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

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: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: 1
  Paranoid ActionableScore: 2

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