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

目标: 1000 元 · 已筹: 1359 元

100%

CVE-2022-50118— Linux kernel 安全漏洞

一分钟漏洞结论

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

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于未正确处理PMI标记,可能导致警告信息误报。

EPSS 0.19% · P9

影响版本矩阵 16

厂商产品 版本范围状态
Linux Linux ef798cd035f316a537fee8ed170c127f12407085< 875b2bf469d094754ac2ba9af91dcd529eb12bf6 affected
fadcafa3959281ce2d96feedece8c75c3f95f8a5< 87b1a9175f08313f40fcb6d6dc536dbe451090eb affected
2c9ac51b850d84ee496b0a5d832ce66d411ae552< 0a24ea26c3278216642a43291df7976a73a0a7ee affected
2c9ac51b850d84ee496b0a5d832ce66d411ae552< 7e83af3dd4a3afca8f83ffde518cafd52f45b830 affected
2c9ac51b850d84ee496b0a5d832ce66d411ae552< 890005a7d98f7452cfe86dcfb2aeeb7df01132ce affected
215a90ce3754fe509efbce6b73a4bb643c7e7528 affected
5.10.94< 5.10.137 affected
5.15.17< 5.15.61 affected
… +8 条更多
获取后续新漏洞提醒 登录后订阅

一、 漏洞 CVE-2022-50118 基础信息

漏洞信息

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

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

Vulnerability Title
powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Optimize clearing the pending PMI and remove WARN_ON for PMI check in power_pmu_disable commit 2c9ac51b850d ("powerpc/perf: Fix PMU callbacks to clear pending PMI before resetting an overflown PMC") added a new function "pmi_irq_pending" in hw_irq.h. This function is to check if there is a PMI marked as pending in Paca (PACA_IRQ_PMI).This is used in power_pmu_disable in a WARN_ON. The intention here is to provide a warning if there is PMI pending, but no counter is found overflown. During some of the perf runs, below warning is hit: WARNING: CPU: 36 PID: 0 at arch/powerpc/perf/core-book3s.c:1332 power_pmu_disable+0x25c/0x2c0 Modules linked in: ----- NIP [c000000000141c3c] power_pmu_disable+0x25c/0x2c0 LR [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 Call Trace: [c000000baffcfb90] [c000000000141c8c] power_pmu_disable+0x2ac/0x2c0 (unreliable) [c000000baffcfc10] [c0000000003e2f8c] perf_pmu_disable+0x4c/0x60 [c000000baffcfc30] [c0000000003e3344] group_sched_out.part.124+0x44/0x100 [c000000baffcfc80] [c0000000003e353c] __perf_event_disable+0x13c/0x240 [c000000baffcfcd0] [c0000000003dd334] event_function+0xc4/0x140 [c000000baffcfd20] [c0000000003d855c] remote_function+0x7c/0xa0 [c000000baffcfd50] [c00000000026c394] flush_smp_call_function_queue+0xd4/0x300 [c000000baffcfde0] [c000000000065b24] smp_ipi_demux_relaxed+0xa4/0x100 [c000000baffcfe20] [c0000000000cb2b0] xive_muxed_ipi_action+0x20/0x40 [c000000baffcfe40] [c000000000207c3c] __handle_irq_event_percpu+0x8c/0x250 [c000000baffcfee0] [c000000000207e2c] handle_irq_event_percpu+0x2c/0xa0 [c000000baffcff10] [c000000000210a04] handle_percpu_irq+0x84/0xc0 [c000000baffcff40] [c000000000205f14] generic_handle_irq+0x54/0x80 [c000000baffcff60] [c000000000015740] __do_irq+0x90/0x1d0 [c000000baffcff90] [c000000000016990] __do_IRQ+0xc0/0x140 [c0000009732f3940] [c000000bafceaca8] 0xc000000bafceaca8 [c0000009732f39d0] [c000000000016b78] do_IRQ+0x168/0x1c0 [c0000009732f3a00] [c0000000000090c8] hardware_interrupt_common_virt+0x218/0x220 This means that there is no PMC overflown among the active events in the PMU, but there is a PMU pending in Paca. The function "any_pmc_overflown" checks the PMCs on active events in cpuhw->n_events. Code snippet: <<>> if (any_pmc_overflown(cpuhw)) clear_pmi_irq_pending(); else WARN_ON(pmi_irq_pending()); <<>> Here the PMC overflown is not from active event. Example: When we do perf record, default cycles and instructions will be running on PMC6 and PMC5 respectively. It could happen that overflowed event is currently not active and pending PMI is for the inactive event. Debug logs from trace_printk: <<>> any_pmc_overflown: idx is 5: pmc value is 0xd9a power_pmu_disable: PMC1: 0x0, PMC2: 0x0, PMC3: 0x0, PMC4: 0x0, PMC5: 0xd9a, PMC6: 0x80002011 <<>> Here active PMC (from idx) is PMC5 , but overflown PMC is PMC6(0x80002011). When we handle PMI interrupt for such cases, if the PMC overflown is from inactive event, it will be ignored. Reference commit: commit bc09c219b2e6 ("powerpc/perf: Fix finding overflowed PMC in interrupt") Patch addresses two changes: 1) Fix 1 : Removal of warning ( WARN_ON(pmi_irq_pending()); ) We were printing warning if no PMC is found overflown among active PMU events, but PMI pending in PACA. But this could happen in cases where PMC overflown is not in active PMC. An inactive event could have caused the overflow. Hence the warning is not needed. To know pending PMI is from an inactive event, we need to loop through all PMC's which will cause more SPR reads via mfspr and increase in context switch. Also in existing function: perf_event_interrupt, already we ignore PMI's overflown when it is from an inactive PMC. 2) Fix 2: optimization in clearing pending PMI. Currently we check for any active PMC overflown before clearing PMI pending in Paca. This is causing additional SP ---truncated---
来源: 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存在安全漏洞,该漏洞源于未正确处理PMI标记,可能导致警告信息误报。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD

