Answer in brief
CVE-2022-48789 records a Critical severity (CVSS 9.8) vulnerability in nvme-tcp: fix possible use-after-free in transport error_recovery work. 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 9.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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <61a26ffd5ad3ece456d74c4c79f7b5e3f440a141 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <e192184cf8bce8dd55d619f5611a2eaba996fa05 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <5e42fca37ccc76f39f73732661bd47254cad5982 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <bb0d8fb35c4ff00a503c2c4dca4cce8d102a21c4 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <ff9fc7ebf5c06de1ef72a69f9b1ab40af8b07f9e | 61a26ffd5ad3ece456d74c4c79f7b5e3f440a141, e192184cf8bce8dd55d619f5611a2eaba996fa05, 5e42fca37ccc76f39f73732661bd47254cad5982, bb0d8fb35c4ff00a503c2c4dca4cce8d102a21c4, ff9fc7ebf5c06de1ef72a69f9b1ab40af8b07f9e |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Jul 16, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix possible use-after-free in transport error_recovery work While nvme_tcp_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2022-48789 records a Critical severity (CVSS 9.8) vulnerability in nvme-tcp: fix possible use-after-free in transport error_recovery work. 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 9.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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <61a26ffd5ad3ece456d74c4c79f7b5e3f440a141 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <e192184cf8bce8dd55d619f5611a2eaba996fa05 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <5e42fca37ccc76f39f73732661bd47254cad5982 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <bb0d8fb35c4ff00a503c2c4dca4cce8d102a21c4 || >=3f2304f8c6d6ed97849057bd16fee99e434ca796 <ff9fc7ebf5c06de1ef72a69f9b1ab40af8b07f9e | 61a26ffd5ad3ece456d74c4c79f7b5e3f440a141, e192184cf8bce8dd55d619f5611a2eaba996fa05, 5e42fca37ccc76f39f73732661bd47254cad5982, bb0d8fb35c4ff00a503c2c4dca4cce8d102a21c4, ff9fc7ebf5c06de1ef72a69f9b1ab40af8b07f9e |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Jul 16, 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 4, 2026
In the Linux kernel, the following vulnerability has been resolved: nvme-tcp: fix possible use-after-free in transport error_recovery work While nvme_tcp_submit_async_event_work is checking the ctrl and queue state before preparing the AER command and scheduling io_work, in order to fully prevent a race where this check is not reliable the error recovery work must flush async_event_work before continuing to destroy the admin queue after setting the ctrl state to RESETTING such that there is no race .submit_async_event and the error recovery handler itself changing the ctrl state.
Quoted source text, attributed separately from HOL analysis.