Answer in brief
CVE-2024-26845 records a Unknown severity vulnerability in scsi: target: core: Add TMF to tmr_list handling. The current sources do not mark it as known exploited. The current feed maps 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.
Answer in brief
CVE-2024-26845 records a Unknown severity vulnerability in scsi: target: core: Add TMF to tmr_list handling. The current sources do not mark it as known exploited. The current feed maps 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.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2281c95fe751325874d135b237ecdcd3bc34cc26 <11f3fe5001ed05721e641f0ecaa7a73b7deb245d || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <168ed59170de1fd7274080fe102216162d6826cf || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <a9849b67b4402a12eb35eadc9306c1ef9847d53d || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <e717bd412001495f17400bfc09f606f1b594ef5a || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <36bc5040c863b44af06094b22f1e50059227b9cb || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <bd508f96b5fef96d8a0ce9cbb211d82bcfc2341f || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <83ab68168a3d990d5ff39ab030ad5754cbbccb25 | 11f3fe5001ed05721e641f0ecaa7a73b7deb245d, 168ed59170de1fd7274080fe102216162d6826cf, a9849b67b4402a12eb35eadc9306c1ef9847d53d, e717bd412001495f17400bfc09f606f1b594ef5a, 36bc5040c863b44af06094b22f1e50059227b9cb, bd508f96b5fef96d8a0ce9cbb211d82bcfc2341f, 83ab68168a3d990d5ff39ab030ad5754cbbccb25 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Apr 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Add TMF to tmr_list handling An abort that is responded to by iSCSI itself is added to tmr_list but does not go to target core. A LUN_RESET that goes through tmr_list takes a refcounter on the abort and waits for completion. However, the abort will be never complete because it was not started in target core. Unable to locate ITT: 0x05000000 on CID: 0 Unable to locate RefTaskTag: 0x05000000 on CID: 0. wait_for_tasks: Stopping tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop wait for tasks: tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop ... INFO: task kworker/0:2:49 blocked for more than 491 seconds. task:kworker/0:2 state:D stack: 0 pid: 49 ppid: 2 flags:0x00000800 Workqueue: events target_tmr_work [target_core_mod] Call Trace: __switch_to+0x2c4/0x470 _schedule+0x314/0x1730 schedule+0x64/0x130 schedule_timeout+0x168/0x430 wait_for_completion+0x140/0x270 target_put_cmd_and_wait+0x64/0xb0 [target_core_mod] core_tmr_lun_reset+0x30/0xa0 [target_core_mod] target_tmr_work+0xc8/0x1b0 [target_core_mod] process_one_work+0x2d4/0x5d0 worker_thread+0x78/0x6c0 To fix this, only add abort to tmr_list if it will be handled by target core.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2281c95fe751325874d135b237ecdcd3bc34cc26 <11f3fe5001ed05721e641f0ecaa7a73b7deb245d || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <168ed59170de1fd7274080fe102216162d6826cf || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <a9849b67b4402a12eb35eadc9306c1ef9847d53d || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <e717bd412001495f17400bfc09f606f1b594ef5a || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <36bc5040c863b44af06094b22f1e50059227b9cb || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <bd508f96b5fef96d8a0ce9cbb211d82bcfc2341f || >=2281c95fe751325874d135b237ecdcd3bc34cc26 <83ab68168a3d990d5ff39ab030ad5754cbbccb25 | 11f3fe5001ed05721e641f0ecaa7a73b7deb245d, 168ed59170de1fd7274080fe102216162d6826cf, a9849b67b4402a12eb35eadc9306c1ef9847d53d, e717bd412001495f17400bfc09f606f1b594ef5a, 36bc5040c863b44af06094b22f1e50059227b9cb, bd508f96b5fef96d8a0ce9cbb211d82bcfc2341f, 83ab68168a3d990d5ff39ab030ad5754cbbccb25 |
| Linux/Linuxgeneric | 5.1 | Not reported |
Published upstream
Apr 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Add TMF to tmr_list handling An abort that is responded to by iSCSI itself is added to tmr_list but does not go to target core. A LUN_RESET that goes through tmr_list takes a refcounter on the abort and waits for completion. However, the abort will be never complete because it was not started in target core. Unable to locate ITT: 0x05000000 on CID: 0 Unable to locate RefTaskTag: 0x05000000 on CID: 0. wait_for_tasks: Stopping tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop wait for tasks: tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_stop ... INFO: task kworker/0:2:49 blocked for more than 491 seconds. task:kworker/0:2 state:D stack: 0 pid: 49 ppid: 2 flags:0x00000800 Workqueue: events target_tmr_work [target_core_mod] Call Trace: __switch_to+0x2c4/0x470 _schedule+0x314/0x1730 schedule+0x64/0x130 schedule_timeout+0x168/0x430 wait_for_completion+0x140/0x270 target_put_cmd_and_wait+0x64/0xb0 [target_core_mod] core_tmr_lun_reset+0x30/0xa0 [target_core_mod] target_tmr_work+0xc8/0x1b0 [target_core_mod] process_one_work+0x2d4/0x5d0 worker_thread+0x78/0x6c0 To fix this, only add abort to tmr_list if it will be handled by target core.
Quoted source text, attributed separately from HOL analysis.