Answer in brief
CVE-2021-47378 records a Unknown severity vulnerability in nvme-rdma: destroy cm id before destroy qp to avoid use after free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (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), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7110230719602852481c2793d054f866b2bf4a2b <ecf0dc5a904830c926a64feffd8e01141f89822f || >=7110230719602852481c2793d054f866b2bf4a2b <d268a182c56e8361e19fb781137411643312b994 || >=7110230719602852481c2793d054f866b2bf4a2b <9817d763dbe15327b9b3ff4404fa6f27f927e744 | ecf0dc5a904830c926a64feffd8e01141f89822f, d268a182c56e8361e19fb781137411643312b994, 9817d763dbe15327b9b3ff4404fa6f27f927e744 |
| Linux/Linuxgeneric | 4.8 | Not reported |
| linux/linux_kernelgeneric | 1da177e4c3f4 | Not reported |
Published upstream
May 21, 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: nvme-rdma: destroy cm id before destroy qp to avoid use after free We should always destroy cm_id before destroy qp to avoid to get cma event after qp was destroyed, which may lead to use after free. In RDMA connection establishment error flow, don't destroy qp in cm event handler.Just report cm_error to upper level, qp will be destroy in nvme_rdma_alloc_queue() after destroy cm id.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2021-47378 records a Unknown severity vulnerability in nvme-rdma: destroy cm id before destroy qp to avoid use after free. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (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), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7110230719602852481c2793d054f866b2bf4a2b <ecf0dc5a904830c926a64feffd8e01141f89822f || >=7110230719602852481c2793d054f866b2bf4a2b <d268a182c56e8361e19fb781137411643312b994 || >=7110230719602852481c2793d054f866b2bf4a2b <9817d763dbe15327b9b3ff4404fa6f27f927e744 | ecf0dc5a904830c926a64feffd8e01141f89822f, d268a182c56e8361e19fb781137411643312b994, 9817d763dbe15327b9b3ff4404fa6f27f927e744 |
| Linux/Linuxgeneric | 4.8 | Not reported |
| linux/linux_kernelgeneric | 1da177e4c3f4 | Not reported |
Published upstream
May 21, 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: nvme-rdma: destroy cm id before destroy qp to avoid use after free We should always destroy cm_id before destroy qp to avoid to get cma event after qp was destroyed, which may lead to use after free. In RDMA connection establishment error flow, don't destroy qp in cm event handler.Just report cm_error to upper level, qp will be destroy in nvme_rdma_alloc_queue() after destroy cm id.
Quoted source text, attributed separately from HOL analysis.