H19Int15CallbackSmm: SMM memory corruption vulnerability in combined DXE/SMM (SMRAM write)

published 2025-12-12 11mo ago modified 2026-10-07 last mo. also EUVD-2025-202936

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 4%
public exploits: 0; none known

Unchecked output buffer may allowed arbitrary code execution in SMM and potentially result in SMM memory corruption.

Is CVE-2025-10451 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 10mo ago (2025-12-12)

Exploit prediction

0.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Affected products

Insyde Software InsydeH2O

Classification

Weakness

CWE-787 Out-of-bounds Write

References

insyde.com /security-pledge/sa-2025009/

Sources

CVE List CVE-2025-10451
NVD CVE-2025-10451

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.