# CVE-2026-97412: pds_core: quiesce DMA before freeing resources

> A use-after-free vulnerability in the pds_core driver allows attackers to execute code or escalate privileges by exploiting DMA operations on freed memory.

- **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:** 21 Oct 2026
- **Also known as:** AZL-103973, BELL-CVE-2026-97412, DEBIAN-CVE-2026-97412, GHSA-vh7w-pf8m-646h, UBUNTU-CVE-2026-97412

## What is CVE-2026-97412?

CVE-2026-97412 is an use after free 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:

pds_core: quiesce DMA before freeing resources

pdsc_teardown() frees DMA buffers but does not disable bus mastering,
leaving the device able to perform DMA after the buffers are freed.
This can lead to use-after-free if the device writes to freed memory.

Add pci_clear_master() to pdsc_teardown() to disable bus mastering
before freeing resources, ensuring all DMA is quiesced.

Add pci_set_master() to pdsc_setup() to re-enable bus mastering,
which is needed for the firmware recovery path since pdsc_teardown()
now disables it.

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


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

Apply the vendor's patch.

## Is CVE-2026-97412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97412 is an use after free 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-97412 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-97412/ (Markdown: https://insights.sbomify.com/CVE-2026-97412/index.md)
```

## Sources

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

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