[CVE-2026-80643][LOW] EDAC/igen6: Fix call trace due to missing release() [ Upstream

[CVE-2026-80643][LOW] EDAC/igen6: Fix call trace due to missing release() [ Upstream

[AL-KERNEL]

CVE: CVE-2026-80643
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: EDAC/igen6: Fix call trace due to missing release() [ Upstream
Commit: 9a84ced0243c74aa431ec287555054c69e6167d1
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9a84ced0243c74aa431ec287555054c69e6167d1
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80643
Analysis date: Fri, 28 Aug 2026 07:07:56 -0400
ActionableScore: 0
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: YES

Summary:
No one-sentence report phrase was found.

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

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

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: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-80643	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	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-703;CWE-665;CWE-404;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.4';DESCR 'The igen6_edac driver registered an embedded memory controller device without a release callback, so driver unload can reach device_release and emit a kernel warning call trace. This is a device lifetime management bug in the local driver teardown path, not a direct memory corruption primitive based on the patch context. For the CVSS the PR:H is used because reliable triggering normally requires administrative control such as unloading the module or unbinding the driver. The issue is not network reachable. Impact is mainly a local availability concern, with a higher paranoid availability impact only for systems where kernel warnings can panic the host.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 0)	YES	SIMPLEFIX HARDWARE  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	NO	NO	checked

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

ActionableScore=0

1. ActionableScore
* Conservative score: 0
* Paranoid score: 0
* Final recommended bucket: **Ordinary Moderate / Low-like**::

2. Signal breakdown
* Warning / call trace concern: +1. The patch fixes a missing device release callback that triggers a kernel warning during driver unload.
* Requires admin/root/CAP_SYS_MODULE in typical deployments: -2. Reliable triggering requires unloading the igen6_edac driver or unbinding the device, which is normally administrative.
* Rare AND difficult-to-reach subsystem/configuration: -1. This is an EDAC driver path for specific Intel client SoCs using IBECC and only the unload/remove path is affected.
* No memory corruption signal: +0. The patch does not show UAF, double free, OOB access, type confusion, arbitrary write, refcount takeover, or attacker-controlled reuse.
* No LPE signal: +0. There is no supported privilege escalation primitive.
* No confidentiality or integrity signal: +0. No data disclosure or unauthorized modification path is shown.
* Availability impact: +0 conservative. The demonstrated impact is a warning/call trace, not a normal reliable crash unless panic_on_warn or similar policy is enabled.

3. Reachability analysis
The bug is local and privileged. A normal unprivileged user cannot unload this driver or reliably force the remove path in typical deployments. Containers or namespaces do not materially lower the requirement unless the container has dangerous host-level device or module-management privileges, which would already be close to administrative control. The path is not network reachable and is not a packet, filesystem, KVM, BPF, or high-control unprivileged API path. Realistic exploitation conditions are limited to administrative driver unload or hardware management operations.

4. Severity interpretation
This behaves like a Low-like or ordinary Moderate kernel correctness issue rather than an actionable Moderate or Important vulnerability. The theoretical concern is device lifetime management, but the provided patch only adds an empty release callback and does not demonstrate a concrete memory corruption or security-boundary bypass. The realistic evidence is a local warning/call trace during rmmod. A higher CVSS availability interpretation is only relevant for systems configured to panic on warnings.

5. One-sentence report phrase
The igen6_edac driver could emit a kernel warning call trace during privileged driver unload because an embedded memory controller device lacked a release callback, with no evidence of memory corruption, privilege escalation, or network reachability.

6. Manual review recommendation
NO MANUAL CHECK NEEDED. NO MANUAL CHECK REQUIRED COULD BE AUTOCLOSED.
Reason: the issue is privileged, non-network-reachable, warning-only in the normal case, and has no supported memory corruption or security-boundary bypass primitive.

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

Patch: EDAC/igen6: Fix call trace due to missing release() [ Upstream
Commit: 9a84ced0243c74aa431ec287555054c69e6167d1
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=9a84ced0243c74aa431ec287555054c69e6167d1

Changed files:
  drivers/base/core.c
  drivers/edac/igen6_edac.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=9a84ced0243c74aa431ec287555054c69e6167d1

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

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

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