受影响产品

厂商 产品 影响版本 CPE 订阅
Linux Linux ef798cd035f316a537fee8ed170c127f12407085 ~ 875b2bf469d094754ac2ba9af91dcd529eb12bf6 -
Linux Linux 5.17 -

二、漏洞 CVE-2022-50118 的公开POC

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

未找到公开 POC。

登录以生成 AI POC

三、漏洞 CVE-2022-50118 的情报信息

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

同批安全公告 · Linux · 2025-06-18 · 共 362 条

CVE-2025-38075 9.8 CRITICAL Linux kernel 安全漏洞
CVE-2022-50098 8.8 HIGH Linux kernel 安全漏洞
CVE-2022-49934 8.8 HIGH Linux kernel 安全漏洞
CVE-2025-38052 8.8 HIGH Linux kernel 安全漏洞
CVE-2022-50164 8.8 HIGH Linux kernel 安全漏洞
CVE-2025-38016 8.8 HIGH Linux kernel 安全漏洞
CVE-2022-49974 8.8 HIGH Linux kernel 安全漏洞
CVE-2025-38074 8.8 HIGH Linux kernel 安全漏洞
CVE-2022-49968 8.0 HIGH Linux kernel 安全漏洞
CVE-2022-49939 7.8 HIGH Linux kernel 安全漏洞
CVE-2022-50022 7.8 HIGH Linux kernel 安全漏洞
CVE-2022-50028 7.8 HIGH Linux kernel 安全漏洞
CVE-2022-49935 7.8 HIGH Linux kernel 安全漏洞
CVE-2025-38082 7.8 HIGH Linux kernel 安全漏洞
CVE-2022-50182 7.8 HIGH Linux kernel 安全漏洞
CVE-2025-38080 7.8 HIGH Linux kernel 安全漏洞
CVE-2025-38079 7.8 HIGH Linux kernel 安全漏洞
CVE-2022-50099 7.8 HIGH Linux kernel 安全漏洞
CVE-2025-38062 7.8 HIGH Linux kernel 安全漏洞
CVE-2025-38060 7.8 HIGH Linux kernel 安全漏洞

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

IV. Related Vulnerabilities

V. Comments for CVE-2022-50118

暂无评论


发表评论