scsi: qla2xxx: Skip vport under deletion in report ID acquisition
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel d61e8de98c5a52978fb1edd95fe4dde3131b280e, Kernel 20bb54601d2655e83795b73499c89f6b1cb31016, Kernel 23582731afa35031c94fadb71a4f3b4afd094649 and 8 more.
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Skip vport under deletion in report ID acquisition qla24xx_report_id_acquisition() format-1 handling walks ha->vp_list under vport_slock, takes a vref_count on the matching vport and calls qla_update_host_map() to register its port id. A vport teardown via qla24xx_vport_delete() sets VPORT_DELETE, then qla24xx_disable_vp() removes the vport from the host_map btree and zeroes vha->d_id (RESET_AL_PA). The vport is only unlinked from vp_list later, in qla24xx_deallocate_vp_id(), which clears vp_map[idx] (RESET_VP_IDX) but does not touch host_map. In the window in between, report ID acquisition can still find the vport on vp_list and call qla_update_host_map(); with d_id already zeroed it takes the btree_insert32() path and re-inserts the dying vport into host_map. Nothing cleans that entry afterwards, so once scsi_host_put() frees the vha a later host_map lookup dereferences freed memory. Skip a vport that has VPORT_DELETE set before taking the reference, so it is neither re-registered nor scheduled for DPC re-registration. This mirrors the existing guard in qla2x00_alert_all_vps().
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=41dc529a4602ac737020f423f84686a81de38e6d <d61e8de98c5a52978fb1edd95fe4dde3131b280e, >=41dc529a4602ac737020f423f84686a81de38e6d <20bb54601d2655e83795b73499c89f6b1cb31016, >=41dc529a4602ac737020f423f84686a81de38e6d <23582731afa35031c94fadb71a4f3b4afd094649, >=41dc529a4602ac737020f423f84686a81de38e6d <40dcd4a71a52414b47fbba2f956387f1077c6c15, >=41dc529a4602ac737020f423f84686a81de38e6d <7a83979d92782f83c90888ebe19bdc9420521940, >=41dc529a4602ac737020f423f84686a81de38e6d <d3ac7e0f454c7d52c0c2e5ecaf5a3d938f1b166d, =4.11 | d61e8de98c5a52978fb1edd95fe4dde3131b280e, 20bb54601d2655e83795b73499c89f6b1cb31016, 23582731afa35031c94fadb71a4f3b4afd094649, 40dcd4a71a52414b47fbba2f956387f1077c6c15, 7a83979d92782f83c90888ebe19bdc9420521940, d3ac7e0f454c7d52c0c2e5ecaf5a3d938f1b166d |
| linux-kernel: Kernel | >=6.13.0 <6.18.53, >=6.19.0 <7.2.7, >=6.2.0 <6.6.160, >=6.7.0 <6.12.112, >=4.11.0 <6.1.191 | 6.18.53, 7.2.7, 6.6.160, 6.12.112, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket