CVE-2026-97535scsi: qla2xxx: Bound VP index against VP_CTRL IOCB bitmap size
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Bound VP index against VP_CTRL IOCB bitmap size The VP control IOCB selects its target virtual port by setting one bit in vp_idx_map, a fixed 16-byte (128-bit) array in both vp_ctrl_entry_24xx and vp_ctrl_entry_24xx_ext. qla25xx_ctrlvp_iocb() computes map = (vp_index - 1) / 8 and writes vce->vp_idx_map[map] without checking that map stays within the array. max_npiv_vports is taken from firmware and only sanitized to a MIN_MULTI_ID_FABRIC-aligned boundary, so it can legitimately be 191 or 255, and qla24xx_control_vp() only rejects vp_index >= max_npiv_vports. A vp_index above 128 therefore yields map >= 16 and an out-of-bounds write of up to 16 bytes past vp_idx_map, corrupting the trailing IOCB fields (or the adjacent request-ring slot on the 64-byte layout). Reject a vp_index that cannot be represented in the IOCB bitmap in qla24xx_control_vp(), and add a defensive ARRAY_SIZE() guard in qla25xx_ctrlvp_iocb() before the write. Adapters that report the usual 63 or 127 NPIV vports are unaffected.
Timeline
ID reserved
By Linux
- 1 day later
· 1 day later
Published
- 35 days later
· 35 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (12 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < 0c73631101e7889c519d4a621cc958f487f8e01a
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < 674d783f2e80d0d7c1c86bf36dc0a09033e704de
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < c80a0362a0fe548c15a0324b1f61c04b62bb2174
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < 48a44e19746eaa70320a3c2571dcb345192fca72
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < 13354ad251ab009102597a791bc7c4d2265229e1
- affected 2853192e154b813fe34a6cbee5e34dfef50d29d0 – < 878613ecb5a36db26859c4fd83daf9283a334fa2
- affected 4.16
- unaffected < 4.16
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References6
- https://git.kernel.org/stable/c/0c73631101e7889c519d4a621cc958f487f8e01a (opens in a new tab)
- https://git.kernel.org/stable/c/674d783f2e80d0d7c1c86bf36dc0a09033e704de (opens in a new tab)
- https://git.kernel.org/stable/c/c80a0362a0fe548c15a0324b1f61c04b62bb2174 (opens in a new tab)
- https://git.kernel.org/stable/c/48a44e19746eaa70320a3c2571dcb345192fca72 (opens in a new tab)
- https://git.kernel.org/stable/c/13354ad251ab009102597a791bc7c4d2265229e1 (opens in a new tab)
- https://git.kernel.org/stable/c/878613ecb5a36db26859c4fd83daf9283a334fa2 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86843 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97535)Record last updated .