dbcve.org
KernelOperating system · Insyde

CVE-2024-52880

HIGH · 7.9 CVSS v3.1 Published 2025-05-15
Fix available
A fix is available. Upgrade to 5.29.50 / 5.38.50 or later.
See remediation →
81/100
Remediation priority · High
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
An 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, SecureBootHandler uses DataSize and VariableNameSize when determining if the data or name are in the buffer, but these are supplied by the caller and therefore cannot be trusted.

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

Buffer boundary validation vulnerability in Insyde InsydeH2O UEFI firmware's VariableRuntimeDxe driver. The SecureBootHandler function uses caller-supplied DataSize and VariableNameSize parameters without validation when checking if data or names fit within buffers, allowing potential out-of-bounds read/write operations.

MitigationApply vendor-provided UEFI firmware updates that address this vulnerability for the specific kernel version in use. The vulnerability is in the firmware itself—no software-only workaround exists.

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
KernelOperating system
Affected:>= 5.2, < 5.29.50>= 5.3, < 5.38.50>= 5.4, < 5.46.50>= 5.5, < 5.54.50>= 5.6, < 5.61.50>= 5.7, < 5.70.50

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
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 checks

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

  1. Identify if system uses InsydeH2O UEFI firmware
    Run 'dmidecode -s bios-version' or check /sys/class/dmi/id/bios_version, and examine the vendor string via 'dmidecode -s bios-vendor' or /sys/class/dmi/id/bios_vendor
    Affected if The BIOS vendor is Insyde or the firmware version string contains InsydeH2O references
  2. Extract the Insyde Kernel version from UEFI firmware
    Parse the UEFI firmware version string - the Insyde Kernel version is typically encoded in the firmware version (for example, version 5.2.x indicates Insyde Kernel 5.2). Use 'dmidecode -s bios-version' output and compare the numeric portion against Insyde version numbering
    Affected if The extracted Insyde Kernel version falls within any of these ranges: >= 5.2 and < 5.29.50; >= 5.3 and < 5.38.50; >= 5.4 and < 5.46.50; >= 5.5 and < 5.54.50; >= 5.6 and < 5.61.50; >= 5.7 and < 5.70.50
  3. Verify SecureBoot is enabled
    Check SecureBoot status by running 'mokutil --sb-state' or 'powershell -command "Confirm-SecureBootUEFI"' on Windows, or check via 'efi-readvar' on Linux
    Affected if SecureBoot is enabled - the vulnerable SecureBootHandler function is invoked when SecureBoot processes variables
  4. Confirm VariableRuntimeDxe driver presence
    Inspect UEFI firmware image or use tools like 'uefi-firmware-parser' or 'chipsec' to extract and examine the VariableRuntimeDxe driver for the SecureBootHandler function
    Affected if The VariableRuntimeDxe driver is present and contains the SecureBootHandler function (this is typically present in InsydeH2O firmware with SecureBoot support)

The system is affected if it runs InsydeH2O UEFI firmware with an Insyde Kernel version matching the affected ranges and has SecureBoot enabled, allowing the vulnerable SecureBootHandler function to be invoked.

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.

dbcve · scoped
Upgrade available Upgrade to 5.29.50 / 5.38.50 / 5.46.50 or later
Fixed in 5.29.505.38.505.46.50
Interim mitigation

Apply vendor-provided UEFI firmware updates that address this vulnerability for the specific kernel version in use. The vulnerability is in the firmware itself—no software-only workaround exists.

Recommended fix High confidence

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

  1. Contact your hardware OEM (Original Equipment Manufacturer) to obtain the firmware update containing the InsydeH2O kernel fix
  2. Apply the firmware update using the vendor's recommended process (typically via BIOS/UEFI update utility or firmware flashing tool)
  3. After updating, verify the InsydeH2O kernel version matches or exceeds the fixed version for your kernel branch (05.29.50 for 5.2, 05.38.50 for 5.3, 05.46.50 for 5.4, or 05.54.50 for 5.5)
Caveat Firmware updates carry a risk of bricking the device if interrupted; ensure stable power and follow vendor instructions exactly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kernel Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52880 — 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-52880 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