CVE-2023-54296: KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 2ee4b180d51b12a45bdd3264629719ef6a572a73, 5.19, 5c18ace750e4d4d58d7da02d1c669bf21c824158.
Low priority for now. Upgrade to Linux Linux 2ee4b180d51b12a45bdd3264629719ef6a572a73, 5.19, 5c18ace750e4d4d58d7da02d1c669bf21c824158 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Get source vCPUs from source VM for SEV-ES intrahost migration Fix a goof where KVM tries to grab source vCPUs from the destination VM when doing intrahost migration. Grabbing the wrong vCPU not only hoses the guest, it also crashes the host due to the VMSA pointer being left NULL. BUG: unable to handle page fault for address: ffffe38687000000 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] SMP NOPTI CPU: 39 PID: 17143 Comm: sev_migrate_tes Tainted: GO 6.5.0-smp--fff2e47e6c3b-next #151 Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.28.0 07/10/2023 RIP: 0010:__free_pages+0x15/0xd0 RSP: 0018:ffff923fcf6e3c78 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffe38687000000 RCX: 0000000000000100 RDX: 0000000000000100 RSI: 0000000000000000 RDI: ffffe38687000000 RBP: ffff923fcf6e3c88 R08: ffff923fcafb0000 R09: 0000000000000000 R10: 0000000000000000 R11: ffffffff83619b90 R12: ffff923fa9540000 R13: 0000000000080007 R14: ffff923f6d35d000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff929d0d7c0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffe38687000000 CR3: 0000005224c34005 CR4: 0000000000770ee0 PKRU: 55555554 Call Trace: <TASK> sev_free_vcpu+0xcb/0x110 [kvm_amd] svm_vcpu_free+0x75/0xf0 [kvm_amd] kvm_arch_vcpu_destroy+0x36/0x140 [kvm] kvm_destroy_vcpus+0x67/0x100 [kvm] kvm_arch_destroy_vm+0x161/0x1d0 [kvm] kvm_put_kvm+0x276/0x560 [kvm] kvm_vm_release+0x25/0x30 [kvm] __fput+0x106/0x280 ____fput+0x12/0x20 task_work_run+0x86/0xb0 do_exit+0x2e3/0x9c0 do_group_exit+0xb1/0xc0 __x64_sys_exit_group+0x1b/0x20 do_syscall_64+0x41/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd </TASK> CR2: ffffe38687000000
- Published
- Dec 30, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 229334a8b1d0d5e60d3bdd091bbc4552d5321c97, 5.19affected
- 6defa24d3b12bbd418bc8526dea1cbc605265c06 and later · before 5c18ace750e4d4d58d7da02d1c669bf21c824158affected · git
- 6defa24d3b12bbd418bc8526dea1cbc605265c06 and later · before 2ee4b180d51b12a45bdd3264629719ef6a572a73affected · git
- 6defa24d3b12bbd418bc8526dea1cbc605265c06 and later · before f1187ef24eb8f36e8ad8106d22615ceddeea6097affected · git
- 5.18.8 and later · before 5.19affected · semver
- before 5.19not affected · semver
- 6.1.54 and later · up to and including 6.1.*not affected · semver
- 6.5.4 and later · up to and including 6.5.*not affected · semver
- 6.6 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-tools | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-tools-libs | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-tools-libs-devel | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-core | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-devel | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-modules | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
| AlmaLinux:8 | perf | before 4.18.0-553.34.1.el8_10 | 4.18.0-553.34.1.el8_10 |
+37
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2023-54294Dec 30, 2025 · md/raid10: fix memleak of md thread0Monitor
- ← EarlierCVE-2023-54295Dec 30, 2025 · mtd: spi-nor: Fix shift-out-of-bounds in spi_nor_set_erase_type0Monitor
- Later →CVE-2023-54297Dec 30, 2025 · btrfs: zoned: fix memory leak after finding block group with super blocks0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2ee4b180d51b12a45bdd3264629719ef6a572a73 | Vendor (CNA) |
| Linux Linux | 5.19 | Vendor (CNA) |
| Linux Linux | 5c18ace750e4d4d58d7da02d1c669bf21c824158 | Vendor (CNA) |
| Linux Linux | f1187ef24eb8f36e8ad8106d22615ceddeea6097 | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.34.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.55-1 · Debian:12 | Package registry (OSV) |
| red hat:bpftool | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:bpftool-debuginfo | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-abi-stablelists | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-core | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-core | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debug-modules-extra | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:4.18.0-553.34.1.el8_10 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.