CVE-2026-89958— s390/vfio-ap 空指针解引用漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已得到修复： s390/vfio-ap：修复在未检查 是否为 NULL 的情况下对其进行解引用的问题 结构体中包含两个指向回调函数的函数指针字段： ：在 AP 总线扫描函数开始时被调用，用于通知设备驱动程序宿主机的 AP 配置已发生变更，相关的 AP 设备将相应地被添加或删除。这为实施者提供了一次机会，以便在相关设备被添加或删除之前评估配置变更并作出响应。 ：在 AP 总线扫描函数结束时被调用，用于通知设备驱动程序宿主机的 AP 配置已发生变更，且 AP 设备已相应地被添加或删除。这
影响版本矩阵 12
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | eeb386aeb5b7c8d2dae6a3ba49255d8a97803182< 5e932abfcce6189d067fffb0eb8214443bc04374 |
affected |
eeb386aeb5b7c8d2dae6a3ba49255d8a97803182< 334b435b951353f934d5110c4630e0cb58d2f9a7 |
affected | ||
eeb386aeb5b7c8d2dae6a3ba49255d8a97803182< 178ea7a1c2c3c0c01d14b8f60aa35f1e0cdc6b78 |
affected | ||
eeb386aeb5b7c8d2dae6a3ba49255d8a97803182< 4f7e869d0db24ae07b4c888fd3bc21554eef775d |
affected | ||
eeb386aeb5b7c8d2dae6a3ba49255d8a97803182< d50346801b4f144e42b49cd4f1496010498ab114 |
affected | ||
6.0 |
affected | ||
< 6.0 |
unaffected | ||
6.6.157≤ 6.6.* |
unaffected | ||
| … +4 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-89958 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
s390/vfio-ap: Fix dereference matrix_mdev->kvm without checking for NULL
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
s390/vfio-ap: Fix dereference matrix_mdev->kvm without checking for NULL
The ap_driver structure has two fields which are function pointers to
callbacks:
* .on_config_changed: called at the start of the AP bus scan function to
notify the device driver that the host AP
configuration has changed and the associated AP
devices will be added or removed accordingly. This
gives the implementor a chance to evaluate the
configuration changes and respond to them before
the associated devices are added or removed.
* .on_scan_complete: Called at the end of the AP bus scan function to
notify the device driver that the host AP
configuration has changed and the AP devices have
been added or removed accordingly. This gives the
implementor the opportunity to respond to the
changes after the associated devices are added or
removed.
These two callbacks are implemented in the vfio_ap device driver via the
vfio_ap_on_cfg_changed and vfio_ap_on_scan_complete functions respectively.
Within the call stack of these two callback functions the
matrix_mdev->kvm->lock mutex is taken without checking whether
matrix_mdev->kvm is NULL or not. If matrix_mdev->kvm has never been set,
trying to take the lock will trigger a NULL pointer dereference. This patch
adds checks for matrix_mdev->kvm == NULL before taking the
matrix_mdev->kvm->lock mutex.
Note that the matrix_mdev->kvm->lock mutex taken in the
vfio_ap_mdev_hot_plug_config function is moved to the calling function
along with the matrix_dev->mdevs_lock which is needed there to access
the fields of the matrix_mdev. It makes little sense to make the change
the check for matrix_mdev->kvm there before taking the kvm->lock
mutex only to have to move it out via another patch, so it is done in
this patch.
It is important to make note of the following:
1. The matrix_dev->guests_lock is acquired at the start of both callback
functions. This ensures that matrix_mdev will not be removed via the
vfio_ap_mdev_remove function because it too takes matrix_dev_guests_lock
before removing the object; so, matrix_mdev will be available for the
duration of the callback functions.
2. The matrix_dev->mdevs_lock mutex must be taken in order to access
fields within the matrix_mdev structure
3. matrix_mdev->kvm->lock mutex must be taken before the
matrix_dev->mdevs_lock to prevent a lockdep splat.
4: The kvm->lock must be held while plugging the guest's AP configuration
into its SIE state description via the vfio_ap_mdev_update_guest_apcb
function.
5. The vfio_ap_mdev_update_guest_apcb checks matrix_mdev->kvm to verify it
is not NULL before doing the hot plug of the guest's AP configuration.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-89958 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-89958 的情报信息
请登录查看更多情报信息。
CVE-2026-89958 其他参考 (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-89915 | 9.3 CRITICAL | KVM arm64 移除虚拟机级 VNCR 映射计数器 |
| 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-89958
暂无评论