CVE-2025-38283: hisi_acc_vfio_pci: bugfix live migration function without VF device driver
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.
Security readout for executives and security teams
Plain-English summary
A Linux live-migration flaw affects certain virtual machines using HiSilicon accelerator virtual functions. If a guest lacks the corresponding VF driver, migration can leave a null data address that the destination accesses during recovery. This can cause access errors and potentially disrupt migration workloads.
Executive priority
Prioritize affected virtualization clusters because the CVSS score is high and migration failures can threaten workload continuity. Urgency is configuration-dependent rather than universal: first identify HiSilicon VF passthrough and live-migration use, then patch or temporarily restrict the risky migration scenario. No active exploitation evidence is provided.
Technical view
The hisi_acc_vfio_pci migration path may produce a NULL migrated-data address when the guest VF driver is absent. Destination-side recovery then accesses that address. The kernel resolution skips device-data migration when no VF driver is present and skips queue recovery when received queue-address data is empty. CVSS 3.1 is 8.8, requiring local, low-privileged access.
Likely exposure
Exposure appears limited to Linux virtualization hosts using hisi_acc_vfio_pci-backed HiSilicon accelerator VFs with live migration, specifically when the guest VF driver is not loaded. Systems without this device configuration or migration workflow are unlikely to encounter the described condition. The supplied version data is inconsistent, so confirm applicability against vendor guidance and fixes.
Exploitation context
The supplied record does not identify active exploitation, and the CVE is not marked as included in CISA KEV. The described trigger requires local access, low privileges, a relevant VF configuration, and a live-migration operation. Public sources supplied here establish the defect and kernel fixes, but not weaponized exploitation.
Researcher notes
The root condition is a missing guest VF driver producing absent migration data, followed by unsafe destination recovery. The fix adds two defensive decisions: omit device-data migration without the driver and omit queue recovery for empty queue-address data. The bundle provides four stable commits but does not clearly map every affected or fixed release.
Mitigation direction
Identify hosts using hisi_acc_vfio_pci devices and VF-backed virtual-machine live migration.
Apply a vendor-supported kernel containing the applicable stable fix referenced by the CVE record.
Until patched, avoid live-migrating affected VMs whose guest VF driver is not loaded.
Consult Linux distribution guidance before selecting a fixed package because supplied version ranges are ambiguous.
Validation and detection
Record kernel and distribution package versions on virtualization hosts using relevant HiSilicon accelerator VFs.
Confirm whether affected guests load the required VF driver before migration.
Verify the installed kernel includes the applicable stable fix or distribution backport.
Review migration and destination-host logs for access errors involving device or queue recovery.
Test live migration safely in staging after remediation, including guests without the VF driver.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38283 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.