Answer in brief
CVE-2023-54100 records a High severity (CVSS 7.8) vulnerability in scsi: qedi: Fix use after free bug in qedi_remove(). 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.
CVSS is 7.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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <fa19c533ab19161298f0780bcc6523af88f6fd20 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <5e756a59cee6a8a79b9059c5bdf0ecbf5bb8d151 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <3738a230831e861503119ee2691c4a7dc56ed60a || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <89f6023fc321c958a0fb11f143a6eb4544ae3940 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <124027cd1a624ce0347adcd59241a9966a726b22 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <c5749639f2d0a1f6cbe187d05f70c2e7c544d748 | fa19c533ab19161298f0780bcc6523af88f6fd20, 5e756a59cee6a8a79b9059c5bdf0ecbf5bb8d151, 3738a230831e861503119ee2691c4a7dc56ed60a, 89f6023fc321c958a0fb11f143a6eb4544ae3940, 124027cd1a624ce0347adcd59241a9966a726b22, c5749639f2d0a1f6cbe187d05f70c2e7c544d748 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 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: qedi: Fix use after free bug in qedi_remove() In qedi_probe() we call __qedi_probe() which initializes &qedi->recovery_work with qedi_recovery_handler() and &qedi->board_disable_work with qedi_board_disable_work(). When qedi_schedule_recovery_handler() is called, schedule_delayed_work() will finally start the work. In qedi_remove(), which is called to remove the driver, the following sequence may be observed: Fix this by finishing the work before cleanup in qedi_remove(). CPU0 CPU1 |qedi_recovery_handler qedi_remove | __qedi_remove | iscsi_host_free | scsi_host_put | //free shost | |iscsi_host_for_each_session |//use qedi->shost Cancel recovery_work and board_disable_work in __qedi_remove().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-54100 records a High severity (CVSS 7.8) vulnerability in scsi: qedi: Fix use after free bug in qedi_remove(). 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.
CVSS is 7.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). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <fa19c533ab19161298f0780bcc6523af88f6fd20 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <5e756a59cee6a8a79b9059c5bdf0ecbf5bb8d151 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <3738a230831e861503119ee2691c4a7dc56ed60a || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <89f6023fc321c958a0fb11f143a6eb4544ae3940 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <124027cd1a624ce0347adcd59241a9966a726b22 || >=4b1068f5d74b6cc92319bd7eba40809b1222e73f <c5749639f2d0a1f6cbe187d05f70c2e7c544d748 | fa19c533ab19161298f0780bcc6523af88f6fd20, 5e756a59cee6a8a79b9059c5bdf0ecbf5bb8d151, 3738a230831e861503119ee2691c4a7dc56ed60a, 89f6023fc321c958a0fb11f143a6eb4544ae3940, 124027cd1a624ce0347adcd59241a9966a726b22, c5749639f2d0a1f6cbe187d05f70c2e7c544d748 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 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: qedi: Fix use after free bug in qedi_remove() In qedi_probe() we call __qedi_probe() which initializes &qedi->recovery_work with qedi_recovery_handler() and &qedi->board_disable_work with qedi_board_disable_work(). When qedi_schedule_recovery_handler() is called, schedule_delayed_work() will finally start the work. In qedi_remove(), which is called to remove the driver, the following sequence may be observed: Fix this by finishing the work before cleanup in qedi_remove(). CPU0 CPU1 |qedi_recovery_handler qedi_remove | __qedi_remove | iscsi_host_free | scsi_host_put | //free shost | |iscsi_host_for_each_session |//use qedi->shost Cancel recovery_work and board_disable_work in __qedi_remove().
Quoted source text, attributed separately from HOL analysis.