CVE-2024-52877
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 · uneditedAn issue was discovered in Insyde InsydeH2O kernel 5.2 before version 05.29.50, kernel 5.3 before version 05.38.50, kernel 5.4 before version 05.46.50, kernel 5.5 before version 05.54.50, kernel 5.6 before version 05.61.50, and kernel 5.7 before version 05.70.50. In VariableRuntimeDxe driver, callback function SmmCreateVariableLockList () calls CreateVariableLockListInSmm (). In CreateVariableLockListInSmm (), it uses StrSize () to get variable name size and it could lead to a buffer over-read.
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 confidenceBuffer over-read vulnerability in InsydeH2O UEFI firmware's VariableRuntimeDxe driver where CreateVariableLockListInSmm() uses StrSize() to determine variable name size, potentially allowing memory contents to be read beyond buffer boundaries in SMM context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.2, < 5.2.05.29.50>= 5.3, < 5.3.05.38.50>= 5.4, < 5.4.05.46.50>= 5.5, < 5.5.05.54.50>= 5.6, < 5.6.05.61.50>= 5.7, < 5.7.05.70.50CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Retrieve UEFI firmware versionUse system information tools such as 'dmidecode -s bios-version', 'uefi-firmware-version', or check the BIOS/UEFI setup utility (typically accessible via F2, F12, or Del during boot) to obtain the installed InsydeH2O firmware version string.Affected if The displayed firmware version falls within any of these ranges: >= 5.2 and < 5.2.05.29.50; >= 5.3 and < 5.3.05.38.50; >= 5.4 and < 5.4.05.46.50; >= 5.5 and < 5.5.05.54.50; >= 5.6 and < 5.6.05.61.50; or >= 5.7 and < 5.7.05.70.50.
-
Confirm InsydeH2O firmware vendorCheck the system BIOS/UEFI vendor information using 'dmidecode -s bios-vendor' or by viewing the BIOS setup utility splash screen during boot. This vulnerability specifically affects InsydeH2O firmware, not other UEFI implementations.Affected if The vendor is Insyde or the firmware is labeled as InsydeH2O.
-
Determine if VariableRuntimeDxe driver is presentThis driver is part of the UEFI firmware image and is not directly observable from the operating system. The presence of the vulnerability is inferred solely from the firmware version check above, as the driver version is bundled with the firmware version.Affected if Any version matching the affected ranges listed in step 1; the driver is included by default in affected InsydeH2O versions.
-
Verify SMM context availabilityThe vulnerability operates within System Management Mode (SMM). From the OS, verify SMM is enabled by checking 'dmidecode -s bios-version' combined with the system's UEFI/ACPI tables, or use tools such as 'intel-smx' or 'amsat' if available. Note: This is a secondary check since all affected firmware versions have SMM active by default.Affected if SMM is enabled on the system (this is the default state for most InsydeH2O systems).
A system is affected if it runs any InsydeH2O UEFI firmware version within the vulnerable ranges (5.2 to 5.2.05.29.49, 5.3 to 5.3.05.38.49, 5.4 to 5.4.05.46.49, 5.5 to 5.5.05.54.49, 5.6 to 5.6.05.61.49, or 5.7 to 5.7.05.70.49).
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped5.2.05.29.505.3.05.38.505.4.05.46.50
Update InsydeH2O firmware to the patched version specific to the kernel branch in use (05.29.50+, 05.38.50+, 05.46.50+, 05.54.50+, 05.61.50+, or 05.70.50+). This is a firmware-level issue requiring vendor-provided BIOS update.
InsydeH2O kernel 5.2 to >=05.29.50, kernel 5.3 to >=05.38.50, kernel 5.4 to >=05.46.50, kernel 5.5 to >=05.54.50 (or kernel 5.6/5.7 if applicable)
- Identify the InsydeH2O kernel version used by your device (check system firmware/UEFI version)
- Contact your device/system vendor (OEM) to obtain the appropriate firmware update containing the fixed InsydeH2O kernel
- Apply the firmware update provided by the OEM following their specific update instructions
- After update, verify the InsydeH2O kernel version matches or exceeds the fixed version for your kernel branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52877 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52877 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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