# CVE-2026-90137: platform/x86: hp-bioscfg: fix password encoding bounds check

> A missing bounds check in the HP BIOS configuration driver allows reading out-of-bounds memory, potentially causing information disclosure or system crashes.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102794, BELL-CVE-2026-90137, DEBIAN-CVE-2026-90137, GHSA-4794-7h5r-v2rf, UBUNTU-CVE-2026-90137

## What is CVE-2026-90137?

CVE-2026-90137 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: hp-bioscfg: fix password encoding bounds check

The password PSWD_ENCODINGS parser reads password_obj[elem + pos_values]
while copying the supported password encodings from the ACPI package.

The outer loop only guarantees that elem is within password_obj_count.
The encoding count is bounded by MAX_ENCODINGS_SIZE, but that does not
guarantee that the ACPI package contains enough entries for all
elem + pos_values accesses.

A malformed package can therefore declare a non-zero encoding count
without providing enough string objects, causing the parser to read past
the ACPI package array and pass an out-of-bounds string pointer and
length to hp_convert_hexstr_to_str().

Add the same computed-index bounds check used by the other offset-based
package parsing loops before reading password_obj[elem + pos_values].

## Which versions are affected by CVE-2026-90137?


## How do I fix CVE-2026-90137?

Apply the vendor's patch.

## Is CVE-2026-90137 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90137 and fix it if it is affected.

What it is: CVE-2026-90137 is a high-severity memory corruption vulnerability in Linux, published on 17 Sep 2026. 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-2026-90137 in the wild and no public exploit code.

Affected product: Linux. 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-2026-90137/ (Markdown: https://insights.sbomify.com/CVE-2026-90137/index.md)
```

## Sources

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

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