# CVE-2026-97414: ASoC: mediatek: mt8365-afe-pcm: fix possible NULL-pointer dereferences in mt8365_afe_suspend()

> A missing NULL check in the MediaTek audio driver can cause a kernel crash during suspend, leading to denial of service.

- **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:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** BELL-CVE-2026-97414, DEBIAN-CVE-2026-97414, GHSA-cfm8-jq8w-4xxp, UBUNTU-CVE-2026-97414

## What is CVE-2026-97414?

CVE-2026-97414 is a vulnerability in Linux, published on 24 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: mediatek: mt8365-afe-pcm: fix possible NULL-pointer dereferences in mt8365_afe_suspend()

mt8365_afe_suspend() allocates the register backup buffer with
devm_kcalloc(), but does not check for allocation failure before using the
returned pointer. This may lead to a NULL pointer dereference when
accessing afe->reg_back_up[i].

Add the missing NULL check and return -ENOMEM on allocation failure after
disabling the main clock.

Also propagate the return value of mt8365_afe_suspend() in
mt8365_afe_dev_runtime_suspend() so that the suspended state is not updated
when suspend fails.

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


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

Apply the vendor's patch.

## Is CVE-2026-97414 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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