目标达成 感谢每一位支持者 — 我们达成了 100% 目标!

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2026-97479— 内核驱动子系统:移除设备时避免供应商解绑警告

一分钟漏洞结论

影响对象
Linux Linux
利用判断
尚无明确在野利用证据,仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本;无法立即升级时,限制受影响服务暴露并加强监测。

在 Linux 内核中,以下漏洞已得到修复: driver core:在移除设备时,若其供应者(supplier)正在解除绑定,则避免发出警告 在驱动程序移除过程中,可能会出现以下警告: 该警告的触发条件是:当某个消费端(consumer)被移除时,其供应端(supplier)的链接状态不是 ,并且链接标志 也未设置。 在此场景下,基于消费端/供应端关系的拓扑结构如下(表示为:消费端 ---> 供应端): 当 PCI 设备被移除时,必须随之移除 OIC(中断控制器)。为了移除 OIC,需要先移除 pinctrl 和

EPSS 0.15% · P4

可能的 ATT&CK 技术 1 AI

T1690 · Prevent Command History Logging

影响版本矩阵 10

厂商产品 版本范围状态
Linux Linux 8c3e315d4296421cd26b3300ee0ac117f0877f20< 73ea4ec0ec46d12558a61842b474e7dd63538edc affected
8c3e315d4296421cd26b3300ee0ac117f0877f20< 36d74f17e03f7e60e1b08fbe16cfad6e69cc3aa9 affected
2e5c082d3727522a3f30a50582784d24754d14a8 affected
70154bb515a325c007bcf64971099e1e17f16f28 affected
5.6.19< 5.7 affected
5.7.3< 5.8 affected
5.8 affected
< 5.8 unaffected
… +2 条更多
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2026-97479 基础信息

漏洞信息

对漏洞内容有疑问?看看神龙的深度分析是否有帮助!
查看神龙十问 ↗

尽管我们使用了先进的大模型技术,但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性,但请您根据实际情况进行核实和判断。

Vulnerability Title
driver core: Avoid warning when removing a device while its supplier is unbinding
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: driver core: Avoid warning when removing a device while its supplier is unbinding During driver removal, the following warning can appear: WARNING: CPU: 1 PID: 139 at drivers/base/core.c:1497 __device_links_no_driver+0xcc/0xfc ... Call trace: __device_links_no_driver+0xcc/0xfc (P) device_links_driver_cleanup+0xa8/0xf0 device_release_driver_internal+0x208/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c device_links_unbind_consumers+0xe0/0x108 device_release_driver_internal+0xec/0x23c driver_detach+0xa0/0x12c bus_remove_driver+0x6c/0xbc driver_unregister+0x30/0x60 pci_unregister_driver+0x20/0x9c lan966x_pci_driver_exit+0x18/0xa90 [lan966x_pci] This warning is triggered when a consumer is removed because the links status of its supplier is not DL_DEV_DRIVER_BOUND and the link flag DL_FLAG_SYNC_STATE_ONLY is not set. The topology in terms of consumers/suppliers used was the following (consumer ---> supplier): i2c -----------> OIC ----> PCI device | ^ | | +---> pinctrl ---+ When the PCI device is removed, the OIC (interrupt controller) has to be removed. In order to remove the OIC, pinctrl and i2c need to be removed and to remove pinctrl, i2c need to be removed. The removal order is: 1) i2c 2) pinctrl 3) OIC 4) PCI device In details, the removal sequence is the following (with 0000:01:00.0 the PCI device): driver_detach: call device_release_driver_internal(0000:01:00.0)... device_links_busy(0000:01:00.0): links->status = DL_DEV_UNBINDING device_links_unbind_consumers(0000:01:00.0): 0000:01:00.0--oic link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(oic)... device_links_busy(oic): links->status = DL_DEV_UNBINDING device_links_unbind_consumers(oic): oic--pinctrl link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(pinctrl)... device_links_busy(pinctrl): links->status = DL_DEV_UNBINDING device_links_unbind_consumers(pinctrl): pinctrl--i2c link->status = DL_STATE_SUPPLIER_UNBIND call device_release_driver_internal(i2c)... device_links_busy(i2c): links->status = DL_DEV_UNBINDING __device_links_no_driver(i2c)... pinctrl--i2c link->status is DL_STATE_SUPPLIER_UNBIND oic--i2c link->status is DL_STATE_ACTIVE oic--i2c link->supplier->links.status is DL_DEV_UNBINDING The warning is triggered by the i2c removal because the OIC (supplier) links status is not DL_DEV_DRIVER_BOUND. Its links status is indeed set to DL_DEV_UNBINDING. It is perfectly legit to have the links status set to DL_DEV_UNBINDING in that case. Indeed we had started to unbind the OIC which triggered the consumer unbinding and didn't finish yet when the i2c is unbound. Avoid the warning when the supplier links status is set to DL_DEV_UNBINDING and thus support this removal sequence without any warnings.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5

