CVE-2026-90184— 设备配置更新同步化
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，以下漏洞已修复： null_blk：将 configfs 属性更新与设备初始化/销毁过程串行化 由 生成的属性存储方法（store methods）会通过检查 标志来拒绝修改处于活动状态（live）设备的配置。然而，该标志仅在 调用 返回之后才会被设置。此外，这些存储方法本身并未获取任何锁。由于 configfs 仅对写入同一个打开的文件进行串行化（通过 ），因此对任意属性的写入操作都可能与正在执行的 并发执行，从而在设备正被使用期间意外改变其配置。 会多次读取配置，例如： 第一次读取 用于
影响版本矩阵 14
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< 6352e7ead2d8111802a554eeb94886f5a9894bb9 |
affected |
3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< 7de792b4c48fba02a36a8077032f7d5093c925e5 |
affected | ||
3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< aed8af338a09a64d63b068a803c4ecfc5701dd4c |
affected | ||
3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< 32456a85995579e56c60cc53c357cda75a9d4f7c |
affected | ||
3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< d3d35dd045a35991bf6fd13de5f293e6dd7bf3b3 |
affected | ||
3bf2bd20734e3e6ffda53719a9c10fb3ee9c5ffa< 4e1f23f9c33c156be7e313b40695af5a3a834739 |
affected | ||
4.14 |
affected | ||
< 4.14 |
unaffected | ||
| … +6 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-90184 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
null_blk: serialize configfs attribute updates with device setup
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
null_blk: serialize configfs attribute updates with device setup
The attribute store methods generated with NULLB_DEVICE_ATTR() refuse to
change the configuration of a live device by testing
NULLB_DEV_FL_CONFIGURED, but that flag is only set by
nullb_device_power_store() after null_add_dev() has returned, and the
store methods take no lock at all. configfs only serializes writes to
the same open file (buffer->mutex), so a write to any attribute can run
concurrently with null_add_dev() and change the device configuration
while it is being used.
null_add_dev() reads the configuration several times, e.g. dev->zoned is
read once to set up the queue limits and once to initialize the zone
resources:
CPU0: echo 1 > nullb0/power CPU1: echo 1 > nullb0/zoned
nullb_device_power_store()
mutex_lock(&lock)
null_add_dev()
if (dev->zoned) -> false
/* no BLK_FEAT_ZONED */ nullb_device_zoned_store()
test_bit(FL_CONFIGURED) -> 0
dev->zoned = true
blk_mq_alloc_disk()
/* queue is not zoned */
if (nullb->dev->zoned) -> true
null_register_zoned_dev()
blk_revalidate_disk_zones()
blk_revalidate_disk_zones() is then called for a queue that does not
have BLK_FEAT_ZONED set, which triggers its WARN_ON_ONCE() and fails the
device setup with -EIO:
WARNING: CPU: 2 PID: 322 at block/blk-zoned.c:2357 blk_revalidate_disk_zones+0x4c/0x560
Clearing dev->zoned in the same window is worse: the queue is created
with BLK_FEAT_ZONED but the zone resources are never initialized, so
add_disk() succeeds for a zoned disk that has no zones. And a store that
lands after the last dev->zoned test leaves dev->zoned set while
dev->zones is still NULL, which null_process_zoned_cmd() dereferences on
the first write.
Fix this by taking the global lock, which nullb_device_power_store()
already holds across null_add_dev() and null_del_dev(), around both the
NULLB_DEV_FL_CONFIGURED test and the update of the device configuration.
The submit_queues and poll_queues apply callbacks are now called with
that lock held, so remove the locking they did themselves.
Since the store methods can run as soon as configfs_register_subsystem()
returns, that is, before null_init() gets to mutex_init(&lock), also
initialize the lock statically with DEFINE_MUTEX().
来源: 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-90184 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-90184 的情报信息
请登录查看更多情报信息。
CVE-2026-90184 补丁与修复 (6)
同批安全公告 · Linux · 2026-09-17 · 共 600 条
| CVE-2026-90235 | 9.8 CRITICAL | 内核sunrpc xprtsock并发读取修复 |
| CVE-2026-90104 | 9.8 CRITICAL | NFSv4.1 解码前未清空调用列表 |
| CVE-2026-90173 | 9.8 CRITICAL | SMB SmbDirect 释放完成队列漏洞 |
| CVE-2026-92489 | 9.8 CRITICAL | Linux内核 xfrm 双重释放漏洞 |
| CVE-2026-90151 | 9.8 CRITICAL | NFSv4客户端分配失败回调处理漏洞 |
| CVE-2026-90110 | 9.4 CRITICAL | inetpeer 随机化RB树节点比较 |
| CVE-2026-90230 | 9.1 CRITICAL | Linux内核Nvme-target堆越界读取漏洞 |
| CVE-2026-90414 | 9.1 CRITICAL | IB/isert拒绝声明超出实际接收数据的PDU |
| CVE-2026-90413 | 9.1 CRITICAL | IB/isert 登录PDU数据长度校验漏洞 |
| CVE-2026-90380 | 8.8 HIGH | MT76驱动 mt792x 使用释放后内存漏洞 |
| CVE-2026-93042 | 8.8 HIGH | Linux内核dmaengine模块资源耗尽漏洞 |
| CVE-2026-90425 | 8.8 HIGH | Linux内核 5.x 内核漏洞 |
| CVE-2026-90240 | 8.8 HIGH | Linux内核 IOMMU 别名拆除时刷新缓存错误 |
| CVE-2026-90381 | 8.8 HIGH | Linux内核mt76驱动无线信道切换漏洞 |
| CVE-2026-90329 | 8.8 HIGH | Linux 内核 HID 驱动探测清理同步漏洞 |
| CVE-2026-90357 | 8.8 HIGH | mt76驱动MT7915无线局域网远程拒绝服务漏洞 |
| CVE-2026-90379 | 8.8 HIGH | Linux 内核 mt76 驱动系统崩溃漏洞 |
| CVE-2026-90162 | 8.8 HIGH | Linux ksmbd 锁授予UAF/双重释放竞态漏洞 |
| CVE-2026-93189 | 8.8 HIGH | Linux HID核心使用已释放内存漏洞 |
| CVE-2026-90255 | 8.8 HIGH | Linux内核 Bluetooth 漏洞 |
显示前 20 条，共 600 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-90184
暂无评论