scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.110, 6.18.51, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition qla24xx_report_id_acquisition() format-1 handling drops vport_slock after taking the vport reference and then calls qla_update_host_map() without the lock. That reaches qla_update_vp_map(), which mutates the ha->host_map btree via btree_insert32()/btree_update32()/btree_remove32() and is documented to require vport_slock to be held by the caller. Running it unlocked can race concurrent host_map updates and corrupt the btree. The format-2 path in the same function already wraps its host_map update (SET_AL_PA) in vport_slock; the format-1 path is the lone outlier. Hold vport_slock across the format-1 qla_update_host_map() call to honor the documented locking contract. The vref_count taken in the loop keeps the vport valid, so this only adds the missing host_map serialization.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 430eef03a763e5e76a371ba6d02779ae4a64b6ea · fixed in e8f1b0cb9782338c6341ceed816e9c1243743cdd; From 430eef03a763e5e76a371ba6d02779ae4a64b6ea · fixed in 6ed66e2a67bbd22877008ff9aa64bd574a7fc011; From 430eef03a763e5e76a371ba6d02779ae4a64b6ea · fixed in 776e4e8cbcf155302f430ce9793d1502e3c113a0; From 430eef03a763e5e76a371ba6d02779ae4a64b6ea · fixed in 7d0b3f745efb24c0aac5e06b49b3420bc65d23b9; From 430eef03a763e5e76a371ba6d02779ae4a64b6ea · fixed in 7944039ba9cb5c3a935d17c91004e3b8649ff58e
- Linux Linux
6.3
- KernelLinux
From 6.3.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5