受影响产品

厂商 产品 影响版本 CPE 订阅
Linux Linux 8c3e315d4296421cd26b3300ee0ac117f0877f20 ~ 73ea4ec0ec46d12558a61842b474e7dd63538edc -
Linux Linux 5.8 -

二、漏洞 CVE-2026-97479 的公开POC

# POC 描述 源链接 神龙链接
AI 生成 POC 高级

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2026-97479 的情报信息

请登录查看更多情报信息。

CVE-2026-97479 补丁与修复 (1)

同批安全公告 · Linux · 2026-09-24 · 共 234 条

CVE-2026-93207 9.8 CRITICAL SUNRPC svcauth_gss_decode_credbody() 存在安全漏洞
CVE-2026-97413 9.8 CRITICAL Linux RDMA/rtrs-srv整数下溢漏洞
CVE-2026-93228 9.1 CRITICAL svcrdma 拒绝段计数为0的写入/回复块漏洞
CVE-2026-93799 8.8 HIGH iwlwifi mvm BA窗口状态通知中sta_id验证漏洞
CVE-2026-97442 8.8 HIGH ath11k无线驱动rx_h_undecap_nwifi无效数据访问漏洞
CVE-2026-97409 8.8 HIGH Linux NVMe-oF目标未初始化前取消请求漏洞
CVE-2026-93806 8.8 HIGH wifi: cfg80211 关联响应长度验证漏洞
CVE-2026-93793 8.8 HIGH iwlwifi 驱动 TX_CMD 响应布局验证漏洞
CVE-2026-93790 8.8 HIGH iwlwifi 驱动 BA 通知中 tid_data 越界访问漏洞
CVE-2026-93284 8.8 HIGH drm/pagemap 迁移错误前未解除 dma 映射
CVE-2026-93280 8.8 HIGH Greybus 音频拓扑边界检查漏洞
CVE-2026-97509 8.8 HIGH Thunderbolt 服务期间保持 XDomain 引用漏洞
CVE-2026-93827 8.4 HIGH virtio-fs 队列设置失败时双重释放漏洞
CVE-2026-97450 8.4 HIGH ACPICA 双重验证处理器对象类型漏洞
CVE-2026-97451 8.4 HIGH ACPICA mid_op 整数溢出漏洞
CVE-2026-97452 8.4 HIGH ACPICA:防止添加无效引用
CVE-2026-97455 8.4 HIGH ACPICA acpi_ds_terminate_control_method 使用后释放漏洞
CVE-2026-97433 8.2 HIGH NVMe 验证 FDP 配置描述符大小
CVE-2026-93221 8.1 HIGH NFS服务端标志位转换为无符号长整型
CVE-2026-93786 8.1 HIGH ksmbd 保持 VFS 继承 POSIX ACL 掩码漏洞

显示前 20 条,共 234 条。 查看全部 &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2026-97479

暂无评论


发表评论