This bug was fixed in the package linux - 6.14.0-35.35
---------------
linux (6.14.0-35.35) plucky; urgency=medium
* plucky/linux: 6.14.0-35.35 -proposed tracker (LP: #2127468)
* VMSCAPE CVE-2025-40300 (LP: #2124105) // CVE-2025-40300
- Documentation/hw-vuln: Add VMSCAPE documentation
- x86/vmscape: Enumerate VMSCAPE bug
- x86/vmscape: Add conditional IBPB mitigation
- x86/vmscape: Enable the mitigation
- x86/bugs: Move cpu_bugs_smt_update() down
- x86/vmscape: Warn when STIBP is disabled with SMT
- x86/vmscape: Add old Intel CPUs to affected list
* VMSCAPE CVE-2025-40300 (LP: #2124105)
- [Config] Enable MITIGATION_VMSCAPE config
-- Manuel Diewald <[email protected]> Fri, 10 Oct 2025
21:09:58 +0200
** Changed in: linux (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
** CVE added: https://cve.org/CVERecord?id=CVE-2025-37838
** CVE added: https://cve.org/CVERecord?id=CVE-2025-38118
** CVE added: https://cve.org/CVERecord?id=CVE-2025-38352
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2124105
Title:
VMSCAPE CVE-2025-40300
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2124105/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs