CVE-2026-89741— Linux内核 V4L2驱动 错误处理修复
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
In the Linux kernel, the following vulnerability has been resolved: Revert "media: v4l2-dev: fix error handling in __video_register_device()" This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a. The intentions of that patch were good, but it doesn't w
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-89741 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
Revert "media: v4l2-dev: fix error handling in __video_register_device()"
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
Revert "media: v4l2-dev: fix error handling in __video_register_device()"
This reverts commit 2a934fdb01db6458288fc9386d3d8ceba6dd551a.
The intentions of that patch were good, but it doesn't work.
The idea is that if device_register fails, you have to do a put_device
to let the ref counter release resources.
However, the V4L2 API says that if video_register_device() fails, then
you have to call video_device_release(), which kfree()s the video_device
struct.
But the put_device() will already have freed the struct, so you end
up in a double-free scenario.
There is not really a good way of fixing this without breaking
video_register_device() into two parts, one that initializes everything,
and one that does the actual device_register, and then converting all
V4L2 drivers to this new model.
That is a massive job, and it is very unlikely that device_register
will fail.
So rather than ending up in a double-free scenario, just revert this
patch, and in that case we'll have a small memory leak. Which is a lot
more robust.
来源: 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-89741 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-89741 的情报信息
请登录查看更多情报信息。
CVE-2026-89741 其他参考 (4)
同批安全公告 · Linux · 2026-09-11 · 共 431 条
| CVE-2026-89491 | OCFS2集群心跳锁持有期间睡眠漏洞 | |
| CVE-2026-89477 | Linux内核 SCTP 重配置空指针引用漏洞 | |
| CVE-2026-89478 | sctp：移除的传输中丢弃数据块 | |
| CVE-2026-89479 | 内核SCTP模块关联删除后仍处理报文 | |
| CVE-2026-89480 | NVMe-TCP 读取字节数异常拒绝漏洞 | |
| CVE-2026-89482 | NVMe-TCP 数据长度误判漏洞 | |
| CVE-2026-89481 | NVMe/TCP 主机内存泄露漏洞 | |
| CVE-2026-89483 | Linux内核 NVMe驱动 逻辑错误 | |
| CVE-2026-89484 | Linux内核lockd 空指针解引用漏洞 | |
| CVE-2026-89485 | Linux lockd 锁释放时文件指针固定漏洞 | |
| CVE-2026-89486 | IPMI 驱动 _ipmi_destroy_user 释放后使用漏洞 | |
| CVE-2026-89487 | Open vSwitch 数据包丢弃逻辑缺陷 | |
| CVE-2026-89488 | Open vSwitch CT limit 释放后使用漏洞 | |
| CVE-2026-89489 | OpenRISC 内核 or1k_atomic 任意内存访问漏洞 | |
| CVE-2026-89500 | ring-buffer 缓冲区读取页修复 | |
| CVE-2026-89497 | Orangefs 调试掩码解析空格处理缺陷 | |
| CVE-2026-89498 | Orangefs 双重释放漏洞 | |
| CVE-2026-89499 | ring-buffer 页面交换失败时停止远程读取 | |
| CVE-2026-89496 | ocfs2文件系统COW完成处理缺陷 | |
| CVE-2026-89501 | ring-buffer 子缓冲区调整时未持锁漏洞 |
显示前 20 条，共 431 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-89741
暂无评论