CVE-2026-93287— i2c smbus: 拒绝常见路径中过大的块传输
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已解决以下漏洞： i2c: smbus：在通用路径中拒绝过大的块传输 SMBus 块传输长度数据 在 中进行了验证，但该检查执行得太晚，无法阻止跟踪点（tracepoints），并且当适配器提供原生的 实现时，该检查会被完全跳过。这导致用户可控的过大块长度未经检查地进入跟踪点的 调用和驱动程序回调。 在 中添加早期验证，在触发任何跟踪点或运行任何驱动程序回调之前，拒绝调用者提供的长度为零或超过 的块传输。由于 是在 SMBus 块读取时由设备填充的，因此该检查仅限于长度实际由调用者提供的操作
可能的 ATT&CK 技术 1 AI
T1068 · Exploitation for Privilege Escalation影响版本矩阵 16
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 4710317891e4824ce1510a6b5066abbd3e917750< 856dffcc097b3d8ed45a643ebda07cb92968cb33 |
affected |
4710317891e4824ce1510a6b5066abbd3e917750< 356875e33f2c6d2061a02c9dec1a1e639d265a55 |
affected | ||
4710317891e4824ce1510a6b5066abbd3e917750< 72ca5e0b8b7a62615758f8871c34d61616c2dc8b |
affected | ||
4710317891e4824ce1510a6b5066abbd3e917750< df077253f6405d67ad087538e495ef32a05717b7 |
affected | ||
4710317891e4824ce1510a6b5066abbd3e917750< f09edffba97d37b1fdff5f818a9a45f8a98ac171 |
affected | ||
4710317891e4824ce1510a6b5066abbd3e917750< c4b478bc50b7ca9865e237909941253a0f7111a2 |
affected | ||
4710317891e4824ce1510a6b5066abbd3e917750< 3051cd060fa496df42954291fa2306ed2eab4ecc |
affected | ||
2.6.33 |
affected | ||
| … +8 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-93287 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
i2c: smbus: reject oversized block transfers in the common path
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
i2c: smbus: reject oversized block transfers in the common path
The SMBus block transfer length data->block[0] is validated in
i2c_smbus_xfer_emulated() but that check runs too late for tracepoints
and is skipped entirely when the adapter provides a native smbus_xfer
implementation. This allows user-controlled oversized block lengths to
reach tracepoint memcpy calls and driver callbacks unchecked.
Add an early validation in __i2c_smbus_xfer() that rejects block
transfers whose caller-supplied length is zero or exceeds
I2C_SMBUS_BLOCK_MAX before any tracepoint fires or driver callback
runs. data->block[0] is filled in by the device on SMBus block reads,
so the check is scoped to operations where the length is actually
supplied by the caller. This is consistent with the existing -EINVAL
convention in the emulated path and protects all downstream consumers
at once: the smbus_write tracepoint, all native smbus_xfer driver
implementations, and the emulated path.
Two distinct bugs are fixed by this change:
Bug 1: smbus_write tracepoint OOB (include/trace/events/smbus.h)
trace_smbus_write() fires before any validation and copies
data->block[0]+1 bytes into a 34-byte event buffer. With
block[0]=0xfe the tracepoint copies 255 bytes, overflowing by 221.
BUG: KASAN: stack-out-of-bounds in trace_event_raw_event_smbus_write+0x27c/0x530
Read of size 255 at addr ffff88800d98fcf8 by task poc_smbus/91
Call Trace:
<TASK>
__asan_memcpy+0x23/0x80
trace_event_raw_event_smbus_write+0x27c/0x530
__i2c_smbus_xfer+0x43a/0xa40
i2c_smbus_xfer+0x19e/0x340
i2cdev_ioctl_smbus+0x38f/0x7f0
i2cdev_ioctl+0x35e/0x680
__x64_sys_ioctl+0x147/0x1e0
do_syscall_64+0xcf/0x15a0
entry_SYSCALL_64_after_hwframe+0x76/0x7e
</TASK>
Bug 2: i2c-stub I2C_SMBUS_I2C_BLOCK_DATA OOB (drivers/i2c/i2c-stub.c)
stub_xfer() implements .smbus_xfer directly and only clamps
block[0] against 256-command, not I2C_SMBUS_BLOCK_MAX. With
block[0]=0xff and command=0 the loop accesses block[1+i] for
i up to 254, far past the 34-byte union.
UBSAN: array-index-out-of-bounds in drivers/i2c/i2c-stub.c:223:44
index 34 is out of range for type '__u8 [34]'
Call Trace:
<TASK>
__ubsan_handle_out_of_bounds+0xd7/0x120
stub_xfer+0x1971/0x198f [i2c_stub]
__i2c_smbus_xfer+0x306/0xa40
i2c_smbus_xfer+0x19e/0x340
i2cdev_ioctl_smbus+0x38f/0x7f0
i2cdev_ioctl+0x35e/0x680
__x64_sys_ioctl+0x147/0x1e0
do_syscall_64+0xcf/0x15a0
entry_SYSCALL_64_after_hwframe+0x76/0x7e
</TASK>
Both traces reproduced on v7.0-rc6+i2c/for-current with KASAN+UBSAN.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
受影响产品
二、漏洞 CVE-2026-93287 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-93287 的情报信息
请登录查看更多情报信息。
CVE-2026-93287 补丁与修复 (7)
同批安全公告 · 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-93793 | 8.8 HIGH | iwlwifi 驱动 TX_CMD 响应布局验证漏洞 |
| CVE-2026-93799 | 8.8 HIGH | iwlwifi mvm BA窗口状态通知中sta_id验证漏洞 |
| CVE-2026-93790 | 8.8 HIGH | iwlwifi 驱动 BA 通知中 tid_data 越界访问漏洞 |
| CVE-2026-93806 | 8.8 HIGH | wifi: cfg80211 关联响应长度验证漏洞 |
| CVE-2026-97442 | 8.8 HIGH | ath11k无线驱动rx_h_undecap_nwifi无效数据访问漏洞 |
| CVE-2026-97509 | 8.8 HIGH | Thunderbolt 服务期间保持 XDomain 引用漏洞 |
| CVE-2026-97409 | 8.8 HIGH | Linux NVMe-oF目标未初始化前取消请求漏洞 |
| CVE-2026-93280 | 8.8 HIGH | Greybus 音频拓扑边界检查漏洞 |
| CVE-2026-93284 | 8.8 HIGH | drm/pagemap 迁移错误前未解除 dma 映射 |
| CVE-2026-97451 | 8.4 HIGH | ACPICA mid_op 整数溢出漏洞 |
| CVE-2026-97455 | 8.4 HIGH | ACPICA acpi_ds_terminate_control_method 使用后释放漏洞 |
| CVE-2026-97452 | 8.4 HIGH | ACPICA：防止添加无效引用 |
| CVE-2026-97450 | 8.4 HIGH | ACPICA 双重验证处理器对象类型漏洞 |
| CVE-2026-93827 | 8.4 HIGH | virtio-fs 队列设置失败时双重释放漏洞 |
| CVE-2026-97433 | 8.2 HIGH | NVMe 验证 FDP 配置描述符大小 |
| CVE-2026-93786 | 8.1 HIGH | ksmbd 保持 VFS 继承 POSIX ACL 掩码漏洞 |
| CVE-2026-93282 | 8.1 HIGH | ksmbd 修复最大允许访问检查漏洞 |
显示前 20 条，共 234 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-93287
暂无评论