[CVE-2026-98680][LOW] iio: accel: kionix-kx022a: Prevent memory leak and fix state [ Upstream

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

CVE: CVE-2026-98680
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: iio: accel: kionix-kx022a: Prevent memory leak and fix state [ Upstream
Commit: e3bc345d08639e62b629e0ec0799f7fb45e21372
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e3bc345d08639e62b629e0ec0799f7fb45e21372
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98680
Analysis date: Sat, 24 Oct 2026 11:27:48 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO

Summary:
A failed KX022A FIFO enable leaks its sample buffer and can leave FIFO/WMI state partially enabled, with only device disruption or cumulative resource loss supported.

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

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

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-98680	LOW	https://www.kernelcve.org/list/?q=CVE-2026-98680 CHECK WITH IMPACT FROM ORIG NN LOW | AEGIS IMPACT LOW AEGIS_AS=0 LEGACY=LOW RESULT=SAME (final reconciliation agrees; DECISION: both LOW)	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-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 'An error during kx022a FIFO enable can leave the allocated sample buffer unreleased and can preserve partially applied hardware or driver state. Repeated failed enable attempts could accumulate kernel memory loss, while an enabled FIFO or WMI interrupt and an incorrect FIFO state flag could disrupt later device operation. For the CVSS the PR:L reflects the need for a local user or process that can control the IIO buffer interface. AC:H reflects the additional requirement for a regmap or hardware transition failure. No UAF, OOB access, information disclosure, or write primitive is established, so confidentiality and integrity remain N. Automated impact decision path. The original SimpleNet classifier selected LOW. The primary LLM estimated paranoid CVSS 4.7 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. No severity changing production threshold or specialist override was recorded. The legacy KP specialist has no review artifact for this run. The legacy FD or DH downgrade specialist has no review artifact for this run. The independent weaker Aegis shadow evaluated CVSS 0.0 and ActionableScore 0 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was LOW. The shadow agreed with the final production impact and aggregation did not change that impact. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1)	MAYBE	INIT LEAK ERRORPATH HARDWARE LINUS 	-	-	checked

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

ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=UNKNOWN
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=UNKNOWN
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO

1. ActionableScore

* Raw base score: 1.
* Conservative score: 1; no floor or cap applied.
* Raw paranoid score: 1.
* Paranoid score: 1; repeated retries and host-wide exhaustion are not established.
* Final recommended bucket: **Ordinary Moderate**::

2. Signal breakdown

* +1 Concrete persistent kernel resource leak: `fifo_buffer` is allocated before this function and was not freed on any shown regmap or power-transition failure.
* +0 Invalid device state: failures could leave FIFO/WMI hardware bits and `KX022A_STATE_FIFO` inconsistent, but only device disruption is supported.
* +0 Resource exhaustion: repeated failed enables could accumulate leaks, but retry reachability, practical accumulation, and host-wide pressure are not shown.
* No UAF, OOB write, shared-backing write, authorization bypass, disclosure, or protected-state corruption is established.
* B5-R does not apply: there is no retry-accumulated index or confirmed heap OOB write.
* B3-PENDING and B4-PENDING do not apply.

3. Reachability analysis

The vulnerable operation is the IIO buffer-enable path and additionally requires a regmap or hardware transition failure. The supplied evidence does not establish which users may invoke the complete operation, whether device-node permissions permit an ordinary user, or whether host-administrator powers are required. No namespace-scoped capability path, special retry control, or remote trigger is shown. Hardware presence is required, but it is not proven rare enough for a penalty.

4. Primitive and severity reading

The proven defect is a persistent allocation leak plus incomplete rollback of device-local hardware and driver state. This is invalid-state/resource-management behavior, classified CLASS_C, not memory corruption or a lifetime-after-free primitive. Plausible effects are memory loss and malfunction of the affected sensor path; host panic or meaningful cross-boundary integrity impact remains unproven. There is no Important-preserving primitive, so automatic Moderate handling is allowed.

5. One-sentence report phrase

A failed KX022A FIFO enable leaks its sample buffer and can leave FIFO/WMI state partially enabled, with only device disruption or cumulative resource loss supported.

6. Manual review advice

NO MANUAL CHECK NEEDED

The patch shows straightforward error-unwind and state-restoration defects without a corruption or security-boundary primitive.

7. Call-site confidence

Call-site confidence: medium

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

Patch: iio: accel: kionix-kx022a: Prevent memory leak and fix state [ Upstream
Commit: e3bc345d08639e62b629e0ec0799f7fb45e21372
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e3bc345d08639e62b629e0ec0799f7fb45e21372

Changed files:
  drivers/iio/accel/kionix-kx022a.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=e3bc345d08639e62b629e0ec0799f7fb45e21372

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

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

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

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