{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-31593 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-31593 is a medium-severity denial of service vulnerability in Linux kernel, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31593 and fix it if it is affected.\n\nWhat it is: CVE-2026-31593 is a medium-severity denial of service vulnerability in Linux kernel, published on 24 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31593 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-31593/ (Markdown: https://insights.sbomify.com/CVE-2026-31593/index.md)","id":"CVE-2026-31593","markdown":"https://insights.sbomify.com/CVE-2026-31593/index.md","name":"CVE-2026-31593","record":{"aliases":["AZL-83648","BELL-CVE-2026-31593","DEBIAN-CVE-2026-31593","GHSA-jp87-j2ph-wv29","ROOT-OS-DEBIAN-11-CVE-2026-31593","ROOT-OS-DEBIAN-12-CVE-2026-31593","ROOT-OS-DEBIAN-13-CVE-2026-31593","UBUNTU-CVE-2026-31593"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel KVM","requires_auth":"low_privilege","summary":"A local attacker can crash the host kernel by triggering an RMP violation when syncing VMSA of an already-launched SEV-SNP vCPU.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU\n\nReject synchronizing vCPU state to its associated VMSA if the vCPU has\nalready been launched, i.e. if the VMSA has already been encrypted.  On a\nhost with SNP enabled, accessing guest-private memory generates an RMP #PF\nand panics the host.\n\n  BUG: unable to handle page fault for address: ff1276cbfdf36000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x80000003) - RMP violation\n  PGD 5a31801067 P4D 5a31802067 PUD 40ccfb5063 PMD 40e5954063 PTE 80000040fdf36163\n  SEV-SNP: PFN 0x40fdf36, RMP entry: [0x6010fffffffff001 - 0x000000000000001f]\n  Oops: Oops: 0003 [#1] SMP NOPTI\n  CPU: 33 UID: 0 PID: 996180 Comm: qemu-system-x86 Tainted: G           OE\n  Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE\n  Hardware name: Dell Inc. PowerEdge R7625/0H1TJT, BIOS 1.5.8 07/21/2023\n  RIP: 0010:sev_es_sync_vmsa+0x54/0x4c0 [kvm_amd]\n  Call Trace:\n   \u003cTASK\u003e\n   snp_launch_update_vmsa+0x19d/0x290 [kvm_amd]\n   snp_launch_finish+0xb6/0x380 [kvm_amd]\n   sev_mem_enc_ioctl+0x14e/0x720 [kvm_amd]\n   kvm_arch_vm_ioctl+0x837/0xcf0 [kvm]\n   kvm_vm_ioctl+0x3fd/0xcc0 [kvm]\n   __x64_sys_ioctl+0xa3/0x100\n   x64_sys_call+0xfe0/0x2350\n   do_syscall_64+0x81/0x10f0\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  RIP: 0033:0x7ffff673287d\n   \u003c/TASK\u003e\n\nNote, the KVM flaw has been present since commit ad73109ae7ec (\"KVM: SVM:\nProvide support to launch and run an SEV-ES guest\"), but has only been\nactively dangerous for the host since SNP support was added.  With SEV-ES,\nKVM would \"just\" clobber guest state, which is totally fine from a host\nkernel perspective since userspace can clobber guest state any time before\nsev_launch_update_vmsa().","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"KVM: SEV: Reject attempts to sync VMSA of an already-launched/encrypted vCPU","id":"CVE-2026-31593","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"PCI: endpoint: pci-epf-vntb: Remove duplicate resource teardown","id":"CVE-2026-31594"},"packages":[],"prev":{"headline":"KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-\u003elock","id":"CVE-2026-31592"},"products":["Linux"],"published":"2026-04-24","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-06-14","vendors":["Linux"]},"summary":"A local attacker can crash the host kernel by triggering an RMP violation when syncing VMSA of an already-launched SEV-SNP vCPU.","url":"https://insights.sbomify.com/CVE-2026-31593/"}