CVE-2026-89960— vfio-ap mdev错误时pqap_hook指针未更新
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已修复以下漏洞： s390/vfio-ap：修复 vfio_ap_mdev_set_kvm() 中错误路径下 pqap_hook 指针未更新的问题 在 函数中， 被提前设置为 ，此时尚未获取更新锁（update locks），也未检查 mdev 列表是否存在冲突的分配。如果另一个 mdev 已经绑定到同一个 KVM 实例，该函数将返回 错误，但不会恢复（restore）原来的 hook 指针。这导致 指向了失败的 ，而不是合法拥有该 KVM 实例的那个 mdev。 由于在此错误路径中， 从未
影响版本矩阵 12
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 86956e70761b3292156d668e87126844334dd71b< eb6cc898501a004c0fa8aab951351d9c959b91cc |
affected |
86956e70761b3292156d668e87126844334dd71b< 6a180adafc2a8a5fbe815985c71b2201e93ab5e1 |
affected | ||
86956e70761b3292156d668e87126844334dd71b< fc069d00a0dbef40042fd681554d48dcd5a1d524 |
affected | ||
86956e70761b3292156d668e87126844334dd71b< 13bfc94eef389bd664ffc67b00184919902c938a |
affected | ||
86956e70761b3292156d668e87126844334dd71b< 4400270ec0348d05dc0439d8f0130853ce7f9e20 |
affected | ||
5.15 |
affected | ||
< 5.15 |
unaffected | ||
6.6.157≤ 6.6.* |
unaffected | ||
| … +4 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-89960 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
s390/vfio-ap: fix stale pqap_hook pointer on error in vfio_ap_mdev_set_kvm()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio-ap: fix stale pqap_hook pointer on error in vfio_ap_mdev_set_kvm()
In vfio_ap_mdev_set_kvm(), kvm->arch.crypto.pqap_hook is set to
&matrix_mdev->pqap_hook before the update locks are acquired and the
mdev list is checked for a conflicting assignment. If another mdev is
already attached to the same KVM instance, the function returns -EPERM
without restoring the hook pointer, leaving kvm->arch.crypto.pqap_hook
pointing at the failing matrix_mdev instead of the mdev that legitimately
owns the KVM.
Since matrix_mdev->kvm is never set on this error path,
vfio_ap_mdev_unset_kvm() will not clean up the hook when matrix_mdev
is later closed. If matrix_mdev is subsequently freed, any PQAP
instruction executed by the guest will dereference the stale pointer
through pqap_hook_rwsem, resulting in a use-after-free.
Since kvm->arch.crypto.pqap_hook is only set in the vfio_ap_mdev_set_kvm()
function and is cleared in the vfio_ap_mdev_unset_kvm() function, a check
for 'kvm->arch.crypto.pqap_hook != NULL' is all that is needed to determine
whether it belongs to another mdev. This will alleviate the need to iterate
the matrix_dev->mdev_list list to see if the kvm object is assigned to
another mdev.This was introduced in v3 to alleviate the need to take the
mdevs_lock while iterating the list; however, this did not prevent a
potential race condition.
The pqap_hook_rwsem(write) is now performed inside
get_update_locks_for_kvm(), which is updated to acquire
pqap_hook_rwsem(write) between kvm->lock and mdevs_lock. This ordering
is consistent with the PQAP intercept path, which acquires pqap_hook_rwsem
in read mode while srcu is held under vcpu->mutex, establishing the
dependency: kvm->lock -> vcpu->mutex -> srcu -> pqap_hook_rwsem(read).
The pqap_hook_rwsem is now released inside the
release_update_locks_for_kvm(), which is updated to release
pqap_hook_rwsem(write) between mdevs_lock and kvm->lock.
Additionally, kvm_put_kvm() in vfio_ap_mdev_unset_kvm() is moved
after release_update_locks_for_kvm(). Previously it was called while
kvm->lock was held; if it were ever the last reference, kvm_destroy_vm()
would run under kvm->lock, which would deadlock.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-89960 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-89960 的情报信息
请登录查看更多情报信息。
CVE-2026-89960 其他参考 (5)
同批安全公告 · Linux · 2026-09-16 · 共 276 条
| CVE-2026-90048 | 9.8 CRITICAL | Linux内核NTFS3文件系统越界写漏洞 |
| CVE-2026-90012 | 9.8 CRITICAL | SPI DMA映射所有权修复 |
| CVE-2026-89970 | 9.8 CRITICAL | NVM Target SQ拆除时超时工作未同步 |
| CVE-2026-89857 | 9.8 CRITICAL | QLogic qla2xxx NVMe LS拒绝竞态条件漏洞 |
| CVE-2026-89969 | 9.8 CRITICAL | Linux内核 nvmet-tcp 越界写入漏洞 |
| CVE-2026-89847 | 9.8 CRITICAL | qla2xxx SCSI驱动异步IOCB超时双重完成漏洞 |
| CVE-2026-89972 | 9.8 CRITICAL | NVMe驱动错误路径SRCU宽限期缺失漏洞 |
| CVE-2026-89990 | 9.8 CRITICAL | Ceph ceph_mds_check_access 互斥锁缺失漏洞 |
| CVE-2026-90036 | 9.8 CRITICAL | Linux NFSd 阻塞锁收割时释放后使用漏洞 |
| CVE-2026-90038 | 9.8 CRITICAL | Linux内核NFSD导出撤销后使用漏洞 |
| CVE-2026-90037 | 9.8 CRITICAL | Linux内核NFSD close_lru释放后使用漏洞 |
| CVE-2026-89788 | 9.8 CRITICAL | Linux kernel ksmbd 释放后使用漏洞 |
| CVE-2026-89783 | 9.8 CRITICAL | Linux内核 xfrm6 越界写入漏洞 |
| CVE-2026-90042 | 9.8 CRITICAL | Ceph 虚拟内存分配缓冲区文件名解密漏洞 |
| CVE-2026-89778 | 9.8 CRITICAL | isofs 空 zisofs 块页面数组越界访问漏洞 |
| CVE-2026-89914 | 9.3 CRITICAL | KVM arm64 虚拟地址符号扩展错误 |
| CVE-2026-90049 | 9.3 CRITICAL | 内核网络子系统中skb_zerocopy处理中的缺陷 |
| CVE-2026-89775 | 9.3 CRITICAL | KVM arm64 VNCR TLB大小计算漏洞 |
| CVE-2026-89916 | 9.3 CRITICAL | KVM arm64 VNCR失效重试漏洞 |
| CVE-2026-89930 | 9.3 CRITICAL | KVM嵌套虚拟化本地TLB刷新漏洞 |
显示前 20 条，共 276 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-89960
暂无评论