CVE-2026-64309

Name	CVE-2026-64309
Description	In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Do not initialize SNP for ioctl(SNP_COMMIT) Sashiko notes: > if SEV initialization fails and KVM is actively running normal VMs, could a > userspace process trigger this code path via /dev/sev ioctls (e.g., > SEV_PDH_GEN) and zero out MSR_VM_HSAVE_PA globally? Would the next VMRUN > execution for an active VM trigger a general protection fault and crash the > host? The SNP_COMMIT command does not require the firmware to be in any particular state. Skip initializing it if it was previously uninitialized. The SEV-SNP firmware specification doc 56860 does not mention SNP_COMMIT in Table 5 as a command that is allowed in the UNINIT state, but it is in fact allowed and a future documentation update will reflect that.
Source	CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
References	DLA-4724-1

Vulnerable and fixed packages

The table below lists information on source packages.

Source Package	Release	Version	Status
linux (PTS)	bullseye	5.10.223-1	fixed
	bullseye (security)	5.10.262-1	fixed
	bookworm	6.1.176-1	fixed
	bookworm (security)	6.1.180-1	fixed
	trixie	6.12.94-1	vulnerable
	trixie (security)	6.12.101-1	fixed
	forky	7.1.7-1	fixed
	sid	7.1.8-1	fixed
linux-6.12 (PTS)	bookworm (security)	6.12.100-1~deb12u1	fixed

The information below is based on the following data on fixed versions.

Package	Type	Release	Fixed Version	Origin
linux	source	bullseye	(not affected)
linux	source	bookworm	(not affected)
linux	source	trixie	6.12.96-1
linux	source	(unstable)	7.1.4-1
linux-6.12	source	bookworm	6.12.100-1~deb12u1	DLA-4724-1

Notes

[bookworm] - linux <not-affected> (Vulnerable code not present)
[bullseye] - linux <not-affected> (Vulnerable code not present)
https://git.kernel.org/linus/5a1364da2f04217a36e2fdfa2db4ee025b383a20 (7.2-rc1)