Problem Description:
Several vulnerabilities were found in the ocs_fc(4) driver.
The driver's ioctl(2) interface, which members of the operator group
can access, did not require superuser privileges and did not
adequately validate requests. Among other problems, it failed to
bound user-supplied buffer sizes and PCI configuration space offsets,
and could issue adapter commands referencing freed memory.
(CVE-2026-127752)
The driver did not adequately validate the length of FCP command
frames received from initiators, and did not range check exchange
identifiers reported by the adapter, potentially leading to
out-of-bounds memory accesses. (CVE-2026-127753)
When rejecting a Process Login (PRLI) request with an unsupported
FC-4 type, the driver sent a second response for the same exchange,
resulting in a use-after-free. Any port which had completed a Port
Login (PLOGI) could trigger this with a single PRLI. Additionally,
formatting the adapter's active profile ID could overflow a stack
buffer. (CVE-2026-127754)
Impact:
A local user in the operator group can use the ioctl(2) interface
to corrupt kernel memory or reprogram the adapter, potentially
gaining full control of the system. A remote port on the same Fibre
Channel fabric can trigger a use-after-free or out-of-bounds memory
access in the kernel, resulting in a Denial of Service (DoS) or
potentially arbitrary code execution in the kernel.