CVE-2026-63807— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会开源的一款操作系统内核。 Linux kernel 5.12版本存在安全漏洞，该漏洞源于在恢复大页时未预先验证影子页面的gfn是否在目标memslot范围内，可能导致越界访问slots的lpage_info。
影响版本矩阵 16
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 9eba50f8d7fcb61774f160890f98239fa3ab68a6< 7b52008023b7facf40fba3ebe92449bda8ea53b9 |
affected |
9eba50f8d7fcb61774f160890f98239fa3ab68a6< 5cab1c989f938f5e1b9a0de66486f1fc2c28479b |
affected | ||
9eba50f8d7fcb61774f160890f98239fa3ab68a6< 48b91ed7e22bb82571c34f8b80b6ecdc90a6fab8 |
affected | ||
9eba50f8d7fcb61774f160890f98239fa3ab68a6< c5c29b3c268332afe67d598a034c58344540ed92 |
affected | ||
9eba50f8d7fcb61774f160890f98239fa3ab68a6< 18587f9831612e24cd8f24be1ec15478feff7abc |
affected | ||
9eba50f8d7fcb61774f160890f98239fa3ab68a6< b2ae3245ea44dccaa9af676b6747476951883318 |
affected | ||
9eba50f8d7fcb61774f160890f98239fa3ab68a6< ef057cbf825e03b63f6edf5980f96abf3c53089d |
affected | ||
5.12 |
affected | ||
| … +8 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-63807 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level
When recovering hugepages in the shadow MMU, verify that the base gfn of
the shadow page is actually contained within the target memslot, *before*
querying the max mapping level given the shadow page's gfn. Failure to
pre-check the validity of the gfn can lead to an out-of-bounds access to
the slot's lpage_info (which typically manifests as a host #PF because the
lpage_info is vmalloc'd) if the guest creates a hugepage mapping (in its
PTEs) that extends "below" the bounds of a memslot.
When faulting in memory for a guest, and the size of the guest mapping is
greater than KVM's (current) max mapping, then KVM will create a "direct"
shadow page (direct in that there are no gPTEs to shadow, and so the target
gfn is a direct calculation given the base gfn of the shadow page). The
hugepage recovery flow looks for such direct shadow pages, as forcing 4KiB
mappings when dirty logging generates the guest > host mapping size case.
When the 4KiB restriction is lifted, then KVM can replace the shadow page
with a hugepage.
But if KVM originally used a smaller mapping than the guest because the
range of memory covered by the guest hugepage exceeds the bounds of a
memslot, then KVM will link a direct shadow page with a gfn that is outside
the bounds of the memslot being used to fault in memory. The rmap entry
added for the leaf mapping is correct and within bounds, but the gfn of the
leaf SPTE's parent shadow page will be out of bounds.
BUG: unable to handle page fault for address: ffffc90000806ffc
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 100000067 P4D 100000067 PUD 1002a7067 PMD 10612f067 PTE 0
Oops: Oops: 0000 [#1] SMP
CPU: 13 UID: 1000 PID: 757 Comm: mmu_stress_test Not tainted 7.1.0-rc1-48ce1e26eace-x86_pir_to_irr_comments-vm #341 PREEMPT
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
RIP: 0010:kvm_mmu_max_mapping_level+0x79/0x2b0 [kvm]
Call Trace:
<TASK>
kvm_mmu_recover_huge_pages+0x21b/0x320 [kvm]
kvm_set_memslot+0x1ee/0x590 [kvm]
kvm_set_memory_region.part.0+0x3a1/0x4d0 [kvm]
kvm_vm_ioctl+0x9bf/0x15d0 [kvm]
__x64_sys_ioctl+0x8a/0xd0
do_syscall_64+0xb7/0xbb0
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7f21c0f1a9bf
</TASK>
Don't bother pre-checking the bounds of the potential hugepage, i.e. don't
check that e.g. sp->gfn + KVM_PAGES_PER_HPAGE(sp->role.level + 1) is also
within the memslot, as the checks performed by kvm_mmu_max_mapping_level()
are a superset of the basic bounds checks. I.e. pre-checking the full
range would be a dubious micro-optimization.
来源: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
来源: 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 kernel 5.12版本存在安全漏洞，该漏洞源于在恢复大页时未预先验证影子页面的gfn是否在目标memslot范围内，可能导致越界访问slots的lpage_info。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-63807 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-63807 的情报信息
请登录查看更多情报信息。
CVE-2026-63807 补丁与修复 (7)
同批安全公告 · Linux · 2026-07-19 · 共 429 条
| CVE-2026-63795 | 10.0 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63887 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64102 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64142 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63924 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63922 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63857 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-53399 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-53398 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63984 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64162 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64025 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64033 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64055 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63978 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63808 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63800 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-64056 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-63888 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
显示前 20 条，共 429 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-63807
暂无评论