CVE-2026-68096— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一个操作系统内核。 Linux kernel存在安全漏洞，该漏洞源于审计子系统在复制可执行相关规则时，通过kern_path_parent()解析路径，尝试获取任务已持有的I_MUTEX_PARENT目录锁，导致递归锁死锁。
可能的 ATT&CK 技术 1 AI
T1564.004 · NTFS File Attributes影响版本矩阵 18
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 6114c3f21eb2ae175401736da744b684705e7ed9 |
affected |
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< f6fda0ac6661c23b8356dfb1cc423960cc6f0593 |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 3bbb4931f7cd84cecf29ec222c0732bf9ad4da9f |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 36eb77f14b4e6f2dc1008c1fabe31236397be27a |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 7d1f66c69898ffb1a718926c32a777ecc471caca |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 40879c39d6740f3dddfb52b5d6ba7fb8cceb84d8 |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 3b601938314c24fcd1afb6659cad92fe96c9c2f8 |
affected | ||
34d99af52ad40bd498ba66970579a5bc1fb1a3bc< 81905b5acbe77284734438df3fbec1158e6429a3 |
affected | ||
| … +10 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-68096 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
audit: fix recursive locking deadlock in audit_dupe_exe()
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
audit: fix recursive locking deadlock in audit_dupe_exe()
A deadlock occurs in the audit subsystem when duplicating
executable-related rules.
When a file is moved (e.g., via do_renameat2()), the VFS layer locks
the parent directory (I_MUTEX_PARENT), which synchronously triggers an
fsnotify_move event. If an existing executable audit rule matches the
file being moved, the audit subsystem catches this event and calls
audit_dupe_exe() to duplicate the watch and update the rule. Then,
audit_alloc_mark() would call kern_path_parent() to resolve the path,
leading to a blind attempt to acquire the exact same I_MUTEX_PARENT lock
already held by the task, resulting in the following recursive locking
deadlock:
============================================
WARNING: possible recursive locking detected
6.12.0-55.27.1.el10_0.x86_64+debug #1 Not tainted
--------------------------------------------
mv/5099 is trying to acquire lock:
ffff888132845358 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3},
at: __kern_path_locked+0x10a/0x2f0
but task is already holding lock:
ffff888132846b58 (&inode->i_sb->s_type->i_mutex_dir_key/1){+.+.}-{3:3},
at: lock_two_directories+0x13f/0x2b0
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&inode->i_sb->s_type->i_mutex_dir_key/1);
lock(&inode->i_sb->s_type->i_mutex_dir_key/1);
*** DEADLOCK ***
May be due to missing lock nesting notation
6 locks held by mv/5099:
#0: ffff888112a9c440 (sb_writers#13)
at: do_renameat2+0x34c/0xbc0
#1: ffff888112a9c790 (&type->s_vfs_rename_key#3)
at: do_renameat2+0x415/0xbc0
#2: ffff888132846b58 (&inode->i_sb->s_type->i_mutex_dir_key/1)
at: lock_two_directories+0x13f/0x2b0
#3: ffff888132845358 (&inode->i_sb->s_type->i_mutex_dir_key/5)
at: lock_two_directories+0x175/0x2b0
#4: ffffffffb3a1fb10 (&fsnotify_mark_srcu)
at: fsnotify+0x454/0x28a0
#5: ffffffffaf886230 (audit_filter_mutex)
at: audit_update_watch+0x36/0x11e0
stack backtrace:
Call Trace:
<TASK>
dump_stack_lvl+0x6f/0xb0
print_deadlock_bug.cold+0xbd/0xca
validate_chain+0x83a/0xf00
__lock_acquire+0xcac/0x1d20
lock_acquire.part.0+0x11b/0x360
down_write_nested+0x9f/0x230
__kern_path_locked+0x10a/0x2f0
kern_path_locked+0x26/0x40
audit_alloc_mark+0xfb/0x4f0
audit_dupe_exe+0x6c/0xe0
audit_dupe_rule+0x6c2/0xc00
audit_update_watch+0x4cc/0x11e0
audit_watch_handle_event+0x12c/0x1b0
send_to_group+0x5d0/0x8b0
fsnotify+0x615/0x28a0
fsnotify_move+0x1d8/0x630
vfs_rename+0xdcd/0x1df0
do_renameat2+0x9d4/0xbc0
__x64_sys_renameat+0x192/0x260
do_syscall_64+0x92/0x180
entry_SYSCALL_64_after_hwframe+0x76/0x7e
RIP: 0033:0x7f0491fe8c4e
Code: 0f 1f 40 00 48 8b 15 c1 e1 16 00 f7 d8 64 89 02 b8 ff ff ff ff
c3 66 0f 1f 44 00 00 f3 0f 1e fa 49 89 ca b8 08 01 00 00 0f 05 <48>
3d 00 f0 ff ff 77 0a c3 66 0f 1f 84 00 00 00 00 00 48 8b 15 89
RSP: 002b:00007ffc7210bf38 EFLAGS: 00000246 ORIG_RAX: 0000000000000108
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f0491fe8c4e
RDX: 0000000000000003 RSI: 00007ffc7210e6c8 RDI: 00000000ffffff9c
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000001
R10: 00005575eb2dae2a R11: 0000000000000246 R12: 00005575eb2dae2a
R13: 00007ffc7210e6c8 R14: 0000000000000003 R15: 00000000ffffff9c
</TASK>
The aforementioned deadlock can be consistently reproduced by running
the script below:
audit-dupe-exe-deadlock.sh
--------------------------
#!/bin/bash
auditctl -D
mkdir -p /tmp/foo
touch /tmp/file
auditctl -a always,exit -F exe=/tmp/file -F path=/tmp/file -S all -k dr
mv /tmp/file /tmp/foo/file
rm -Rf /tmp/foo
This patch fixes the issue by introducing struct audit_watch_ctx to pass
the fsnotify event context down to audit_alloc_mark(). By utilizing the
already-resolved directory inode provided by the event, we bypass the
kern_path_parent() path resol
---truncated---
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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存在安全漏洞，该漏洞源于审计子系统在复制可执行相关规则时，通过kern_path_parent()解析路径，尝试获取任务已持有的I_MUTEX_PARENT目录锁，导致递归锁死锁。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-68096 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-68096 的情报信息
请登录查看更多情报信息。
CVE-2026-68096 补丁与修复 (8)
同批安全公告 · Linux · 2026-08-10 · 共 344 条
| CVE-2026-68160 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68300 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68136 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68137 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68144 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68302 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68127 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68154 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68156 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68158 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68159 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68381 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68385 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68170 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68426 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68123 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68117 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68161 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68388 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-68124 | 9.6 CRITICAL | Linux kernel 安全漏洞 |
显示前 20 条，共 344 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-68096
暂无评论