CVE-2026-90112: net: qlcnic: validate unified ROM sections before loading
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.
Affected Software
Event History
Frequently Asked Questions
What systems are exposed to this issue?
Systems running the Linux kernel with the qlcnic network driver are exposed when that driver parses a unified ROM firmware image. The issue is triggered by a malformed or truncated firmware file.
What does an attacker need to exploit it?
An attacker needs to cause the qlcnic driver to load a crafted unified ROM image containing malformed offsets, sizes, descriptor fields, or truncated sections. The provided information does not establish whether this can be done by an unprivileged local user or remotely.
How can I tell whether a firmware image is suspicious?
Suspicious images include those with section ranges, table entry sizes, or descriptor indices that exceed the firmware file bounds, as well as images whose bootloader section is shorter than the fixed load length or whose version data lacks the expected 17-byte tail. Truncated images with a partial final firmware word are also relevant.
What is the mitigation if an update cannot be applied immediately?
Avoid loading untrusted, malformed, or truncated unified ROM firmware files through the qlcnic driver. Restrict control of firmware files and firmware update or loading workflows to trusted administrators and sources.