# CVE-2024-52880: Memory corruption in n/a

> Attackers can exploit improper input validation in the SecureBootHandler to cause memory corruption, potentially leading to arbitrary code execution or privilege escalation.

- **Severity:** High 7.9 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-4762-7j7m-8cjh

## What is CVE-2024-52880?

CVE-2024-52880 is a high-severity memory corruption vulnerability in n/a, published on 15 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-52880?

It affects 1 product.


Products: Insyde Kernel.

## How do I fix CVE-2024-52880?

No fix has been published for CVE-2024-52880 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-52880 being exploited?

There is no known exploitation of CVE-2024-52880 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-36337](https://insights.sbomify.com/CVE-2022-36337/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29275](https://insights.sbomify.com/CVE-2022-29275/): Privilege escalation in n/a (high 8.2)
- [CVE-2022-29276](https://insights.sbomify.com/CVE-2022-29276/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29278](https://insights.sbomify.com/CVE-2022-29278/): Memory corruption in n/a (high 8.2)
- [CVE-2022-29279](https://insights.sbomify.com/CVE-2022-29279/): Memory corruption in n/a (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52880 and fix it if it is affected.

What it is: CVE-2024-52880 is a high-severity memory corruption vulnerability in n/a, published on 15 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-52880 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52880/ (Markdown: https://insights.sbomify.com/CVE-2024-52880/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52880
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52880
- OSV: https://osv.dev/vulnerability/CVE-2024-52880

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52880/
Summaries are generated and may contain mistakes; the official description above is the record.