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

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2026-68082— Linux kernel 安全漏洞

一分钟漏洞结论

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

Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel存在安全漏洞,该漏洞源于libceph的decode_lockers函数中存在两个不安全的解码操作,缺少边界检查,可能导致恶意或受损的OSD触发越界读取,造成信息泄露。

CVSS 9.8 · Critical EPSS 0.40% · P33

影响版本矩阵 18

厂商产品 版本范围状态
Linux Linux d4ed4a530562881cc5225050e42d96034f405aae< c8ade01170a27d8ede0d761c255268af81e417f8 affected
d4ed4a530562881cc5225050e42d96034f405aae< 001835c599899ef1bd3506a815110a6374451554 affected
d4ed4a530562881cc5225050e42d96034f405aae< 7c422364acd93d7da1dfc27d6b54635a269653a1 affected
d4ed4a530562881cc5225050e42d96034f405aae< 02430f6f729b297e803d0605871f0a670b4eafd6 affected
d4ed4a530562881cc5225050e42d96034f405aae< 57ba829804fe6d34bbac3b826c4b15c1caa54862 affected
d4ed4a530562881cc5225050e42d96034f405aae< 89df5d71f83f8e2781286798fd8ae5e42cf5f1a7 affected
d4ed4a530562881cc5225050e42d96034f405aae< a54be593d0b749161b08a1e56189b2cb9114267a affected
d4ed4a530562881cc5225050e42d96034f405aae< a109a556115271ca7896dcda7b4b7e45e156c227 affected
… +10 条更多
获取后续新漏洞提醒 登录后订阅

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

漏洞信息

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

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

Vulnerability Title
libceph: fix two unsafe bare decodes in decode_lockers()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: libceph: fix two unsafe bare decodes in decode_lockers() decode_lockers() in cls_lock_client.c contains two bare decode operations that allow a malicious or compromised OSD to trigger slab-out-of-bounds reads: 1. ceph_decode_32(p) at the num_lockers field has no preceding bounds check. ceph_start_decoding() accepts struct_len=0 as valid -- the internal ceph_decode_need(p, end, 0, bad) always passes -- so when an OSD sends struct_len=0, ceph_start_decoding() returns success with p == end. The immediately following bare ceph_decode_32(p) then reads 4 bytes past the validated buffer boundary. The garbage value is passed directly to kzalloc_objs() as the locker count. The sibling function decode_watchers() in osd_client.c already uses ceph_decode_32_safe() after its own ceph_start_decoding() call. decode_lockers() was the only site using the bare variant. 2. ceph_decode_8(p) after the decode_locker() loop has no preceding bounds check. If an OSD crafts num_lockers such that the loop advances p exactly to end, the subsequent bare ceph_decode_8(p) reads one byte past the validated buffer boundary. The result is passed directly into *type, which is used as a lock type discriminator by callers, giving an OSD-controlled one-byte OOB read with direct influence over the lock type field. Fix both by replacing bare operations with their safe variants: ceph_decode_32(p) -> ceph_decode_32_safe(p, end, *num_lockers, err_inval) ceph_decode_8(p) -> ceph_decode_8_safe(p, end, *type, err_free_lockers) The goto targets differ intentionally: err_inval: is a new label returning -EINVAL directly. It is used for the pre-allocation failure path where *lockers is not yet allocated and must not be passed to ceph_free_lockers(). err_free_lockers: is the existing label. It is used for the post-allocation failure path where *lockers is allocated and must be freed. ret is set to -EINVAL before ceph_decode_8_safe() so that err_free_lockers returns the correct error code on bounds violation. Without this, err_free_lockers would return a stale ret value (0 from the successful decode_locker() loop), silently swallowing the error. -EINVAL is correct for both failure paths. The data received from the OSD is structurally malformed. -ENOMEM would misrepresent the failure class to callers and to stable@ backporters triaging error paths. Attacker model: a malicious or compromised OSD in a multi-tenant Ceph deployment can trigger this against any kernel client that issues the lock.get_info class method (e.g. during RBD exclusive lock acquisition). [ idryomov: trim changelog, formatting ]
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel存在安全漏洞,该漏洞源于libceph的decode_lockers函数中存在两个不安全的解码操作,缺少边界检查,可能导致恶意或受损的OSD触发越界读取,造成信息泄露。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
Linux Linux d4ed4a530562881cc5225050e42d96034f405aae ~ c8ade01170a27d8ede0d761c255268af81e417f8 -
Linux Linux 4.9 -

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

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

未找到公开 POC。

登录以生成 AI POC

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

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

CVE-2026-68082 补丁与修复 (7)

IV. Related Vulnerabilities

V. Comments for CVE-2026-68082

暂无评论


发表评论