dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2024-36355

HIGH · 7.0 CVSS v4.0 Published 2026-02-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (sleep) wake up, potentially resulting in arbitrary code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Improper input validation in the System Management Mode (SMM) handler allows an attacker with Ring0 (kernel) access to write to protected SMRAM and modify execution flow during S3 (sleep) wake-up transitions, potentially achieving arbitrary code execution in the highly privileged SMM context.

MitigationApply vendor-provided firmware updates that patch the SMM handler input validation. Ensure secure boot is enabled and restrict physical access to prevent Ring0 privilege escalation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if S3 sleep states are in use
    Check system power management settings or examine firmware/UEFI configuration for S3 (suspend to RAM) state availability and usage. On Linux, run 'cat /sys/power/state' to see available sleep states; on Windows, check power options for sleep functionality.
    Affected if S3 (suspend to RAM) is enabled or commonly used on the system, as the vulnerability triggers during S3 wake-up transitions
  2. Verify Ring0 (kernel) access model
    Confirm the system allows or has processes running with kernel-level (Ring0) privileges. Check for administrative/root access capabilities and kernel module loading permissions.
    Affected if The system permits untrusted or less-privileged users to attain Ring0/kernel access, which is a prerequisite for exploiting this flaw
  3. Check UEFI/BIOS firmware version
    Access the system UEFI/BIOS setup (typically via F2/Delete at boot) and record the firmware version and vendor. Compare against vendor release notes or security advisories for CVE-2024-36355 to determine if the installed version includes the SMM handler patch.
    Affected if The installed UEFI/BIOS firmware version predates the vendor patch for this SMM input validation vulnerability, or the patch status is unknown
  4. Inspect SMRAM protection status
    If available, use system firmware tools (like dmidecode on Linux or vendor-specific utilities) to examine SMM memory region (SMRAM) lock and protection settings. Verify whether SMM_CORRUPTED or similar status bits are set.
    Affected if SMRAM protection mechanisms are disabled or misconfigured, leaving the SMM memory region writable from Ring0 during S3 transitions
  5. Assess physical access and boot chain security
    Review whether Secure Boot is enabled in UEFI settings and verify physical security controls. Check boot logs for any unexpected firmware modifications or SMM configuration changes.
    Affected if Secure Boot is disabled and the system has physical accessibility that could allow an attacker to escalate to Ring0 before exploiting the SMM handler

The environment is affected if S3 sleep states are enabled, the UEFI/BIOS firmware is unpatched for CVE-2024-36355, and an attacker can obtain Ring0 privileges to trigger the SMM handler vulnerability during wake-up transitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided firmware updates that patch the SMM handler input validation. Ensure secure boot is enabled and restrict physical access to prevent Ring0 privilege escalation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36355 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data