cve.bz

CVE-2025-29943 (StackWarp) Write-what-where Condition

4.6 mediumEPSS 0.2%

Known as StackWarp

Medium (4.6). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Write what were condition within AMD CPUs may allow an admin-privileged attacker to modify the configuration of the CPU pipeline potentially resulting in the corruption of the stack pointer inside an SEV-SNP guest.

Severity

CVSS 4.0

4.6 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-01-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-123 Write-what-where Condition
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-29943 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-29943?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-29943?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-29943 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13amd64-microcodeno fix listedDEBIAN-CVE-2025-29943
Debian14amd64-microcode3.20251202.1DEBIAN-CVE-2025-29943
Ubuntu14.04:LTS, 20.04:LTS, 22.04:LTS and 2 moreamd64-microcodeno fix listedUBUNTU-CVE-2025-29943
Ubuntu24.04:LTSamd64-microcode3.20251202.1ubuntu0.24.04.1UBUNTU-CVE-2025-29943
Ubuntu25.10amd64-microcode3.20251202.1ubuntu0.25.10.1UBUNTU-CVE-2025-29943
Ubuntu26.04:LTSamd64-microcode3.20251202.1ubuntu1UBUNTU-CVE-2025-29943
openSUSETumbleweedspectre-meltdown-checker26.36.0602723-1.1openSUSE-SU-2026:11242-1
Alpaquita23, 25linux-firmwareno fix listedBELL-CVE-2025-29943
Alpaquitastreamlinux-firmware20251125-r1BELL-CVE-2025-29943

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON