Answer in brief
CVE-2022-49159 records a High severity (CVSS 8.8) vulnerability in scsi: qla2xxx: Implement ref count for SRB. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7ebb336e45ef1ce23462c3bbd03779929008901f <e17111dd2fda81c35f309b1e5b6ab35809a375e7 || >=7ebb336e45ef1ce23462c3bbd03779929008901f <e140723f78ff418c8df7d990e102e07b65c87d4a || >=7ebb336e45ef1ce23462c3bbd03779929008901f <ceda7f794f3dfe272491e93e3e93049f8be5f07b || >=7ebb336e45ef1ce23462c3bbd03779929008901f <31e6cdbe0eae37badceb5e0d4f06cf051432fd77 | e17111dd2fda81c35f309b1e5b6ab35809a375e7, e140723f78ff418c8df7d990e102e07b65c87d4a, ceda7f794f3dfe272491e93e3e93049f8be5f07b, 31e6cdbe0eae37badceb5e0d4f06cf051432fd77 |
| Linux/Linuxgeneric | 5.15 | Not reported |
| Linux/Linuxgeneric | >=ac280b670e6d6666667aba02324e2fc50bd96ae7 <e17111dd2fda81c35f309b1e5b6ab35809a375e7 || >=ac280b670e6d6666667aba02324e2fc50bd96ae7 <e140723f78ff418c8df7d990e102e07b65c87d4a || >=ac280b670e6d6666667aba02324e2fc50bd96ae7 <ceda7f794f3dfe272491e93e3e93049f8be5f07b || >=ac280b670e6d6666667aba02324e2fc50bd96ae7 <31e6cdbe0eae37badceb5e0d4f06cf051432fd77 | e17111dd2fda81c35f309b1e5b6ab35809a375e7, e140723f78ff418c8df7d990e102e07b65c87d4a, ceda7f794f3dfe272491e93e3e93049f8be5f07b, 31e6cdbe0eae37badceb5e0d4f06cf051432fd77 |
| Linux/Linuxgeneric | 2.6.32 | Not reported |
Published upstream
Feb 26, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Implement ref count for SRB The timeout handler and the done function are racing. When qla2x00_async_iocb_timeout() starts to run it can be preempted by the normal response path (via the firmware?). qla24xx_async_gpsc_sp_done() releases the SRB unconditionally. When scheduling back to qla2x00_async_iocb_timeout() qla24xx_async_abort_cmd() will access an freed sp->qpair pointer: qla2xxx [0000:83:00.0]-2871:0: Async-gpsc timeout - hdl=63d portid=234500 50:06:0e:80:08:77:b6:21. qla2xxx [0000:83:00.0]-2853:0: Async done-gpsc res 0, WWPN 50:06:0e:80:08:77:b6:21 qla2xxx [0000:83:00.0]-2854:0: Async-gpsc OUT WWPN 20:45:00:27:f8:75:33:00 speeds=2c00 speed=0400. qla2xxx [0000:83:00.0]-28d8:0: qla24xx_handle_gpsc_event 50:06:0e:80:08:77:b6:21 DS 7 LS 6 rc 0 login 1|1 rscn 1|0 lid 5 BUG: unable to handle kernel NULL pointer dereference at 0000000000000004 IP: qla24xx_async_abort_cmd+0x1b/0x1c0 [qla2xxx] Obvious solution to this is to introduce a reference counter. One reference is taken for the normal code path (the 'good' case) and one for the timeout path. As we always race between the normal good case and the timeout/abort handler we need to serialize it. Also we cannot assume any order between the handlers. Since this is slow path we can use proper synchronization via locks. When we are able to cancel a timer (del_timer returns 1) we know there can't be any error handling in progress because the timeout handler hasn't expired yet, thus we can safely decrement the refcounter by one. If we are not able to cancel the timer, we know an abort handler is running. We have to make sure we call sp->done() in the abort handlers before calling kref_put().
Quoted source text, attributed separately from HOL analysis.