# CVE-2025-38625: vfio/pds: Fix missing detach_ioas op

> Missing detach_ioas operation in the pds_vfio_pci driver causes probe failure and kernel warnings when IOMMUFD is enabled, leading to denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-66632, BELL-CVE-2025-38625, DEBIAN-CVE-2025-38625, GHSA-xj8c-4hpj-pm7v, ROOT-OS-DEBIAN-13-CVE-2025-38625, ROOT-OS-UBUNTU-2404-CVE-2025-38625, UBUNTU-CVE-2025-38625

## What is CVE-2025-38625?

CVE-2025-38625 is a medium-severity denial of service vulnerability in Linux kernel, published on 22 Aug 2025. 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:

vfio/pds: Fix missing detach_ioas op

When CONFIG_IOMMUFD is enabled and a device is bound to the pds_vfio_pci
driver, the following WARN_ON() trace is seen and probe fails:

WARNING: CPU: 0 PID: 5040 at drivers/vfio/vfio_main.c:317 __vfio_register_dev+0x130/0x140 [vfio]
<...>
pds_vfio_pci 0000:08:00.1: probe with driver pds_vfio_pci failed with error -22

This is because the driver's vfio_device_ops.detach_ioas isn't set.

Fix this by using the generic vfio_iommufd_physical_detach_ioas
function.

## Which versions are affected by CVE-2025-38625?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-38625?

Apply the vendor's patch.

## Is CVE-2025-38625 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-38625 and fix it if it is affected.

What it is: CVE-2025-38625 is a medium-severity denial of service vulnerability in Linux kernel, published on 22 Aug 2025. 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-2025-38625 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2025-38625/ (Markdown: https://insights.sbomify.com/CVE-2025-38625/index.md)
```

## Sources

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

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