CVE-2024-49998— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于net子系统中的dsa驱动在关闭时的不当处理，可能导致竞争条件和内核崩溃。
可能的 ATT&CK 技术 1 AI
T1211 · Exploitation for Stealth影响版本矩阵 17
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | ff45899e732e57088985e3a497b1d9100571c0f5< 87bd909a7014e32790e8c759d5b7694a95778ca5 |
affected |
ee534378f00561207656663d93907583958339ae< ab9e90619b6339becc5415647ae154a9a46a044d |
affected | ||
ee534378f00561207656663d93907583958339ae< 2e93bf719462ac6d23c881c8b93e5dc9bf5ab7f5 |
affected | ||
ee534378f00561207656663d93907583958339ae< ab5d3420a1120950703dbdc33698b28a6ebc3d23 |
affected | ||
ee534378f00561207656663d93907583958339ae< b4a65d479213fe84ecb14e328271251eebe69492 |
affected | ||
ee534378f00561207656663d93907583958339ae< 6c24a03a61a245fe34d47582898331fa034b6ccd |
affected | ||
89b60402d43cdab4387dbbf24afebda5cf092ae7 |
affected | ||
5.15.155< 5.15.176 |
affected | ||
| … +9 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2024-49998 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
net: dsa: improve shutdown sequence
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: improve shutdown sequence
Alexander Sverdlin presents 2 problems during shutdown with the
lan9303 driver. One is specific to lan9303 and the other just happens
to reproduce there.
The first problem is that lan9303 is unique among DSA drivers in that it
calls dev_get_drvdata() at "arbitrary runtime" (not probe, not shutdown,
not remove):
phy_state_machine()
-> ...
-> dsa_user_phy_read()
-> ds->ops->phy_read()
-> lan9303_phy_read()
-> chip->ops->phy_read()
-> lan9303_mdio_phy_read()
-> dev_get_drvdata()
But we never stop the phy_state_machine(), so it may continue to run
after dsa_switch_shutdown(). Our common pattern in all DSA drivers is
to set drvdata to NULL to suppress the remove() method that may come
afterwards. But in this case it will result in an NPD.
The second problem is that the way in which we set
dp->conduit->dsa_ptr = NULL; is concurrent with receive packet
processing. dsa_switch_rcv() checks once whether dev->dsa_ptr is NULL,
but afterwards, rather than continuing to use that non-NULL value,
dev->dsa_ptr is dereferenced again and again without NULL checks:
dsa_conduit_find_user() and many other places. In between dereferences,
there is no locking to ensure that what was valid once continues to be
valid.
Both problems have the common aspect that closing the conduit interface
solves them.
In the first case, dev_close(conduit) triggers the NETDEV_GOING_DOWN
event in dsa_user_netdevice_event() which closes user ports as well.
dsa_port_disable_rt() calls phylink_stop(), which synchronously stops
the phylink state machine, and ds->ops->phy_read() will thus no longer
call into the driver after this point.
In the second case, dev_close(conduit) should do this, as per
Documentation/networking/driver.rst:
| Quiescence
| ----------
|
| After the ndo_stop routine has been called, the hardware must
| not receive or transmit any data. All in flight packets must
| be aborted. If necessary, poll or wait for completion of
| any reset commands.
So it should be sufficient to ensure that later, when we zeroize
conduit->dsa_ptr, there will be no concurrent dsa_switch_rcv() call
on this conduit.
The addition of the netif_device_detach() function is to ensure that
ioctls, rtnetlinks and ethtool requests on the user ports no longer
propagate down to the driver - we're no longer prepared to handle them.
The race condition actually did not exist when commit 0650bf52b31f
("net: dsa: be compatible with masters which unregister on shutdown")
first introduced dsa_switch_shutdown(). It was created later, when we
stopped unregistering the user interfaces from a bad spot, and we just
replaced that sequence with a racy zeroization of conduit->dsa_ptr
(one which doesn't ensure that the interfaces aren't up).
来源: 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存在安全漏洞，该漏洞源于net子系统中的dsa驱动在关闭时的不当处理，可能导致竞争条件和内核崩溃。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2024-49998 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2024-49998 的情报信息
请登录查看更多情报信息。
CVE-2024-49998 补丁与修复 (5)
同批安全公告 · Linux · 2024-10-21 · 共 372 条
| CVE-2024-50033 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-49855 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-47695 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2022-48985 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2022-49003 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-50043 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-50047 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-50046 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-49996 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2024-47678 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2022-48962 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49950 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49939 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2022-48967 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2022-48964 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-50029 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49930 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-50041 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2024-49936 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2022-48954 | 8.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 372 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2024-49998
暂无评论