* [CVE-2026-98743][LOW] ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type
@ 2026-10-19 8:36 21% AL-KERNEL
0 siblings, 0 replies; 1+ results
From: AL-KERNEL @ 2026-10-19 8:36 UTC (permalink / raw)
To: kernel-cve
CVE: CVE-2026-98743
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type
Commit: 4e337c24c0a97fcdb394f954208971de5d372066
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e337c24c0a97fcdb394f954208971de5d372066
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98743
Analysis date: Mon, 19 Oct 2026 04:36:20 -0400
ActionableScore: 1
ActionableScore lower bound: unknown
Actionable bucket: Ordinary Moderate
Manual review required: NO
Summary:
An uninitialized SoundWire stream type can cause incorrect RT1017 audio stream configuration, but the patch does not establish memory corruption, kernel compromise, or host-wide denial of service.
======================================================================
ABOUT THIS REPORT
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98743 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98743
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-98743 LOW https://www.kernelcve.org/list/?q=CVE-2026-98743 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:L/PR:L/UI:N/S:U/C:N/I:N/A:L';*CWE-457;CWE-665;*CWE-20;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '3.3';DESCR 'An uninitialized type field in the rt1017 SoundWire stream configuration can be copied into stream type when a PCM stream is configured. The stack value may cause the stream to be classified incorrectly and can result in failed or inconsistent audio stream setup. For the CVSS the PR:L value is used because a local process needs permission to access and configure the PCM device. The issue is not network reachable. The demonstrated impact is limited availability loss for the affected audio path. There is no supported UAF, OOB access, information leak, arbitrary write, kernel crash, or privilege escalation primitive. Automated impact decision path. The original SimpleNet classifier selected LOW. 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. 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 NONE and manual review NO. 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 SIMPLEFIX HARDWARE - - checked
======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================
ActionableScore=1
PrimitiveClass=NONE
RealUAF=NO
HostAdminRequired=NO
NamespaceScopedPrivilege=NO
ImportantCandidate=NO
ManualReview=NO
AutoDowngradeAllowed=YES
RequiresHostUID0=NO
AuthorizationDecisionBypass=NO
ProtectedResourceImpact=NONE
B4PendingReview=NO
B4PendingConfirmed=NO
1. ActionableScore
* Raw conservative score: 1
* Conservative score: 1
* Raw paranoid score: 1
* Paranoid score: 1
* No floor or cap was applied.
* Final recommended bucket: **Ordinary Moderate**::
2. Signal breakdown
Positive signals:
* +1 Local below-host-admin trigger. An authorized local PCM client can reach `rt1017_sdca_pcm_hw_params()` through normal audio stream configuration.
* +0 Uninitialized ordinary value. `stream_config.type` contains stack garbage and is copied into `stream->type`, but this does not establish memory corruption or disclosure.
Non-awarded signals:
* No UAF, OOB read, OOB write, heap overwrite, repeated release, or refcount corruption is established.
* No reliable kernel crash or host-wide denial of service is supported. The plausible effect is incorrect or failed audio stream configuration.
* No attacker-controlled payload or target exists. The user selects PCM parameters but does not meaningfully control the uninitialized stack value.
* No confidentiality or integrity signal is awarded because the uninitialized value is not returned to userspace and no protected state modification is demonstrated.
* No authorization decision changes from DENY to ALLOW.
* NEW52 B5-R does not apply because there is no retry-accumulated index and no heap OOB write.
* NEW53 B3-PENDING does not apply because no shared-backing write occurs.
* V33 and V34 do not apply because there is no attacker-influenced active structured-state corruption crossing a trust boundary.
* No hardware rarity penalty is applied merely because this is a codec-specific driver.
Arithmetic:
* Conservative: +1 local below-host-admin reachability = 1.
* Paranoid: +1 local below-host-admin reachability = 1.
* A stronger paranoid score would require unsupported evidence of a kernel crash, memory corruption, disclosure, or protected-state modification.
3. Reachability analysis
An authorized local process can configure a PCM stream and reach the affected `hw_params` callback. This does not require host UID 0 or host-administrator-equivalent privilege, although normal device-node or audio-session permission is required.
The path is not network reachable and is not meaningfully namespace scoped. No prior privileged configuration beyond the presence and normal initialization of the affected RT1017 SoundWire codec is established. There is no race or retry requirement. Triggering depends on hardware using this codec and on the vulnerable driver being active, but hardware specificity alone does not justify a scoring penalty.
4. Primitive and severity interpretation
The exact defect is an uninitialized scalar field in a stack-allocated configuration structure. The field is copied into active SoundWire stream configuration, but the supplied code establishes only an invalid stream-type value, not corruption outside the intended object.
This is neither fixed stale storage nor an active-object lifetime violation. There is no cleanup UAF, repeated lifetime mutation, semantic reinterpretation involving attacker-controlled structured input, or authorization bypass.
PrimitiveClass is `NONE`. The demonstrated consequence is incorrect or inconsistent audio stream setup. A device-local stream failure is plausible. Kernel panic, host-wide denial of service, information disclosure, privilege escalation, and arbitrary state modification are unsupported.
ImportantCandidate is `NO` because no Important-preserving primitive exists. AutoDowngradeAllowed is `YES` because the issue is a localized initialization defect without unresolved corruption or trust-boundary consequences.
5. One-sentence report phrase
An uninitialized SoundWire stream type can cause incorrect RT1017 audio stream configuration, but the patch does not establish memory corruption, kernel compromise, or host-wide denial of service.
6. Manual review recommendation
NO MANUAL CHECK NEEDED
The issue is suitable for automatic low-priority handling because it has no demonstrated corruption, lifetime, authorization, or cross-boundary security primitive.
7. Call-site confidence
Call-site confidence: medium
======================================================================
UPSTREAM PATCH SUMMARY
======================================================================
Patch: ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type
Commit: 4e337c24c0a97fcdb394f954208971de5d372066
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e337c24c0a97fcdb394f954208971de5d372066
Commit description:
stream_config is not initialized before being passed to
sdw_stream_add_slave(). The type field may contain garbage and is
later copied to stream->type by sdw_config_stream().
Zero-initialize stream_config so type defaults to SDW_STREAM_PCM.
While at it, use snd_sdw_params_to_config() helper instead of
open-coding the same logic.
Fixes: 2b7aecd ("ASoC: rt1017: Add RT1017 SDCA amplifier driver")
Cc: [email protected]
Signed-off-by: Jiangshan Yi <[email protected]>
Link: https://patch.msgid.link/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Changed files:
sound/soc/codecs/rt1017-sdca-sdw.c
sound/pcm_params.h
sound/soc.h
sound/soc-dapm.h
sound/sdw.h
sound/initval.h
sound/tlv.h
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=4e337c24c0a97fcdb394f954208971de5d372066
======================================================================
DETAILED REPORT METHODOLOGY
======================================================================
The original Linux kernel CVE announcement for CVE-2026-98743 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-98743
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: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-19 8:36 21% [CVE-2026-98743][LOW] ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type AL-KERNEL
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox