CVE-2026-93203— batman-adv 并发添加导致 CRC 损坏
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
在 Linux 内核中，已解决以下漏洞： batman-adv: bla: 避免并行执行时因添加声明（claim）导致的 CRC 损坏 函数用于添加声明（claim）并修改来自远程骨干节点（backbone）的 CLAIM 帧以及本地报文所对应的骨干链路。在处理声明时，它需要执行以下操作之一： 将新声明的 CRC 添加到骨干链路的 CRC 中 从旧骨干链路中移除已存在声明的 CRC，并将其添加到新骨干链路中 但是，当“新声明”代码路径与“切换骨干链路”代码路径并行执行时，由于声明的 在“新声明”路径中被修改了两次，
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-93203 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
batman-adv: bla: avoid CRC corruption due to parallel claim add
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
batman-adv: bla: avoid CRC corruption due to parallel claim add
batadv_bla_add_claim() is used to add claims and modify the backbone of
claims for CLAIM frames from remote backbones and local packets. When it
handles a claim, it needs to either
* add the new claim's CRC to the backbone CRC
* remove the already existing claim's CRC from the old backbone and add it
to the new backbone
But when the "new" claim code was running in parallel to the "change
backbone" code, it can happen that the CRC was invalid because the
backbone_gw of the claim was changed twice in the "new" claim code path:
* CPU0 creates the claim for gateway A and publishes it in the claim
hash. The crc16 of the address has not yet been added to A's crc at
this point.
* CPU1 processes a claim frame of gateway B for the same client, finds
the just published claim, and performs the ownership change: it
switches the pointer to B, removes the crc16 from A's crc - which
never contained it - and adds it to B's crc.
* CPU0 continues behind the creation branch, unconditionally switches
the pointer back to A without compensating B's crc (its remove_crc
is false for the creation path), and finally adds the crc16 to A's
crc
The CRC is then wrong for both:
* claim belongs to A: but CRC is not part of backbone A's CRC
* claim doesn't belong to B: CRC is still part of backbone B's CRC
This wrong CRC is never recomputated from the stored claims. For local
backbone claims, this can also not recovered using syncs.
To avoid this, split the functionality in clear separate parts:
* new claim which always adds claim CRC to the backbone CRC (but never
changes the already set backbone_gw of the claim back)
* update of existing claim which automatically changes the backbone_gw
entry and only updates both backbone CRCs when there was an actual change
来源: 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-93203 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-93203 的情报信息
请登录查看更多情报信息。
CVE-2026-93203 补丁与修复 (2)
CVE-2026-93203 其他参考 (6)
同批安全公告 · Linux · 2026-09-17 · 共 602 条
| CVE-2026-90255 | Linux内核 Bluetooth 漏洞 | |
| CVE-2026-90238 | Linux内核 AMD ISP4 驱动死锁漏洞 | |
| CVE-2026-90240 | Linux内核 IOMMU 别名拆除时刷新缓存错误 | |
| CVE-2026-90239 | Linux内核 AMD ISP4 内存管理缺陷 | |
| CVE-2026-90241 | Intel VT-d 可扩展模式探测失败导致上下文拆除缺陷 | |
| CVE-2026-90243 | Linux内核 VT-d IOMMU 安全漏洞 | |
| CVE-2026-90242 | Linux内核IOMMU VTD引用计数泄漏 | |
| CVE-2026-90244 | Linux内核 iommu/dma 竞争条件漏洞 | |
| CVE-2026-90245 | Linux fbdev kyro 驱动坐标校验缺陷 | |
| CVE-2026-90246 | AppArmor 标签验证整数溢出 | |
| CVE-2026-90247 | 内核bpf路径mmap_lock内存泄漏 | |
| CVE-2026-90248 | Linux内核net/sched：修复竞态条件导致的协议拆解错误 | |
| CVE-2026-90249 | Linux内核iio驱动运行时电源管理修复 | |
| CVE-2026-90250 | Linux内核 bpf cgroup 空指针解引用漏洞 | |
| CVE-2026-90251 | Windows 17763 Bluetooth RCE漏洞 | |
| CVE-2026-90253 | Linux 蓝牙MESH 发送取消命令内存泄漏漏洞 | |
| CVE-2026-90252 | Linux Bluetooth MGMT 取消时未释放HCI命令 | |
| CVE-2026-90254 | 蓝牙 hci_sync 广告实例释放漏洞 | |
| CVE-2026-90256 | Linux Bluetooth L2CAP 远程代码执行漏洞 | |
| CVE-2026-90268 | Linux内核 SCSI子系统探测功能处理错误 |
显示前 20 条，共 602 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-93203
暂无评论