CVE-2026-97529
Last modified
CVE-2026-97529 is a vulnerability of currently unknown severity. 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.
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 Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 01e0e15c8b3b32e006e5cccac10c8b377ac3d803, < 740f3458a4798af54aaf8cf63e797d407e8b6d3b; >= 01e0e15c8b3b32e006e5cccac10c8b377ac3d803, < f75bff451a2fac5aed82f9641df1e9a42c5a899d; >= 01e0e15c8b3b32e006e5cccac10c8b377ac3d803, < 4cf38dd9465736141263ebb63375868311a0ec81 |
| Linux | Linux | 4.10 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-97529?
How severe is CVE-2026-97529?
How do I fix CVE-2026-97529?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-97523In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97524In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97525In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97526In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97527In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97528In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9753The $_internalApplyOplogUpdate aggregation pipeline stage ca…8.1
- CVE-2026-97530In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97531In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97532In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97533In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97534In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-97529?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
