* [CVE-2026-98679][LOW] iio: accel: kxcjk-1013: reject duplicate event disable
@ 2026-10-24 10:29 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-24 10:29 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-98679
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: iio: accel: kxcjk-1013: reject duplicate event disable
Commit: ad690c0c1b9131725619e352cb7c970488cbf436
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad690c0c1b9131725619e352cb7c970488cbf436
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98679
Analysis date: Sat, 24 Oct 2026 06:29:12 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
A duplicate IIO event-disable write can underflow the sensor’s runtime-PM usage counter and emit a warning, without evidence of memory corruption or host-wide failure.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98679 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98679
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-98679 LOW https://www.kernelcve.org/list/?q=CVE-2026-98679 CHECK WITH IMPACT FROM ORIG NN MODERATE | AEGIS IMPACT MODERATE AEGIS_AS=1 LEGACY=LOW RESULT=DIFF (final Legacy and Aegis differ; FINAL: LOW, Aegis: MODERATE) Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L';CWE-191;*CWE-664;CWE-682;Other CVSS 'AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '3.3';DESCR 'A duplicate disable write to the kxcjk1013 event enable attribute can call the runtime PM put path without a matching reference and trigger a Runtime PM usage count underflow warning. The demonstrated primitive is an attempted reference count imbalance affecting device power management. There is no evidence of UAF, out of bounds access, information disclosure, privilege escalation, or a host wide crash. For the CVSS the PR:L value in the paranoid score reflects a local user or delegated service that can write the IIO event sysfs attribute, although default permissions commonly restrict this operation to root. The issue is not network reachable and the supported impact is limited availability degradation of the sensor or log consumption from repeated warnings. Automated impact decision path. The original SimpleNet classifier selected MODERATE_KPANIC. The primary LLM estimated paranoid CVSS 3.3 and the production ActionableScore returned 1 with recommendation Ordinary Moderate. The production rules then evaluated CVSS thresholds and ActionableScore thresholds. Recorded rule transitions were CVSS and initial triage stage MODERATE_KPANIC to MODERATE because the CVSS score, vector or bug class threshold rule was applied. ActionableScore thresholds stage MODERATE to LOW because the ActionableScore threshold rule was applied. final reconciliation stage LOW to LOW because KP specialist did not establish a qualifying panic and the cross model evidence reconciliation rule was applied. 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. Exact triggered rule markers were DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS and DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 and KPANIC_UNSUPPORTED_REMOVED and V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED. The independent weaker Aegis shadow evaluated CVSS 3.3 and ActionableScore 1 with primitive class CLASS_C and manual review REQUIRED. Its independently reconciled impact was MODERATE. The models disagreed but the aggregation rules retained the production result. The final reported impact is LOW.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate (with actual score 1) MAYBE OOB SIMPLEFIX LINUS DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3 KPANIC_UNSUPPORTED_REMOVED V64_AEGIS_UNSUPPORTED_PROMOTION_BLOCKED - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=1
PrimitiveClass=CLASS_C
RealUAF=NO
HostAdminRequired=UNKNOWN
NamespaceScopedPrivilege=NO
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; no supported stronger consequence.
* Final recommended bucket: **Ordinary Moderate**::
2. Signal breakdown
* +1 weak invalid-state mutation: a duplicate disable performs an unmatched runtime-PM put, allowing the device’s PM usage count to underflow.
* +0 WARN_ON: the patch supports a runtime-PM underflow warning, not a fatal kernel crash.
* No UAF, object-lifetime-ending refcount operation, OOB access, arbitrary write, disclosure, authorization bypass, or protected-state corruption is shown.
* No availability point: sensor degradation or log consumption is plausible but not established by the patch.
* NEW52/B5-R does not apply: there is no heap OOB write or later consumption of corrupted descriptors.
* No retry-refcount escalation: the PM usage counter does not establish a repeated release of a potentially freed object.
3. Reachability analysis
The trigger is a duplicate write to an IIO event-enable sysfs attribute. Exact permissions and the complete below-host-admin path are not supplied, so host-admin requirements and host UID 0 requirements remain unknown. No namespace capability path, network reachability, special race, or unusual hardware penalty is established.
4. Primitive and severity reading
The exact defect is an unmatched runtime-PM reference decrement affecting active device-power bookkeeping. It is neither a real UAF nor a repeated object-lifetime mutation because the PM usage counter does not itself free the device object. The demonstrated effect is a warning and invalid PM state; broader device failure is unproven. This is CLASS_C, not an Important-preserving corruption primitive. Auto-downgrade is allowed because no material unknown memory-corruption or trust-boundary chain remains.
5. One-sentence report phrase
A duplicate IIO event-disable write can underflow the sensor’s runtime-PM usage counter and emit a warning, without evidence of memory corruption or host-wide failure.
6. Manual review advice
NO MANUAL CHECK NEEDED
The patch shows a narrow device power-management bookkeeping error with no Important-class primitive.
7. Call-site confidence
Call-site confidence: high
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: iio: accel: kxcjk-1013: reject duplicate event disable
Commit: ad690c0c1b9131725619e352cb7c970488cbf436
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad690c0c1b9131725619e352cb7c970488cbf436
Commit description:
The IIO core does not filter duplicate writes to the event enable
attribute. kxcjk1013_write_event_config() already ignores repeated
enable requests, but a repeated disable request still calls
kxcjk1013_set_power_state(data, false), dropping a runtime PM reference
that was not acquired for this request. This can underflow the runtime
PM usage count and trigger a "Runtime PM usage count underflow" warning.
Return early when the requested state already matches ev_enable_state.
Fixes: b4b491c ("iio: accel: kxcjk-1013: Support thresholds")
Signed-off-by: Jiale Yao <[email protected]>
Cc: [email protected]
Signed-off-by: Jonathan Cameron <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Changed files:
drivers/iio/accel/kxcjk-1013.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=ad690c0c1b9131725619e352cb7c970488cbf436
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98679 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98679
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:L/UI:N/S:U/C:N/I:N/A:L
The Best / paranoid CVSS score: 3.3
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 [email protected] (and both
send reply to CVE record itself too and see "reply" button below for howto reply).
^ permalink raw reply [relevance 21%]
Results 1-1 of 1 | reverse | sort options + mbox downloads above
-- links below jump to the message on this page --
2026-10-24 10:29 21% [CVE-2026-98679][LOW] iio: accel: kxcjk-1013: reject duplicate event disable AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox