# CVE-2026-98743: ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type

> An uninitialized variable in the Linux kernel's rt1017-sdca-sdw codec driver may leak stack memory contents to local attackers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-109065, BELL-CVE-2026-98743, DEBIAN-CVE-2026-98743, GHSA-33xw-2m9p-9fgf, UBUNTU-CVE-2026-98743

## What is CVE-2026-98743?

CVE-2026-98743 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ASoC: codecs: rt1017-sdca-sdw: fix uninitialized stream_config->type

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.

## Which versions are affected by CVE-2026-98743?


## How do I fix CVE-2026-98743?

Apply the vendor's patch.

## Is CVE-2026-98743 being exploited?

There is no known exploitation of CVE-2026-98743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98743 and fix it if it is affected.

What it is: CVE-2026-98743 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98743 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98743/ (Markdown: https://insights.sbomify.com/CVE-2026-98743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98743
- OSV: https://osv.dev/vulnerability/CVE-2026-98743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98743/
Summaries are generated and may contain mistakes; the official description above is the record.