{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2026-31569", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2026-03-09T15:48:24.117Z", "datePublished": "2026-04-24T14:35:48.768Z", "dateUpdated": "2026-08-05T12:23:33.914Z" }, "containers": { "cna": { "providerMetadata": { "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T12:23:33.914Z" }, "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: KVM: Handle the case that EIOINTC's coremap is empty\n\nEIOINTC's coremap in eiointc_update_sw_coremap() can be empty, currently\nwe get a cpuid with -1 in this case, but we actually need 0 because it's\nsimilar as the case that cpuid >= 4.\n\nThis fix an out-of-bounds access to kvm_arch::phyid_map::phys_map[]." } ], "metrics": [ { "cvssV3_1": { "version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:H", "baseScore": 7.3, "baseSeverity": "HIGH" }, "scenarios": [ { "lang": "en", "value": "AV:L - The vulnerable LoongArch KVM EIOINTC path is reached through local KVM ioctls or by running guest code that causes IOCSR writes on the same host, not by network packets.\nAC:L - An attacker who can create/control a LoongArch KVM VM can supply an empty EIOINTC coremap deterministically; no race or external timing condition is required.\nPR:L - The path requires access to KVM VM/device/vCPU interfaces or control of a guest VM, which is a low-privileged local/tenant capability rather than host administrator privilege.\nUI:N - Once the attacker controls the VM/VMM inputs, triggering the bad coremap update does not require any separate victim action.\nS:C - The bug is in host KVM emulation and can be triggered from the guest/VMM boundary, so a guest or local KVM tenant can affect the host kernel security scope.\nC:L - The flaw creates a bounded negative-index host kernel read adjacent to kvm_arch::phyid_map::phys_map; there is no direct bulk memory disclosure path, but host kernel memory is still accessed out of bounds.\nI:N - The investigated path does not provide a defensible arbitrary write or host data modification primitive; the direct effect is bad lookup/interrupt routing rather than host integrity compromise.\nA:H - The out-of-bounds access is reachable on demand and was observed as a kernel UBSAN warning; on hardened or panic-on-warn configurations, and potentially with unlucky adjacent data, this can crash or destabilize the host kernel." } ] } ], "affected": [ { "product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/loongarch/kvm/intc/eiointc.c" ], "versions": [ { "version": "3956a52bc05bd811082a3c9d2b423ee957e6fefc", "lessThan": "126053d0a685bf1f2e98db8966386f38b2336338", "status": "affected", "versionType": "git" }, { "version": "3956a52bc05bd811082a3c9d2b423ee957e6fefc", "lessThan": "2a0cbcd28ecf6e0b88fa498bebb94bd1be61a7c3", "status": "affected", "versionType": "git" }, { "version": "3956a52bc05bd811082a3c9d2b423ee957e6fefc", "lessThan": "b97bd69eb0f67b5f961b304d28e9ba45e202d841", "status": "affected", "versionType": "git" } ] }, { "product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": [ "arch/loongarch/kvm/intc/eiointc.c" ], "versions": [ { "version": "6.13", "status": "affected" }, { "version": "0", "lessThan": "6.13", "status": "unaffected", "versionType": "semver" }, { "version": "6.18.21", "lessThanOrEqual": "6.18.*", "status": "unaffected", "versionType": "semver" }, { "version": "6.19.11", "lessThanOrEqual": "6.19.*", "status": "unaffected", "versionType": "semver" }, { "version": "7.0", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix" } ] } ], "cpeApplicability": [ { "nodes": [ { "operator": "OR", "negate": false, "cpeMatch": [ { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.13", "versionEndExcluding": "6.18.21" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.13", "versionEndExcluding": "6.19.11" }, { "vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.13", "versionEndExcluding": "7.0" } ] } ] } ], "references": [ { "url": "https://git.kernel.org/stable/c/126053d0a685bf1f2e98db8966386f38b2336338" }, { "url": "https://git.kernel.org/stable/c/2a0cbcd28ecf6e0b88fa498bebb94bd1be61a7c3" }, { "url": "https://git.kernel.org/stable/c/b97bd69eb0f67b5f961b304d28e9ba45e202d841" } ], "title": "LoongArch: KVM: Handle the case that EIOINTC's coremap is empty", "x_generator": { "engine": "bippy-1.2.0" } } } }