# CVE-2022-27540: Race condition in HP PC BIOS

> A TOCTOU race condition in HP PC BIOS allows attackers to execute arbitrary code, cause denial of service, or disclose information.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-gfx2-f362-7f24

## What is CVE-2022-27540?

CVE-2022-27540 is a high-severity vulnerability in HP PC BIOS, published on 28 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A potential Time-of-Check to Time-of Use (TOCTOU) vulnerability has been identified in the HP BIOS for certain HP PC products, which might allow arbitrary code execution, denial of service, and information disclosure. HP is releasing BIOS updates to mitigate the potential vulnerability.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2022-27540?

It affects 353 products.


Products: Hp Dragonfly Folio 13.5 Inch G3 2-in-1 Notebook Pc Firmware, Hp Elite Dragonfly 13.5 Inch G3 Notebook Pc Firmware, Hp Elite Dragonfly Firmware, Hp Elite Dragonfly G2 Firmware, Hp Elite Dragonfly Max Firmware, Hp Elite Mini 600 G9 Desktop Pc Firmware, Hp Elite Mini 800 G9 Desktop Pc Firmware, Hp Elite Mt645 G7 Mobile Thin Client Firmware, Hp Elite Sff 600 G9 Desktop Pc Firmware, Hp Elite Sff 800 G9 Desktop Pc Firmware, Hp Elite Slice G2 - Audio Ready With Zoom Rooms Firmware, Hp Elite Slice G2 - Partner Ready With Microsoft Teams Rooms Firmware, Hp Elite Slice G2 With Intel Unite Firmware, Hp Elite Slice G2 With Microsoft Teams Rooms Firmware, Hp Elite Slice G2 With Zoom Rooms Firmware, Hp Elite Tower 600 G9 Desktop Pc Firmware, Hp Elite Tower 680 G9 Desktop Pc Firmware, Hp Elite Tower 800 G9 Desktop Pc Firmware, Hp Elite Tower 880 G9 Desktop Pc Firmware, Hp Elite X2 1012 G1 Firmware and 333 more.

## How do I fix CVE-2022-27540?

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

## Is CVE-2022-27540 being exploited?

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

## Other vulnerabilities in HP PC BIOS

- [CVE-2022-31635](https://insights.sbomify.com/CVE-2022-31635/): Race condition in HP PC BIOS (high 7.8)
- [CVE-2022-31636](https://insights.sbomify.com/CVE-2022-31636/): Race condition in HP PC BIOS (high 7.8)
- [CVE-2022-31637](https://insights.sbomify.com/CVE-2022-31637/): Race condition in HP PC BIOS (high 7.8)
- [CVE-2022-31638](https://insights.sbomify.com/CVE-2022-31638/): Race condition in HP PC BIOS (high 7.8)
- [CVE-2022-31639](https://insights.sbomify.com/CVE-2022-31639/): Race condition in HP PC BIOS (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27540 and fix it if it is affected.

What it is: CVE-2022-27540 is a high-severity vulnerability in HP PC BIOS, published on 28 Jun 2024. 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-2022-27540 in the wild and no public exploit code.

Affected product: HP PC BIOS. 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-2022-27540/ (Markdown: https://insights.sbomify.com/CVE-2022-27540/index.md)
```

## Sources

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

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