# CVE-2026-90112: net: qlcnic: validate unified ROM sections before loading

> A local attacker can trigger integer overflows in the qlcnic driver ROM parser, causing out-of-bounds reads and potential system crashes or information leaks.

- **Severity:** Not scored
- **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:** 21 Oct 2026
- **Also known as:** AZL-102842, BELL-CVE-2026-90112, DEBIAN-CVE-2026-90112, GHSA-8m8v-32h4-xj63, UBUNTU-CVE-2026-90112

## What is CVE-2026-90112?

CVE-2026-90112 is a 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:

net: qlcnic: validate unified ROM sections before loading

The unified ROM parser reads directory, product, and data-descriptor fields
from the firmware file.  Existing validation forms table and data ends with
unchecked additions and multiplications.  Malformed values can wrap before
they are compared with the firmware size.  The parser also dereferences
typed pointers at firmware-controlled offsets.

Valid descriptor extents alone are insufficient for the consumers.  The
loader reads a fixed-size bootloader regardless of its declared size, the
version parser assumes a 17-byte tail, and a partial final firmware word is
read as a full u64.  A truncated image can therefore make the driver read
beyond the firmware allocation during validation or loading.

Replace the pointer-returning parser with bounded range helpers.  Validate
table entry sizes, descriptor indices, section ranges, the fixed
bootloader load length, and the version tail before exposing any section.
Read all file fields with unaligned little-endian accessors and assemble a
partial final word from only the bytes that remain.  Apply the same range
checks to the legacy image before reading its fixed fields.

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


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

Apply the vendor's patch.

## Is CVE-2026-90112 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90112 is a 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-90112 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-90112/ (Markdown: https://insights.sbomify.com/CVE-2026-90112/index.md)
```

## Sources

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

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