{ "schema_version": "1.6.1", "id": "RPI-CVE-2024-26598", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2024-26598" ], "published": "2024-02-23T14:48:05Z", "summary": "KVM: arm64: vgic-its: Avoid potential UAF in LPI translation cache", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: arm64: vgic-its: Avoid potential UAF in LPI translation cache\n\nThere is a potential UAF scenario in the case of an LPI translation\ncache hit racing with an operation that invalidates the cache, such\nas a DISCARD ITS command. The root of the problem is that\nvgic_its_check_cache() does not elevate the refcount on the vgic_irq\nbefore dropping the lock that serializes refcount changes.\n\nHave vgic_its_check_cache() raise the refcount on the returned vgic_irq\nand add the corresponding decrement after queueing the interrupt.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:12", "name": "linux" }, "versions": [ "1:6.1.21-1+rpt1", "1:6.1.47-1+rpt2", "1:6.1.47-1+rpt4", "1:6.1.54-1+rpt2", "1:6.1.58-1+rpt2", "1:6.1.63-1+rpt1", "1:6.1.73-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.1.0-rpi1-rpi-v8", "binary_version": "1:6.1.21-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi2-rpi-v8", "binary_version": "1:6.1.47-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-2712", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v6", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi3-rpi-v8", "binary_version": "1:6.1.47-1+rpt4" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-2712", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi4-rpi-v8", "binary_version": "1:6.1.54-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi6-rpi-2712", "binary_version": "1:6.1.58-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi6-rpi-v8", "binary_version": "1:6.1.58-1+rpt2" }, { "binary_name": "linux-image-6.1.0-rpi7-rpi-2712", "binary_version": "1:6.1.63-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi7-rpi-v8", "binary_version": "1:6.1.63-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi8-rpi-2712", "binary_version": "1:6.1.73-1+rpt1" }, { "binary_name": "linux-image-6.1.0-rpi8-rpi-v8", "binary_version": "1:6.1.73-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.1.21-1+rpt1": { "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed", "upstream_version": "6.1.21", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.75" }, "1:6.1.47-1+rpt2": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.75" }, "1:6.1.47-1+rpt4": { "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e", "upstream_version": "6.1.47", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.75", "compiled_filter": false }, "1:6.1.54-1+rpt2": { "linux_commit": "2906f7abdc03d4a92b6b0e2e0c87ea2a9dffe8f7", "upstream_version": "6.1.54", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.75" }, "1:6.1.58-1+rpt2": { "linux_commit": "ccf1586ad0663fa91238ac56abf6340d6d740d18", "upstream_version": "6.1.58", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.1.75" }, "1:6.1.63-1+rpt1": { "linux_commit": null, "upstream_version": "6.1.63", "assessment": "upstream version (no usable Linux commit)", "upstream_fixed": "6.1.75" }, "1:6.1.73-1+rpt1": { "linux_commit": null, "upstream_version": "6.1.73", "assessment": "upstream version (no usable Linux commit)", "upstream_fixed": "6.1.75" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2024-26598" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/d04acadb6490aa3314f9c9e087691e55de153b88" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/ba7be666740847d967822bed15500656b26bc703" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/12c2759ab1343c124ed46ba48f27bd1ef5d2dff4" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/dba788e25f05209adf2b0175eb1691dc89fb1ba6" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/65b201bf3e9af1b0254243a5881390eda56f72d1" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/dd3956a1b3dd11f46488c928cb890d6937d1ca80" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/ad362fe07fecf0aba839ff2cc59a3617bd42c33f" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-08-05T11:52:36Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 8.8, "cvss_v3_severity": "High", "scenario": "AV:L - Exploitation requires running code inside a KVM/arm64 guest (to issue ITS DISCARD/MAPD commands via GITS_CWRITER) or holding local /dev/kvm access to drive KVM_SIGNAL_MSI, so the attacker needs local access to the host or a VM on it. No purely remote network path can drive both sides of the race.\nAC:L - The attacker controls both sides of the race \u2014 one vCPU thread issues DISCARD/MAPD ITS commands while another CPU (vhost worker via irqfd, or a userspace KVM_SIGNAL_MSI thread) performs the cache lookup \u2014 and can prime the cache deterministically with an INT command and repeat the loop indefinitely without any detection or rate limit.\nPR:L - The attacker only needs to be an unprivileged guest (or a local unprivileged user with /dev/kvm access, which is standard on virtualization hosts); no host root or special capability is required, and ITS emulation is created by default by QEMU's virt machine with GICv3.\nUI:N - The entire sequence \u2014 MAPTI/INT to populate the translation cache, MSI generation, and the DISCARD command \u2014 is driven autonomously by the attacker from inside the guest. No victim action is needed.\nS:C - The vulnerable component is KVM's vGIC ITS emulation, whose security authority is the guest VM, but the corrupted memory is host kernel heap; a guest crossing into host kernel memory is a guest-to-host boundary violation.\nC:H - The freed vgic_irq can be reallocated with attacker-controlled data and is then read back (intid, priority, group, config, vcpu/target_vcpu pointers) and re-linked into live host kernel lists, giving an arbitrary-pointer dereference and kernel memory disclosure primitive.\nI:H - The stale pointer is written through \u2014 spinlock acquire, pending_latch store, kref increment, and list_add_tail writing both into the freed chunk and storing its address into the live ap_list \u2014 a use-after-free write primitive leveragable for control-flow hijack and host privilege escalation.\nA:H - Even without successful heap grooming, the use-after-free corrupts the vgic ap_list and LPI list, reliably producing kernel oops, list-corruption BUG, or lock-up, taking down the entire host and all co-resident VMs." } } }