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

目标: 1000 元 · 已筹: 1000

100.0%

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

EPSS 0.02% · P5
获取后续新漏洞提醒登录后订阅

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

漏洞信息

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

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

Vulnerability Title
liveupdate: luo_file: remember retrieve() status
来源: 美国国家漏洞数据库 NVD
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: liveupdate: luo_file: remember retrieve() status LUO keeps track of successful retrieve attempts on a LUO file. It does so to avoid multiple retrievals of the same file. Multiple retrievals cause problems because once the file is retrieved, the serialized data structures are likely freed and the file is likely in a very different state from what the code expects. The retrieve boolean in struct luo_file keeps track of this, and is passed to the finish callback so it knows what work was already done and what it has left to do. All this works well when retrieve succeeds. When it fails, luo_retrieve_file() returns the error immediately, without ever storing anywhere that a retrieve was attempted or what its error code was. This results in an errored LIVEUPDATE_SESSION_RETRIEVE_FD ioctl to userspace, but nothing prevents it from trying this again. The retry is problematic for much of the same reasons listed above. The file is likely in a very different state than what the retrieve logic normally expects, and it might even have freed some serialization data structures. Attempting to access them or free them again is going to break things. For example, if memfd managed to restore 8 of its 10 folios, but fails on the 9th, a subsequent retrieve attempt will try to call kho_restore_folio() on the first folio again, and that will fail with a warning since it is an invalid operation. Apart from the retry, finish() also breaks. Since on failure the retrieved bool in luo_file is never touched, the finish() call on session close will tell the file handler that retrieve was never attempted, and it will try to access or free the data structures that might not exist, much in the same way as the retry attempt. There is no sane way of attempting the retrieve again. Remember the error retrieve returned and directly return it on a retry. Also pass this status code to finish() so it can make the right decision on the work it needs to do. This is done by changing the bool to an integer. A value of 0 means retrieve was never attempted, a positive value means it succeeded, and a negative value means it failed and the error code is the value.
来源: 美国国家漏洞数据库 NVD
CVSS Information
N/A
来源: 美国国家漏洞数据库 NVD
Vulnerability Type
N/A
来源: 美国国家漏洞数据库 NVD
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于luo_retrieve_file函数在检索失败时未记录尝试状态,可能导致重复检索引发问题。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商产品影响版本CPE订阅
LinuxLinux 7c722a7f44e0c1f9714084152226bc7bd644b7e3 ~ 1d3ad69484dc1cc53be62d2554e7ef038a627af9 -
LinuxLinux 6.19 -

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

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

未找到公开 POC。

登录以生成 AI POC

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

登录查看更多情报信息。

同批安全公告 · Linux · 2026-05-13 · 共 14 条

CVE-2026-43487Linux kernel 安全漏洞
CVE-2026-43488Linux kernel 安全漏洞
CVE-2026-43485Linux kernel 安全漏洞
CVE-2026-43486Linux kernel 安全漏洞
CVE-2026-43484Linux kernel 安全漏洞
CVE-2026-43482Linux kernel 安全漏洞
CVE-2026-43483Linux kernel 安全漏洞
CVE-2026-43480Linux kernel 安全漏洞
CVE-2026-43481Linux kernel 安全漏洞
CVE-2026-43479Linux kernel 安全漏洞
CVE-2026-43477Linux kernel 安全漏洞
CVE-2026-43478Linux kernel 安全漏洞
CVE-2026-43476Linux kernel 安全漏洞

IV. Related Vulnerabilities

V. Comments for CVE-2026-43489

暂无评论


发表评论