CVE-2026-97529

scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[]

N/A
Published: September 25, 2026 at 10:21 AM UTC
Updated: October 21, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Validate BSG request_len before reading vendor_cmd[] The FC BSG transport allocates job->request via memdup_user() using the exact user-supplied request_len. For FC_BSG_HST_VENDOR, fc_bsg_host_dispatch() only guarantees request_len covers msgcode and vendor_id; it does not account for the vendor_cmd[] flexible array. qla2xxx then reads the command selector vendor_cmd[0] and, in several sub-handlers, vendor_cmd[1]/[2] or structures overlaid on the vendor command area without verifying request_len. A caller holding CAP_SYS_RAWIO can submit a short request whose vendor_id matches the host, triggering out-of-bounds heap reads (KASAN-detectable, and able to mis-select a command or panic). Add a central guard in qla2x00_process_vendor_specific() so the selector is always in bounds, restrict the early vendor_cmd[0] read in qla24xx_bsg_request() to sufficiently long vendor messages, and add request_len checks to the sub-handlers that read further: qla24xx_proc_fcp_prio_cfg_cmd(), qla2x00_process_loopback(), qla84xx_reset(), qla84xx_updatefw(), qla2x00_read_optrom(), qla2x00_update_optrom(), qlafx00_mgmt_cmd() and qla28xx_validate_flash_image().

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

01e0e15c8b3b32e006e5cccac10c8b377ac3d8031e0e15c8b3b32e6e5cccac10c8b377ac3d8034.10
Vendor states this is fixed in 4cf38dd9465736141263ebb63375868311a0ec81 (fixed)
Vendor states this is fixed in 740f3458a4798af54aaf8cf63e797d407e8b6d3b (fixed)
Vendor states this is fixed in ef63922d8bdea03de1804af39a6b12212acb1be2 (fixed)
Vendor states this is fixed in f75bff451a2fac5aed82f9641df1e9a42c5a899d (fixed)
Vendor states this is fixed in 4.10 (unaffected)
Vendor states this is fixed in 6.12.112 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card