CVE-2024-46830 (GCVE-0-2024-46830)
Vulnerability from cvelistv5 – Published: 2024-09-27 12:39 – Updated: 2026-08-05 11:38
VLAI
EPSS
VEX
Title
KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS
Summary
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: Acquire kvm->srcu when handling KVM_SET_VCPU_EVENTS
Grab kvm->srcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly
leave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX
reads guest memory.
Note, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN
via sync_regs(), which already holds SRCU. I.e. trying to precisely use
kvm_vcpu_srcu_read_lock() around the problematic SMM code would cause
problems. Acquiring SRCU isn't all that expensive, so for simplicity,
grab it unconditionally for KVM_SET_VCPU_EVENTS.
=============================
WARNING: suspicious RCU usage
6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted
-----------------------------
include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!
other info that might help us debug this:
rcu_scheduler_active = 2, debug_locks = 1
1 lock held by repro/1071:
#0: ffff88811e424430 (&vcpu->mutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]
stack backtrace:
CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
Call Trace:
<TASK>
dump_stack_lvl+0x7f/0x90
lockdep_rcu_suspicious+0x13f/0x1a0
kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]
kvm_vcpu_read_guest+0x3e/0x90 [kvm]
nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]
load_vmcs12_host_state+0x432/0xb40 [kvm_intel]
vmx_leave_nested+0x30/0x40 [kvm_intel]
kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]
kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]
? mark_held_locks+0x49/0x70
? kvm_vcpu_ioctl+0x7d/0x970 [kvm]
? kvm_vcpu_ioctl+0x497/0x970 [kvm]
kvm_vcpu_ioctl+0x497/0x970 [kvm]
? lock_acquire+0xba/0x2d0
? find_held_lock+0x2b/0x80
? do_user_addr_fault+0x40c/0x6f0
? lock_release+0xb7/0x270
__x64_sys_ioctl+0x82/0xb0
do_syscall_64+0x6c/0x170
entry_SYSCALL_64_after_hwframe+0x4b/0x53
RIP: 0033:0x7ff11eb1b539
</TASK>
Severity
7.8 (High)
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2024-09-29 14:12 UTC
Assigner
References
6 references
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Linux | Linux |
Affected:
e302786233e6bc512986d007c96458ccf5ca21c7 , < 5f35099fa3d59caf10bda88b033538e90086684e
(git)
Affected: f7e570780efc5cec9b2ed1e0472a7da14e864fdb , < fa297c33faefe51e10244e8a378837fca4963228 (git) Affected: f7e570780efc5cec9b2ed1e0472a7da14e864fdb , < 939375737b5a0b1bf9b1e75129054e11bc9ca65e (git) Affected: f7e570780efc5cec9b2ed1e0472a7da14e864fdb , < ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9 (git) Affected: f7e570780efc5cec9b2ed1e0472a7da14e864fdb , < 4bcdd831d9d01e0fb64faea50732b59b2ee88da1 (git) Affected: 080dbe7e9b86a0392d8dffc00d9971792afc121f (git) Affected: b4c0d89c92e957ecccce12e66b63875d0cc7af7e (git) Affected: 5.15.19 , < 5.15.198 (semver) Affected: 5.10.97 , < 5.11 (semver) Affected: 5.16.5 , < 5.17 (semver) |
guessed | |
| Linux | Linux |
Affected:
5.17
Unaffected: 0 , < 5.17 (semver) Unaffected: 5.15.198 , ≤ 5.15.* (semver) Unaffected: 6.1.110 , ≤ 6.1.* (semver) Unaffected: 6.6.51 , ≤ 6.6.* (semver) Unaffected: 6.10.10 , ≤ 6.10.* (semver) Unaffected: 6.11 , ≤ * (original_commit_for_fix) |
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2024-46830",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2024-09-29T14:12:09.375859Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2024-09-29T14:12:18.179Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"providerMetadata": {
"dateUpdated": "2025-11-03T22:19:21.236Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/x86.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "5f35099fa3d59caf10bda88b033538e90086684e",
"status": "affected",
"version": "e302786233e6bc512986d007c96458ccf5ca21c7",
"versionType": "git"
},
{
"lessThan": "fa297c33faefe51e10244e8a378837fca4963228",
"status": "affected",
"version": "f7e570780efc5cec9b2ed1e0472a7da14e864fdb",
"versionType": "git"
},
{
"lessThan": "939375737b5a0b1bf9b1e75129054e11bc9ca65e",
"status": "affected",
"version": "f7e570780efc5cec9b2ed1e0472a7da14e864fdb",
"versionType": "git"
},
{
"lessThan": "ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9",
"status": "affected",
"version": "f7e570780efc5cec9b2ed1e0472a7da14e864fdb",
"versionType": "git"
},
{
"lessThan": "4bcdd831d9d01e0fb64faea50732b59b2ee88da1",
"status": "affected",
"version": "f7e570780efc5cec9b2ed1e0472a7da14e864fdb",
"versionType": "git"
},
{
"status": "affected",
"version": "080dbe7e9b86a0392d8dffc00d9971792afc121f",
"versionType": "git"
},
{
"status": "affected",
"version": "b4c0d89c92e957ecccce12e66b63875d0cc7af7e",
"versionType": "git"
},
{
"lessThan": "5.15.198",
"status": "affected",
"version": "5.15.19",
"versionType": "semver"
},
{
"lessThan": "5.11",
"status": "affected",
"version": "5.10.97",
"versionType": "semver"
},
{
"lessThan": "5.17",
"status": "affected",
"version": "5.16.5",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"arch/x86/kvm/x86.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "5.17"
},
{
"lessThan": "5.17",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.198",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.51",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.10.*",
"status": "unaffected",
"version": "6.10.10",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.11",
"versionType": "original_commit_for_fix"
}
]
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.15.198",
"versionStartIncluding": "5.15.19",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.1.110",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.6.51",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.10.10",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionEndExcluding": "6.11",
"versionStartIncluding": "5.17",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.10.97",
"vulnerable": true
},
{
"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
"versionStartIncluding": "5.16.5",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS\n\nGrab kvm-\u003esrcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\nreads guest memory.\n\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\nvia sync_regs(), which already holds SRCU. I.e. trying to precisely use\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\nproblems. Acquiring SRCU isn\u0027t all that expensive, so for simplicity,\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\n\n =============================\n WARNING: suspicious RCU usage\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\n -----------------------------\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\n\n other info that might help us debug this:\n\n rcu_scheduler_active = 2, debug_locks = 1\n 1 lock held by repro/1071:\n #0: ffff88811e424430 (\u0026vcpu-\u003emutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n\n stack backtrace:\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n Call Trace:\n \u003cTASK\u003e\n dump_stack_lvl+0x7f/0x90\n lockdep_rcu_suspicious+0x13f/0x1a0\n kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\n kvm_vcpu_read_guest+0x3e/0x90 [kvm]\n nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\n load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\n vmx_leave_nested+0x30/0x40 [kvm_intel]\n kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\n kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\n ? mark_held_locks+0x49/0x70\n ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\n ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\n kvm_vcpu_ioctl+0x497/0x970 [kvm]\n ? lock_acquire+0xba/0x2d0\n ? find_held_lock+0x2b/0x80\n ? do_user_addr_fault+0x40c/0x6f0\n ? lock_release+0xb7/0x270\n __x64_sys_ioctl+0x82/0xb0\n do_syscall_64+0x6c/0x170\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7ff11eb1b539\n \u003c/TASK\u003e"
}
],
"metrics": [
{
"cvssV3_1": {
"baseScore": 7.8,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"scenarios": [
{
"lang": "en",
"value": "AV:L - The vulnerability is reached solely through ioctls on a KVM vCPU file descriptor (`KVM_SET_NESTED_STATE` then `KVM_SET_VCPU_EVENTS`), racing against `KVM_SET_USER_MEMORY_REGION` on the VM fd. This requires local access to /dev/kvm with no network component.\nAC:L - The attacker owns both sides of the race \u2014 one thread toggles SMM via KVM_SET_VCPU_EVENTS while another deletes/moves memslots \u2014 and the two paths take disjoint locks (vcpu-\u003emutex vs kvm-\u003eslots_lock). Because the unprotected read is a __copy_from_user() on the attacker\u0027s own guest mapping, userfaultfd/FUSE backing can stall the reader inside the window indefinitely, making the race deterministically winnable.\nPR:L - Only an open /dev/kvm descriptor is needed, which systemd\u0027s default udev rule grants world read/write (MODE=0666), and nested-virt CI runners, cloud images, and Android AVF routinely expose KVM to unprivileged users. No CAP_SYS_ADMIN or real root is required.\nUI:N - The attacker\u0027s own process performs every step \u2014 creating the VM, stuffing nested state, toggling SMM, and cycling memslots. No action by any other user is involved.\nS:U - The attacker is already host userspace and the impact is on the host kernel, so no security boundary is crossed; this is not a guest-to-host escape since guest-initiated SMM transitions go through KVM_RUN, which already holds SRCU. Vulnerable and impacted components share the same security authority.\nC:H - The missing SRCU read lock yields a use-after-free read of a kfree()\u0027d struct kvm_memory_slot and of rbtree nodes in search_memslots(), and a reallocated slot gives the attacker control of userspace_addr/base_gfn/npages plus arch.rmap pointers. This permits reading memory of deleted regions and, via heap grooming, arbitrary kernel-memory disclosure.\nI:H - A freed slot that is reallocated with attacker-groomed contents is used to compute host addresses and is consumed by KVM\u0027s MMU and nested_vmx_load_msr(), and the concurrently-mutated rbtree traversal writes back into slots-\u003elast_used_slot. This gives the corruption-and-control-flow primitives characteristic of an exploitable heap UAF.\nA:H - Dereferencing freed memslot objects and walking an rbtree whose nodes are being freed under the reader reliably produces wild-pointer dereferences, oopses, and kernel panics. Any local user with /dev/kvm can trigger this in a loop to crash the host."
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-05T11:38:52.433Z",
"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"shortName": "Linux"
},
"references": [
{
"url": "https://git.kernel.org/stable/c/5f35099fa3d59caf10bda88b033538e90086684e"
},
{
"url": "https://git.kernel.org/stable/c/fa297c33faefe51e10244e8a378837fca4963228"
},
{
"url": "https://git.kernel.org/stable/c/939375737b5a0b1bf9b1e75129054e11bc9ca65e"
},
{
"url": "https://git.kernel.org/stable/c/ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9"
},
{
"url": "https://git.kernel.org/stable/c/4bcdd831d9d01e0fb64faea50732b59b2ee88da1"
}
],
"title": "KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS",
"x_generator": {
"engine": "bippy-1.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"assignerShortName": "Linux",
"cveId": "CVE-2024-46830",
"datePublished": "2024-09-27T12:39:28.396Z",
"dateReserved": "2024-09-11T15:12:18.286Z",
"dateUpdated": "2026-08-05T11:38:52.433Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2024-46830",
"date": "2026-09-13",
"epss": "0.00247",
"percentile": "0.16056"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2024-46830\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-09-27T13:15:15.380\",\"lastModified\":\"2026-08-04T11:20:30.960\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS\\n\\nGrab kvm-\u003esrcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\\nreads guest memory.\\n\\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\\nvia sync_regs(), which already holds SRCU. I.e. trying to precisely use\\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\\nproblems. Acquiring SRCU isn\u0027t all that expensive, so for simplicity,\\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\\n\\n =============================\\n WARNING: suspicious RCU usage\\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\\n -----------------------------\\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\\n\\n other info that might help us debug this:\\n\\n rcu_scheduler_active = 2, debug_locks = 1\\n 1 lock held by repro/1071:\\n #0: ffff88811e424430 (\u0026vcpu-\u003emutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\\n\\n stack backtrace:\\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\\n Call Trace:\\n \u003cTASK\u003e\\n dump_stack_lvl+0x7f/0x90\\n lockdep_rcu_suspicious+0x13f/0x1a0\\n kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\\n kvm_vcpu_read_guest+0x3e/0x90 [kvm]\\n nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\\n load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\\n vmx_leave_nested+0x30/0x40 [kvm_intel]\\n kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\\n kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\\n ? mark_held_locks+0x49/0x70\\n ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\\n ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\\n kvm_vcpu_ioctl+0x497/0x970 [kvm]\\n ? lock_acquire+0xba/0x2d0\\n ? find_held_lock+0x2b/0x80\\n ? do_user_addr_fault+0x40c/0x6f0\\n ? lock_release+0xb7/0x270\\n __x64_sys_ioctl+0x82/0xb0\\n do_syscall_64+0x6c/0x170\\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\\n RIP: 0033:0x7ff11eb1b539\\n \u003c/TASK\u003e\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: KVM: x86: Adquirir kvm-\u0026gt;srcu al manejar KVM_SET_VCPU_EVENTS Adquiera kvm-\u0026gt;srcu al procesar KVM_SET_VCPU_EVENTS, ya que KVM abandonar\u00e1 a la fuerza el VMX/SVM anidado si se alterna el modo SMM, y al abandonar el VMX anidado se lee la memoria del invitado. Tenga en cuenta que kvm_vcpu_ioctl_x86_set_vcpu_events() tambi\u00e9n se puede llamar desde KVM_RUN a trav\u00e9s de sync_regs(), que ya contiene SRCU. Es decir, intentar usar con precisi\u00f3n kvm_vcpu_srcu_read_lock() alrededor del c\u00f3digo SMM problem\u00e1tico causar\u00eda problemas. Adquirir SRCU no es tan caro, as\u00ed que para simplificar, t\u00f3melo incondicionalmente para KVM_SET_VCPU_EVENTS. ============================= ADVERTENCIA: uso sospechoso de RCU 6.10.0-rc7-332d2c1d713e-next-vm #552 No contaminado ----------------------------- include/linux/kvm_host.h:1027 \u00a1Uso sospechoso de rcu_dereference_check()! Otra informaci\u00f3n que podr\u00eda ayudarnos a depurar esto: rcu_scheduler_active = 2, debug_locks = 1 1 bloqueo retenido por repro/1071: #0: ffff88811e424430 (\u0026amp;vcpu-\u0026gt;mutex){+.+.}-{3:3}, en: kvm_vcpu_ioctl+0x7d/0x970 [kvm] seguimiento de pila: CPU: 15 PID: 1071 Comm: repro No contaminado 6.10.0-rc7-332d2c1d713e-next-vm #552 Nombre del hardware: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Seguimiento de llamadas: dump_stack_lvl+0x7f/0x90 kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm] kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm] ? kvm_vcpu_ioctl+0x497/0x970 [kvm] kvm_vcpu_ioctl+0x497/0x970 [kvm] ? bloqueo_adquirir+0xba/0x2d0 ? encontrar_bloqueo_retenido+0x2b/0x80 ? hacer_error_direcci\u00f3n_usuario+0x40c/0x6f0 ? liberaci\u00f3n_de_bloqueo+0xb7/0x270 __x64_sys_ioctl+0x82/0xb0 hacer_llamada_al_sistema_64+0x6c/0x170 entrada_SYSCALL_64_despu\u00e9s_de_hwframe+0x4b/0x53 RIP: 0033:0x7ff11eb1b539 \"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"arch/x86/kvm/x86.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"e302786233e6bc512986d007c96458ccf5ca21c7\",\"lessThan\":\"5f35099fa3d59caf10bda88b033538e90086684e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\",\"lessThan\":\"fa297c33faefe51e10244e8a378837fca4963228\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\",\"lessThan\":\"939375737b5a0b1bf9b1e75129054e11bc9ca65e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\",\"lessThan\":\"ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\",\"lessThan\":\"4bcdd831d9d01e0fb64faea50732b59b2ee88da1\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"080dbe7e9b86a0392d8dffc00d9971792afc121f\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"b4c0d89c92e957ecccce12e66b63875d0cc7af7e\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"5.15.19\",\"lessThan\":\"5.15.198\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"5.10.97\",\"lessThan\":\"5.11\",\"versionType\":\"semver\",\"status\":\"affected\"},{\"version\":\"5.16.5\",\"lessThan\":\"5.17\",\"versionType\":\"semver\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"arch/x86/kvm/x86.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.17\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.17\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.198\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.110\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.51\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.10.10\",\"lessThanOrEqual\":\"6.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-09-29T14:12:09.375859Z\",\"id\":\"CVE-2024-46830\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*\",\"matchCriteriaId\":\"FA6FEEC2-9F11-4643-8827-749718254FED\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.10.97\",\"versionEndExcluding\":\"5.11\",\"matchCriteriaId\":\"6CDC103F-CA28-421D-9F6C-F133A3A06F17\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.15.19\",\"versionEndExcluding\":\"5.15.198\",\"matchCriteriaId\":\"5BC080EF-13AB-4B4C-A969-2E51CE23720D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16.5\",\"versionEndExcluding\":\"5.17\",\"matchCriteriaId\":\"DFA0DD9B-9B37-4E0C-8DEF-2E20FE0A8B51\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.17.1\",\"versionEndExcluding\":\"6.1.110\",\"matchCriteriaId\":\"E40366D5-0D82-49F9-AB3E-C54A428951B7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.51\",\"matchCriteriaId\":\"E4529134-BAC4-4776-840B-304009E181A0\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.10.10\",\"matchCriteriaId\":\"ACDEE48C-137A-4731-90D0-A675865E1BED\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"8B3CE743-2126-47A3-8B7C-822B502CF119\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"4DEB27E7-30AA-45CC-8934-B89263EF3551\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"E0005AEF-856E-47EB-BFE4-90C46899394D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"39889A68-6D34-47A6-82FC-CD0BF23D6754\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"B8383ABF-1457-401F-9B61-EE50F4C61F4F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.11:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"B77A9280-37E6-49AD-B559-5B23A3B1DC3D\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/4bcdd831d9d01e0fb64faea50732b59b2ee88da1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/5f35099fa3d59caf10bda88b033538e90086684e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/939375737b5a0b1bf9b1e75129054e11bc9ca65e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/fa297c33faefe51e10244e8a378837fca4963228\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Third Party Advisory\"]}]}}",
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-09-13T09:30:37+00:00",
"cve": "CVE-2024-46830",
"id": "CVE-2024-46830",
"initial_release_date": "2024-09-27T00:00:00+00:00",
"product_status:known_affected": "198",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "kernel: KVM: x86: Acquire kvm-\u0026gt;srcu when handling KVM_SET_VCPU_EVENTS",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-46830.json",
"version": "3"
},
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T22:19:21.236Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-46830\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-29T14:12:09.375859Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-29T14:12:10.454Z\"}}], \"cna\": {\"title\": \"KVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"e302786233e6bc512986d007c96458ccf5ca21c7\", \"lessThan\": \"5f35099fa3d59caf10bda88b033538e90086684e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\", \"lessThan\": \"fa297c33faefe51e10244e8a378837fca4963228\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\", \"lessThan\": \"939375737b5a0b1bf9b1e75129054e11bc9ca65e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\", \"lessThan\": \"ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"f7e570780efc5cec9b2ed1e0472a7da14e864fdb\", \"lessThan\": \"4bcdd831d9d01e0fb64faea50732b59b2ee88da1\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"080dbe7e9b86a0392d8dffc00d9971792afc121f\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"b4c0d89c92e957ecccce12e66b63875d0cc7af7e\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"5.15.19\", \"lessThan\": \"5.15.198\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"5.10.97\", \"lessThan\": \"5.11\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"5.16.5\", \"lessThan\": \"5.17\", \"versionType\": \"semver\"}], \"programFiles\": [\"arch/x86/kvm/x86.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.17\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.17\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.15.198\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"6.1.110\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.51\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.10.10\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.10.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"arch/x86/kvm/x86.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/5f35099fa3d59caf10bda88b033538e90086684e\"}, {\"url\": \"https://git.kernel.org/stable/c/fa297c33faefe51e10244e8a378837fca4963228\"}, {\"url\": \"https://git.kernel.org/stable/c/939375737b5a0b1bf9b1e75129054e11bc9ca65e\"}, {\"url\": \"https://git.kernel.org/stable/c/ecdbe8ac86fb5538ccc623a41f88ec96c7168ab9\"}, {\"url\": \"https://git.kernel.org/stable/c/4bcdd831d9d01e0fb64faea50732b59b2ee88da1\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nKVM: x86: Acquire kvm-\u003esrcu when handling KVM_SET_VCPU_EVENTS\\n\\nGrab kvm-\u003esrcu when processing KVM_SET_VCPU_EVENTS, as KVM will forcibly\\nleave nested VMX/SVM if SMM mode is being toggled, and leaving nested VMX\\nreads guest memory.\\n\\nNote, kvm_vcpu_ioctl_x86_set_vcpu_events() can also be called from KVM_RUN\\nvia sync_regs(), which already holds SRCU. I.e. trying to precisely use\\nkvm_vcpu_srcu_read_lock() around the problematic SMM code would cause\\nproblems. Acquiring SRCU isn\u0027t all that expensive, so for simplicity,\\ngrab it unconditionally for KVM_SET_VCPU_EVENTS.\\n\\n =============================\\n WARNING: suspicious RCU usage\\n 6.10.0-rc7-332d2c1d713e-next-vm #552 Not tainted\\n -----------------------------\\n include/linux/kvm_host.h:1027 suspicious rcu_dereference_check() usage!\\n\\n other info that might help us debug this:\\n\\n rcu_scheduler_active = 2, debug_locks = 1\\n 1 lock held by repro/1071:\\n #0: ffff88811e424430 (\u0026vcpu-\u003emutex){+.+.}-{3:3}, at: kvm_vcpu_ioctl+0x7d/0x970 [kvm]\\n\\n stack backtrace:\\n CPU: 15 PID: 1071 Comm: repro Not tainted 6.10.0-rc7-332d2c1d713e-next-vm #552\\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\\n Call Trace:\\n \u003cTASK\u003e\\n dump_stack_lvl+0x7f/0x90\\n lockdep_rcu_suspicious+0x13f/0x1a0\\n kvm_vcpu_gfn_to_memslot+0x168/0x190 [kvm]\\n kvm_vcpu_read_guest+0x3e/0x90 [kvm]\\n nested_vmx_load_msr+0x6b/0x1d0 [kvm_intel]\\n load_vmcs12_host_state+0x432/0xb40 [kvm_intel]\\n vmx_leave_nested+0x30/0x40 [kvm_intel]\\n kvm_vcpu_ioctl_x86_set_vcpu_events+0x15d/0x2b0 [kvm]\\n kvm_arch_vcpu_ioctl+0x1107/0x1750 [kvm]\\n ? mark_held_locks+0x49/0x70\\n ? kvm_vcpu_ioctl+0x7d/0x970 [kvm]\\n ? kvm_vcpu_ioctl+0x497/0x970 [kvm]\\n kvm_vcpu_ioctl+0x497/0x970 [kvm]\\n ? lock_acquire+0xba/0x2d0\\n ? find_held_lock+0x2b/0x80\\n ? do_user_addr_fault+0x40c/0x6f0\\n ? lock_release+0xb7/0x270\\n __x64_sys_ioctl+0x82/0xb0\\n do_syscall_64+0x6c/0x170\\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\\n RIP: 0033:0x7ff11eb1b539\\n \u003c/TASK\u003e\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.198\", \"versionStartIncluding\": \"5.15.19\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.110\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.51\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.10.10\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"5.10.97\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionStartIncluding\": \"5.16.5\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-05-23T15:53:35.775Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2024-46830\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-05-23T15:53:35.775Z\", \"dateReserved\": \"2024-09-11T15:12:18.286Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-09-27T12:39:28.396Z\", \"assignerShortName\": \"Linux\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…