CVE-2025-38158: hisi_acc_vfio_pci: fix XQE dma address error
In the Linux kernel, the following vulnerability has been resolved:
hisiaccvfiopci: fix XQE dma address error
The dma addresses of EQE and AEQE are wrong after migration and results in guest kernel-mode encryption services failure. Comparing the definition of hardware registers, we found that there was an error when the data read from the register was combined into an address. Therefore, the address combination sequence needs to be corrected.
Even after fixing the above problem, we still have an issue where the Guest from an old kernel can get migrated to new kernel and may result in wrong data.
In order to ensure that the address is correct after migration, if an old magic number is detected, the dma address needs to be updated.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1 - Compensating control
In hisi_acc_vfio_pci, correct the register-data address-combination sequence and update the EQE and AEQE DMA addresses when an old magic number is detected, so migrated guests receive correct addresses.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-38158?
CVE-2025-38158 has a severity rating that reflects its potential impact on the Linux kernel and the security of systems utilizing it.
How do I fix CVE-2025-38158?
To fix CVE-2025-38158, ensure that you update your Linux kernel to the latest stable version provided by your distribution.
What are the implications of CVE-2025-38158?
CVE-2025-38158 can lead to failures in guest kernel-mode encryption services, impacting the security of affected systems.
Which versions of Linux are affected by CVE-2025-38158?
CVE-2025-38158 affects specific versions of the Linux kernel where the vulnerability was present prior to being patched.
Is CVE-2025-38158 being actively exploited?
As of now, there is no public information confirming active exploitation of CVE-2025-38158.