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

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2021-46997— Linux kernel 安全漏洞

一分钟漏洞结论

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

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel 存在安全漏洞,该漏洞源于不会在异常入口序列中设置 GIC_PRIO_PSR_I_SET。

AI 预测 5.5 利用难度: 理论可行 EPSS 0.25% · P15

可能的 ATT&CK 技术 1 AI

T1562.001

影响版本矩阵 10

厂商产品 版本范围状态
Linux Linux 23529049c68423820487304f244144e0d576e85a< 51524fa8b5f7b879ba569227738375d283b79382 affected
23529049c68423820487304f244144e0d576e85a< e67a83f078005461b59b4c776e6b5addd11725fa affected
23529049c68423820487304f244144e0d576e85a< d8d52005f57bbb4a4ec02f647e2555d327135c68 affected
23529049c68423820487304f244144e0d576e85a< 4d6a38da8e79e94cbd1344aa90876f0f805db705 affected
5.10 affected
< 5.10 unaffected
5.10.38≤ 5.10.* unaffected
5.11.22≤ 5.11.* unaffected
… +2 条更多
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2021-46997 基础信息

漏洞信息

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

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

Vulnerability Title
arm64: entry: always set GIC_PRIO_PSR_I_SET during entry
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: arm64: entry: always set GIC_PRIO_PSR_I_SET during entry Zenghui reports that booting a kernel with "irqchip.gicv3_pseudo_nmi=1" on the command line hits a warning during kernel entry, due to the way we manipulate the PMR. Early in the entry sequence, we call lockdep_hardirqs_off() to inform lockdep that interrupts have been masked (as the HW sets DAIF wqhen entering an exception). Architecturally PMR_EL1 is not affected by exception entry, and we don't set GIC_PRIO_PSR_I_SET in the PMR early in the exception entry sequence, so early in exception entry the PMR can indicate that interrupts are unmasked even though they are masked by DAIF. If DEBUG_LOCKDEP is selected, lockdep_hardirqs_off() will check that interrupts are masked, before we set GIC_PRIO_PSR_I_SET in any of the exception entry paths, and hence lockdep_hardirqs_off() will WARN() that something is amiss. We can avoid this by consistently setting GIC_PRIO_PSR_I_SET during exception entry so that kernel code sees a consistent environment. We must also update local_daif_inherit() to undo this, as currently only touches DAIF. For other paths, local_daif_restore() will update both DAIF and the PMR. With this done, we can remove the existing special cases which set this later in the entry code. We always use (GIC_PRIO_IRQON | GIC_PRIO_PSR_I_SET) for consistency with local_daif_save(), as this will warn if it ever encounters (GIC_PRIO_IRQOFF | GIC_PRIO_PSR_I_SET), and never sets this itself. This matches the gic_prio_kentry_setup that we have to retain for ret_to_user. The original splat from Zenghui's report was: | DEBUG_LOCKS_WARN_ON(!irqs_disabled()) | WARNING: CPU: 3 PID: 125 at kernel/locking/lockdep.c:4258 lockdep_hardirqs_off+0xd4/0xe8 | Modules linked in: | CPU: 3 PID: 125 Comm: modprobe Tainted: G W 5.12.0-rc8+ #463 | Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 | pstate: 604003c5 (nZCv DAIF +PAN -UAO -TCO BTYPE=--) | pc : lockdep_hardirqs_off+0xd4/0xe8 | lr : lockdep_hardirqs_off+0xd4/0xe8 | sp : ffff80002a39bad0 | pmr_save: 000000e0 | x29: ffff80002a39bad0 x28: ffff0000de214bc0 | x27: ffff0000de1c0400 x26: 000000000049b328 | x25: 0000000000406f30 x24: ffff0000de1c00a0 | x23: 0000000020400005 x22: ffff8000105f747c | x21: 0000000096000044 x20: 0000000000498ef9 | x19: ffff80002a39bc88 x18: ffffffffffffffff | x17: 0000000000000000 x16: ffff800011c61eb0 | x15: ffff800011700a88 x14: 0720072007200720 | x13: 0720072007200720 x12: 0720072007200720 | x11: 0720072007200720 x10: 0720072007200720 | x9 : ffff80002a39bad0 x8 : ffff80002a39bad0 | x7 : ffff8000119f0800 x6 : c0000000ffff7fff | x5 : ffff8000119f07a8 x4 : 0000000000000001 | x3 : 9bcdab23f2432800 x2 : ffff800011730538 | x1 : 9bcdab23f2432800 x0 : 0000000000000000 | Call trace: | lockdep_hardirqs_off+0xd4/0xe8 | enter_from_kernel_mode.isra.5+0x7c/0xa8 | el1_abort+0x24/0x100 | el1_sync_handler+0x80/0xd0 | el1_sync+0x6c/0x100 | __arch_clear_user+0xc/0x90 | load_elf_binary+0x9fc/0x1450 | bprm_execve+0x404/0x880 | kernel_execve+0x180/0x188 | call_usermodehelper_exec_async+0xdc/0x158 | ret_from_fork+0x10/0x18
来源: 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 存在安全漏洞,该漏洞源于不会在异常入口序列中设置 GIC_PRIO_PSR_I_SET。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
Linux Linux 23529049c68423820487304f244144e0d576e85a ~ 51524fa8b5f7b879ba569227738375d283b79382 -
Linux Linux 5.10 -

二、漏洞 CVE-2021-46997 的公开POC

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

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2021-46997 的情报信息

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

CVE-2021-46997 其他参考 (4)

同批安全公告 · Linux · 2024-02-28 · 共 86 条

CVE-2021-47013 9.8 CRITICAL Linux kernel 安全漏洞
CVE-2021-46999 9.8 CRITICAL Linux kernel 安全漏洞
CVE-2021-47036 9.8 CRITICAL Linux kernel 安全漏洞
CVE-2021-47017 8.8 HIGH Linux kernel 安全漏洞
CVE-2021-47035 8.8 HIGH Linux kernel 安全漏洞
CVE-2021-47049 8.4 HIGH Linux kernel 安全漏洞
CVE-2021-47014 7.8 HIGH Linux kernel 安全漏洞
CVE-2020-36785 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-47040 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-46998 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-47048 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-46984 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-46993 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-46977 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-47012 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-47011 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-46992 7.8 HIGH Linux kernel 安全漏洞
CVE-2020-36787 7.8 HIGH Linux kernel 安全漏洞
CVE-2021-47001 7.5 HIGH Linux kernel 安全漏洞
CVE-2021-46983 7.5 HIGH Linux kernel 安全漏洞

显示前 20 条,共 86 条。 查看全部 &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2021-46997

暂无评论


发表评论