CVE-2025-38158: Linux kernel · hisi_acc_vfio_pci: fix XQE dma address error
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1046.49~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1046.49~22.04.1, 6.8.0-1051.57~22.04.1, 6.8.0-1047.50~22.04.2 +30
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7769-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7770-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7771-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7789-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7789-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: hisi_acc_vfio_pci: 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.
References
- ubuntu.com/security/CVE-2025-38158 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-38158 (opens in a new tab)
- git.kernel.org/linus/8bb7170c5a055ea17c6857c256ee73c10ff872eb (opens in a new tab)
- git.kernel.org/stable/c/7710c883eb8cb5cf510ca47ec0e26c6cb7e94a4f (opens in a new tab)
- git.kernel.org/stable/c/809a9c10274e1bcf6d05f1c0341459a425a4f05f (opens in a new tab)
- git.kernel.org/stable/c/884a76e813178778d271fea59783763d32bb7e72 (opens in a new tab)
- git.kernel.org/stable/c/8bb7170c5a055ea17c6857c256ee73c10ff872eb (opens in a new tab)
- git.kernel.org/stable/c/f0423873e7aeb69cb68f4e8fa3827832e7b037ba (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7770-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7771-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7769-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7789-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7789-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)