# CVE-2026-89943: ASoC: loongson: Fix error handling in ACPI property parsing

> An attacker with local access could trigger a kernel crash by exploiting an uninitialized pointer in the Loongson ASoC driver's ACPI property parsing.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-89943, DEBIAN-CVE-2026-89943, GHSA-r596-mvwg-48gr, UBUNTU-CVE-2026-89943

## What is CVE-2026-89943?

CVE-2026-89943 is a high-severity vulnerability in Linux, published on 16 Sep 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: loongson: Fix error handling in ACPI property parsing

In loongson_card_parse_acpi(), the return value of
device_property_read_string() for the `codec-dai-name` property was
ignored. If the property is missing or invalid, an uninitialized pointer
would be used later, potentially leading to undefined behavior.

Fix this by checking the return value and propagating the error
appropriately.

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


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

Apply the vendor's patch.

## Is CVE-2026-89943 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89943 is a high-severity vulnerability in Linux, published on 16 Sep 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-89943 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-89943/ (Markdown: https://insights.sbomify.com/CVE-2026-89943/index.md)
```

## Sources

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

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