CVE-2024-47717— RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
Quick assessment
Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于RISC-V KVM中在释放数据前未清零PMU快照区域，可能导致空指针取消引用。
Possible ATT&CK Techniques 1 AI
T1055.008 · Ptrace System CallsAffected Version Matrix 8
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| Linux | Linux | c2f41ddbcdd75689d9f512638a40263e3127be93< 81aa95fd5bd14ff49617f07fa79a8d1f1cf2ce9a |
affected |
c2f41ddbcdd75689d9f512638a40263e3127be93< 6d0a5dcfc78bd18f2abb9641f83380135494559b |
affected | ||
c2f41ddbcdd75689d9f512638a40263e3127be93< 47d40d93292d9cff8dabb735bed83d930fa03950 |
affected | ||
6.10 |
affected | ||
< 6.10 |
unaffected | ||
6.10.13≤ 6.10.* |
unaffected | ||
6.11.2≤ 6.11.* |
unaffected | ||
6.12≤ * |
unaffected |
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2024-47717
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
With the latest Linux-6.11-rc3, the below NULL pointer crash is observed
when SBI PMU snapshot is enabled for the guest and the guest is forcefully
powered-off.
Unable to handle kernel NULL pointer dereference at virtual address 0000000000000508
Oops [#1]
Modules linked in: kvm
CPU: 0 UID: 0 PID: 61 Comm: term-poll Not tainted 6.11.0-rc3-00018-g44d7178dd77a #3
Hardware name: riscv-virtio,qemu (DT)
epc : __kvm_write_guest_page+0x94/0xa6 [kvm]
ra : __kvm_write_guest_page+0x54/0xa6 [kvm]
epc : ffffffff01590e98 ra : ffffffff01590e58 sp : ffff8f80001f39b0
gp : ffffffff81512a60 tp : ffffaf80024872c0 t0 : ffffaf800247e000
t1 : 00000000000007e0 t2 : 0000000000000000 s0 : ffff8f80001f39f0
s1 : 00007fff89ac4000 a0 : ffffffff015dd7e8 a1 : 0000000000000086
a2 : 0000000000000000 a3 : ffffaf8000000000 a4 : ffffaf80024882c0
a5 : 0000000000000000 a6 : ffffaf800328d780 a7 : 00000000000001cc
s2 : ffffaf800197bd00 s3 : 00000000000828c4 s4 : ffffaf800248c000
s5 : ffffaf800247d000 s6 : 0000000000001000 s7 : 0000000000001000
s8 : 0000000000000000 s9 : 00007fff861fd500 s10: 0000000000000001
s11: 0000000000800000 t3 : 00000000000004d3 t4 : 00000000000004d3
t5 : ffffffff814126e0 t6 : ffffffff81412700
status: 0000000200000120 badaddr: 0000000000000508 cause: 000000000000000d
[<ffffffff01590e98>] __kvm_write_guest_page+0x94/0xa6 [kvm]
[<ffffffff015943a6>] kvm_vcpu_write_guest+0x56/0x90 [kvm]
[<ffffffff015a175c>] kvm_pmu_clear_snapshot_area+0x42/0x7e [kvm]
[<ffffffff015a1972>] kvm_riscv_vcpu_pmu_deinit.part.0+0xe0/0x14e [kvm]
[<ffffffff015a2ad0>] kvm_riscv_vcpu_pmu_deinit+0x1a/0x24 [kvm]
[<ffffffff0159b344>] kvm_arch_vcpu_destroy+0x28/0x4c [kvm]
[<ffffffff0158e420>] kvm_destroy_vcpus+0x5a/0xda [kvm]
[<ffffffff0159930c>] kvm_arch_destroy_vm+0x14/0x28 [kvm]
[<ffffffff01593260>] kvm_destroy_vm+0x168/0x2a0 [kvm]
[<ffffffff015933d4>] kvm_put_kvm+0x3c/0x58 [kvm]
[<ffffffff01593412>] kvm_vm_release+0x22/0x2e [kvm]
Clearly, the kvm_vcpu_write_guest() function is crashing because it is
being called from kvm_pmu_clear_snapshot_area() upon guest tear down.
To address the above issue, simplify the kvm_pmu_clear_snapshot_area() to
not zero-out PMU snapshot area from kvm_pmu_clear_snapshot_area() because
the guest is anyway being tore down.
The kvm_pmu_clear_snapshot_area() is also called when guest changes
PMU snapshot area of a VCPU but even in this case the previous PMU
snaphsot area must not be zeroed-out because the guest might have
reclaimed the pervious PMU snapshot area for some other purpose.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于RISC-V KVM中在释放数据前未清零PMU快照区域，可能导致空指针取消引用。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2024-47717
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2024-47717
请登录查看更多情报信息。
Patches & Fixes for CVE-2024-47717 (1)
Same Patch Batch · Linux · 2024-10-21 · 372 CVEs total
| CVE-2024-50043 | 9.8 CRITICAL | nfsd: fix possible badness in FREE_STATEID |
| CVE-2022-48985 | 9.8 CRITICAL | net: mana: Fix race on per-CQ variable napi work_done |
| CVE-2024-47695 | 9.8 CRITICAL | RDMA/rtrs-clt: Reset cid to con_num - 1 to stay in bounds |
| CVE-2024-50033 | 9.8 CRITICAL | slip: make slhc_remember() more robust against malicious packets |
| CVE-2024-49855 | 9.8 CRITICAL | nbd: fix race between timeout and normal completion |
| CVE-2024-50047 | 9.8 CRITICAL | smb: client: fix UAF in async decryption |
| CVE-2022-49003 | 9.8 CRITICAL | nvme: fix SRCU protection of nvme_ns_head list |
| CVE-2024-50046 | 9.8 CRITICAL | NFSv4: Prevent NULL-pointer dereference in nfs42_complete_copies() |
| CVE-2024-49996 | 9.4 CRITICAL | cifs: Fix buffer overflow when parsing NFS reparse points |
| CVE-2024-47678 | 9.4 CRITICAL | icmp: change the order of rate limits |
| CVE-2022-49017 | 8.8 HIGH | tipc: re-fetch skb cb after tipc_msg_validate |
| CVE-2024-50029 | 8.8 HIGH | Bluetooth: hci_conn: Fix UAF in hci_enhanced_setup_sync |
| CVE-2024-50041 | 8.8 HIGH | i40e: Fix macvlan leak by synchronizing access to mac_filter_hash |
| CVE-2024-49939 | 8.8 HIGH | wifi: rtw89: avoid to add interface to list twice when SER |
| CVE-2022-48960 | 8.8 HIGH | net: hisilicon: Fix potential use-after-free in hix5hd2_rx() |
| CVE-2022-48962 | 8.8 HIGH | net: hisilicon: Fix potential use-after-free in hisi_femac_rx() |
| CVE-2022-48964 | 8.8 HIGH | ravb: Fix potential use-after-free in ravb_rx_gbeth() |
| CVE-2022-49015 | 8.8 HIGH | net: hsr: Fix potential use-after-free |
| CVE-2022-48967 | 8.8 HIGH | NFC: nci: Bounds check struct nfc_target arrays |
| CVE-2024-49930 | 8.8 HIGH | wifi: ath11k: fix array out-of-bound access in SoC stats |
Showing top 20 of 372 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
-
CVE-2026-80589
block: stop the timeout timer when releasing a never added d -
CVE-2026-80588
mptcp: reclaim forward-allocated memory on RX path errors -
CVE-2026-80587
mptcp: avoid combining some incoming suboptions -
CVE-2026-80586
mptcp: options: reset DSS fields in case of unexpected size -
CVE-2026-80585
mptcp: fastopen: only mark MPTFO subflows with SYN data
Same vendor: Linux
-
CVE-2026-80589
block: stop the timeout timer when releasing a never added d -
CVE-2026-80588
mptcp: reclaim forward-allocated memory on RX path errors -
CVE-2026-80587
mptcp: avoid combining some incoming suboptions -
CVE-2026-80586
mptcp: options: reset DSS fields in case of unexpected size -
CVE-2026-80585
mptcp: fastopen: only mark MPTFO subflows with SYN data
V. Comments for CVE-2024-47717
No comments yet