CVE-2024-35970— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于存在死锁。
影响版本矩阵 12
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 314001f0bf927015e459c9d387d62a231fe93af3< b4bc99d04c689b5652665394ae8d3e02fb754153 |
affected |
314001f0bf927015e459c9d387d62a231fe93af3< 84a352b7eba1142a95441380058985ff19f25ec9 |
affected | ||
314001f0bf927015e459c9d387d62a231fe93af3< 601a89ea24d05089debfa2dc896ea9f5937ac7a6 |
affected | ||
314001f0bf927015e459c9d387d62a231fe93af3< 698a95ade1a00e6494482046902b986dfffd1caf |
affected | ||
314001f0bf927015e459c9d387d62a231fe93af3< b46f4eaa4f0ec38909fb0072eea3aeddb32f954e |
affected | ||
5.15 |
affected | ||
< 5.15 |
unaffected | ||
5.15.156≤ 5.15.* |
unaffected | ||
| … +4 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-35970 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
af_unix: Clear stale u->oob_skb.
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
af_unix: Clear stale u->oob_skb.
syzkaller started to report deadlock of unix_gc_lock after commit
4090fa373f0e ("af_unix: Replace garbage collection algorithm."), but
it just uncovers the bug that has been there since commit 314001f0bf92
("af_unix: Add OOB support").
The repro basically does the following.
from socket import *
from array import array
c1, c2 = socketpair(AF_UNIX, SOCK_STREAM)
c1.sendmsg([b'a'], [(SOL_SOCKET, SCM_RIGHTS, array("i", [c2.fileno()]))], MSG_OOB)
c2.recv(1) # blocked as no normal data in recv queue
c2.close() # done async and unblock recv()
c1.close() # done async and trigger GC
A socket sends its file descriptor to itself as OOB data and tries to
receive normal data, but finally recv() fails due to async close().
The problem here is wrong handling of OOB skb in manage_oob(). When
recvmsg() is called without MSG_OOB, manage_oob() is called to check
if the peeked skb is OOB skb. In such a case, manage_oob() pops it
out of the receive queue but does not clear unix_sock(sk)->oob_skb.
This is wrong in terms of uAPI.
Let's say we send "hello" with MSG_OOB, and "world" without MSG_OOB.
The 'o' is handled as OOB data. When recv() is called twice without
MSG_OOB, the OOB data should be lost.
>>> from socket import *
>>> c1, c2 = socketpair(AF_UNIX, SOCK_STREAM, 0)
>>> c1.send(b'hello', MSG_OOB) # 'o' is OOB data
5
>>> c1.send(b'world')
5
>>> c2.recv(5) # OOB data is not received
b'hell'
>>> c2.recv(5) # OOB date is skipped
b'world'
>>> c2.recv(5, MSG_OOB) # This should return an error
b'o'
In the same situation, TCP actually returns -EINVAL for the last
recv().
Also, if we do not clear unix_sk(sk)->oob_skb, unix_poll() always set
EPOLLPRI even though the data has passed through by previous recv().
To avoid these issues, we must clear unix_sk(sk)->oob_skb when dequeuing
it from recv queue.
The reason why the old GC did not trigger the deadlock is because the
old GC relied on the receive queue to detect the loop.
When it is triggered, the socket with OOB data is marked as GC candidate
because file refcount == inflight count (1). However, after traversing
all inflight sockets, the socket still has a positive inflight count (1),
thus the socket is excluded from candidates. Then, the old GC lose the
chance to garbage-collect the socket.
With the old GC, the repro continues to create true garbage that will
never be freed nor detected by kmemleak as it's linked to the global
inflight list. That's why we couldn't even notice the issue.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: 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所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于存在死锁。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-35970 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-35970 的情报信息
请登录查看更多情报信息。
CVE-2024-35970 其他参考 (5)
同批安全公告 · Linux · 2024-05-20 · 共 62 条
| CVE-2024-35969 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35980 | 8.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35987 | 8.4 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35993 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-36007 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-36001 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35954 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35949 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35950 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35951 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35948 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35994 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35990 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35958 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-36009 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35979 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35968 | 7.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35998 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35999 | 7.5 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-35971 | 7.5 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 62 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-35970
暂无评论