CVE-2022-49214— Linux kernel 安全漏洞
获取后续新漏洞提醒登录后订阅
一、 漏洞 CVE-2022-49214 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗ 尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
powerpc/64s: Don't use DSISR for SLB faults
来源: 美国国家漏洞数据库 NVD
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: powerpc/64s: Don't use DSISR for SLB faults Since commit 46ddcb3950a2 ("powerpc/mm: Show if a bad page fault on data is read or write.") we use page_fault_is_write(regs->dsisr) in __bad_page_fault() to determine if the fault is for a read or write, and change the message printed accordingly. But SLB faults, aka Data Segment Interrupts, don't set DSISR (Data Storage Interrupt Status Register) to a useful value. All ISA versions from v2.03 through v3.1 specify that the Data Segment Interrupt sets DSISR "to an undefined value". As far as I can see there's no mention of SLB faults setting DSISR in any BookIV content either. This manifests as accesses that should be a read being incorrectly reported as writes, for example, using the xmon "dump" command: 0:mon> d 0x5deadbeef0000000 5deadbeef0000000 [359526.415354][ C6] BUG: Unable to handle kernel data access on write at 0x5deadbeef0000000 [359526.415611][ C6] Faulting instruction address: 0xc00000000010a300 cpu 0x6: Vector: 380 (Data SLB Access) at [c00000000ffbf400] pc: c00000000010a300: mread+0x90/0x190 If we disassemble the PC, we see a load instruction: 0:mon> di c00000000010a300 c00000000010a300 89490000 lbz r10,0(r9) We can also see in exceptions-64s.S that the data_access_slb block doesn't set IDSISR=1, which means it doesn't load DSISR into pt_regs. So the value we're using to determine if the fault is a read/write is some stale value in pt_regs from a previous page fault. Rework the printing logic to separate the SLB fault case out, and only print read/write in the cases where we can determine it. The result looks like eg: 0:mon> d 0x5deadbeef0000000 5deadbeef0000000 [ 721.779525][ C6] BUG: Unable to handle kernel data access at 0x5deadbeef0000000 [ 721.779697][ C6] Faulting instruction address: 0xc00000000014cbe0 cpu 0x6: Vector: 380 (Data SLB Access) at [c00000000ffbf390] 0:mon> d 0 0000000000000000 [ 742.793242][ C6] BUG: Kernel NULL pointer dereference at 0x00000000 [ 742.793316][ C6] Faulting instruction address: 0xc00000000014cbe0 cpu 0x6: Vector: 380 (Data SLB Access) at [c00000000ffbf390]
来源: 美国国家漏洞数据库 NVD
CVSS Information
N/A
来源: 美国国家漏洞数据库 NVD
Vulnerability Type
N/A
来源: 美国国家漏洞数据库 NVD
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于SLB故障，不应使用DSISR。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2022-49214 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2022-49214 的情报信息
请登录查看更多情报信息。
同批安全公告 · Linux · 2025-02-26 · 共 706 条
| CVE-2022-49498 | Linux kernel 安全漏洞 | |
| CVE-2022-49486 | Linux kernel 安全漏洞 | |
| CVE-2022-49488 | Linux kernel 安全漏洞 | |
| CVE-2022-49489 | Linux kernel 安全漏洞 | |
| CVE-2022-49490 | Linux kernel 安全漏洞 | |
| CVE-2022-49491 | Linux kernel 安全漏洞 | |
| CVE-2022-49492 | Linux kernel 安全漏洞 | |
| CVE-2022-49493 | Linux kernel 安全漏洞 | |
| CVE-2022-49494 | Linux kernel 安全漏洞 | |
| CVE-2022-49495 | Linux kernel 安全漏洞 | |
| CVE-2022-49497 | Linux kernel 安全漏洞 | |
| CVE-2022-49496 | Linux kernel 安全漏洞 | |
| CVE-2022-49502 | Linux kernel 安全漏洞 | |
| CVE-2022-49507 | Linux kernel 安全漏洞 | |
| CVE-2022-49508 | Linux kernel 安全漏洞 | |
| CVE-2022-49506 | Linux kernel 安全漏洞 | |
| CVE-2022-49504 | Linux kernel 安全漏洞 | |
| CVE-2022-49505 | Linux kernel 安全漏洞 | |
| CVE-2022-49501 | Linux kernel 安全漏洞 | |
| CVE-2022-49500 | Linux kernel 安全漏洞 |
显示前 20 条，共 706 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2022-49214
暂无评论