CVE-2024-47717
- Source
- https://nvd.nist.gov/vuln/detail/CVE-2024-47717
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47717.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2024-47717
- Downstream
- Related
- Published
- 2024-10-21T11:53:48Z
- Modified
- 2025-10-15T15:51:02.045573Z
- Summary
- RISC-V: KVM: Don't zero-out PMU snapshot area before freeing data
- Details
-
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 : _kvmwriteguestpage+0x94/0xa6 [kvm] ra : _kvmwriteguestpage+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>] _kvmwriteguestpage+0x94/0xa6 [kvm] [<ffffffff015943a6>] kvmvcpuwriteguest+0x56/0x90 [kvm] [<ffffffff015a175c>] kvmpmuclearsnapshotarea+0x42/0x7e [kvm] [<ffffffff015a1972>] kvmriscvvcpupmudeinit.part.0+0xe0/0x14e [kvm] [<ffffffff015a2ad0>] kvmriscvvcpupmudeinit+0x1a/0x24 [kvm] [<ffffffff0159b344>] kvmarchvcpudestroy+0x28/0x4c [kvm] [<ffffffff0158e420>] kvmdestroyvcpus+0x5a/0xda [kvm] [<ffffffff0159930c>] kvmarchdestroyvm+0x14/0x28 [kvm] [<ffffffff01593260>] kvmdestroyvm+0x168/0x2a0 [kvm] [<ffffffff015933d4>] kvmputkvm+0x3c/0x58 [kvm] [<ffffffff01593412>] kvmvm_release+0x22/0x2e [kvm]
Clearly, the kvmvcpuwriteguest() function is crashing because it is being called from kvmpmuclearsnapshot_area() upon guest tear down.
To address the above issue, simplify the kvmpmuclearsnapshotarea() to not zero-out PMU snapshot area from kvmpmuclearsnapshotarea() because the guest is anyway being tore down.
The kvmpmuclearsnapshotarea() 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.
- References
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedc2f41ddbcdd75689d9f512638a40263e3127be93Fixed81aa95fd5bd14ff49617f07fa79a8d1f1cf2ce9a
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedc2f41ddbcdd75689d9f512638a40263e3127be93Fixed6d0a5dcfc78bd18f2abb9641f83380135494559b
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedc2f41ddbcdd75689d9f512638a40263e3127be93Fixed47d40d93292d9cff8dabb735bed83d930fa03950
Affected versions
v6.*
Database specific
{
"vanir_signatures": [
{
"digest": {
"line_hashes": [
"108308544790651461591557140044367736802",
"39293954731067436122672907875353486490",
"35894913522688272593622287761233102483",
"236811222524480259447392002844016925444",
"339126839957693064196832744695286635444",
"324460983151715378785026120070393244584",
"259137152847179062057780500735639709533",
"83162995266118553549187873513038752323",
"290384633576042786091704616677008422254",
"212246903434745023225898688304206140470",
"206224369110316573598300780057537344144",
"248829541129506160032478480956986665083",
"216095317652138977564037160095520478903",
"277028980179305645377343116013913929583",
"326285017710635420390527032251285919452"
],
"threshold": 0.9
},
"source": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git@47d40d93292d9cff8dabb735bed83d930fa03950",
"signature_type": "Line",
"target": {
"file": "arch/riscv/kvm/vcpu_pmu.c"
},
"deprecated": false,
"signature_version": "v1",
"id": "CVE-2024-47717-4f737b3a"
},
{
"digest": {
"length": 423.0,
"function_hash": "74513715111347092663638866662921453106"
},
"source": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git@47d40d93292d9cff8dabb735bed83d930fa03950",
"signature_type": "Function",
"target": {
"function": "kvm_pmu_clear_snapshot_area",
"file": "arch/riscv/kvm/vcpu_pmu.c"
},
"deprecated": false,
"signature_version": "v1",
"id": "CVE-2024-47717-de3ed858"
}
]
}