[CVE-2026-90119][LOW] ALSA: ice1712: Fix the card leak at probe error with the auto-cleanup [ Upstream

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

CVE: CVE-2026-90119
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ALSA: ice1712: Fix the card leak at probe error with the auto-cleanup [ Upstream
Commit: c5c7c7b6cfae73c46e4544a9ef08ff89231a670d
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c5c7c7b6cfae73c46e4544a9ef08ff89231a670d
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90119
Analysis date: Fri, 18 Sep 2026 01:30:44 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
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-90119 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-90119

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-90119	LOW	https://www.kernelcve.org/list/?q=CVE-2026-90119 CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';*CWE-401;*CWE-772;CWE-404;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.1';DESCR 'snd_ice1712_probe() can leak ALSA card resources when a later initialization step fails after card allocation. The issue is an error path resource leak during PCI sound driver probing rather than a use after free or direct memory corruption primitive. For the CVSS the PR:H is used because reliable triggering normally requires administrative control over driver loading, PCI device binding, reprobe, or a comparable local hardware management operation. The issue is not network reachable and cannot be triggered by remote audio or network traffic. Impact is denial of service only through possible resource exhaustion if probe failures can be repeated many times on an affected system.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 0)	YES	INIT SIMPLEFIX LEAK HARDWARE LINUS 	NO	NO	checked

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

ActionableScore=0
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=YES
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES

1. ActionableScore

* Raw conservative score: -1
* Conservative score: 0
* Raw paranoid score: 0
* Paranoid score: 0
* Applied floor/cap: score was clamped at 0 because ActionableScore is not negative.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

Positive signals:

* +1 Concrete persistent kernel resource/reference leak. The patch directly establishes that an ALSA card object allocated during `snd_ice1712_probe()` can be lost on later probe failure paths.
* +1 Paranoid resource accumulation concern. Repeated failed probes could theoretically accumulate leaked card resources and cause resource pressure.

Negative signals:

* -2 Host-admin-equivalent trigger requirement. Reliable triggering requires control over PCI driver probing, module loading, driver bind/unbind, reprobe, or equivalent host device-management operations.

Important non-awarded signals:

* RealUAF not awarded. The patch fixes a missing release on an error path, not a stale post-free use.
* Concrete repeated release/refcount not awarded. There is no first release followed by a second lifetime mutation on the same dangling reference.
* Controlled reclaim not demonstrated.
* Arbitrary write not demonstrated.
* Confidentiality and integrity not awarded. The established effect is resource leakage only.
* Remote reachability not established.
* Extra availability not awarded conservatively because immediate host-wide crash or exhaustion is not demonstrated.
* Hardware rarity was not separately penalized to avoid double-counting the host-admin/device-management restriction.

3. Reachability analysis

The affected path is PCI sound driver probe for ALSA ice1712 hardware. An ordinary local user is not shown to be able to trigger the complete vulnerable operation. Reliable repeated triggering would normally require host administrator control over driver loading, PCI device binding or unbinding, reprobe, or equivalent device-management operations.

No namespace-scoped capability path is established. There is no network exposure. Prior hardware and driver availability are required, but the main practical attacker requirement is host-level device-management privilege. No race is involved.

4. Primitive and severity interpretation

The exact primitive is a persistent resource leak after successful ALSA card allocation followed by later probe failure. This is not active structured UAF, not fixed stale storage UAF, and not a repeated release/refcount corruption case.

Demonstrated consequence is leaked kernel/ALSA card resources during probe failure. Speculative consequence is resource exhaustion if a privileged actor can repeatedly force probe failures. There is no meaningful exploitation leverage beyond resource consumption, no memory corruption, no authorization bypass, and no privilege escalation path.

PrimitiveClass is NONE because no corruption, stale-object use, ownership violation, or security-boundary primitive is established. ImportantCandidate is NO because the issue is a host-admin-gated resource leak without unresolved Important-grade leverage. AutoDowngradeAllowed is YES because automatic downgrade would not discard a meaningful unresolved corruption or boundary primitive.

Likely operational severity is Low / ordinary Moderate.

5. One-sentence report phrase

ALSA ice1712 probe error handling can leak an allocated sound card object when later initialization fails, but exploitation is host-admin-gated and the impact is limited to possible local resource exhaustion.

6. Manual review recommendation

NO MANUAL CHECK NEEDED

Reason: this is a concrete resource leak only, with no UAF, no repeated refcount mutation, no memory corruption, no network trigger, and no plausible below-host-admin attacker path in the supplied evidence.

7. Call-site confidence

Call-site confidence: high

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

Patch: ALSA: ice1712: Fix the card leak at probe error with the auto-cleanup [ Upstream
Commit: c5c7c7b6cfae73c46e4544a9ef08ff89231a670d
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c5c7c7b6cfae73c46e4544a9ef08ff89231a670d

Changed files:
  sound/pci/ice1712/ice1712.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=c5c7c7b6cfae73c46e4544a9ef08ff89231a670d

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

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

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:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.1

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