Answer in brief
CVE-2023-54201 records a Unknown severity vulnerability in RDMA/efa: Fix wrong resources deallocation order. 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 | >=ff6629f88c529b07d9704c656c64dae76910e3e9 <cf38960386f3cc4abf395e556af915e4babcafd2 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <e79db2f51a564fd4daa3e508b987df5e81c34b20 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <24f9884971f9b34915b67baacf7350a3f6f19ea4 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <dc202c57e9a1423aed528e4b8dc949509cd32191 | cf38960386f3cc4abf395e556af915e4babcafd2, e79db2f51a564fd4daa3e508b987df5e81c34b20, 24f9884971f9b34915b67baacf7350a3f6f19ea4, dc202c57e9a1423aed528e4b8dc949509cd32191 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Dec 30, 2025
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: RDMA/efa: Fix wrong resources deallocation order When trying to destroy QP or CQ, we first decrease the refcount and potentially free memory regions allocated for the object and then request the device to destroy the object. If the device fails, the object isn't fully destroyed so the user/IB core can try to destroy the object again which will lead to underflow when trying to decrease an already zeroed refcount. Deallocate resources in reverse order of allocating them to safely free them.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-54201 records a Unknown severity vulnerability in RDMA/efa: Fix wrong resources deallocation order. 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 | >=ff6629f88c529b07d9704c656c64dae76910e3e9 <cf38960386f3cc4abf395e556af915e4babcafd2 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <e79db2f51a564fd4daa3e508b987df5e81c34b20 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <24f9884971f9b34915b67baacf7350a3f6f19ea4 || >=ff6629f88c529b07d9704c656c64dae76910e3e9 <dc202c57e9a1423aed528e4b8dc949509cd32191 | cf38960386f3cc4abf395e556af915e4babcafd2, e79db2f51a564fd4daa3e508b987df5e81c34b20, 24f9884971f9b34915b67baacf7350a3f6f19ea4, dc202c57e9a1423aed528e4b8dc949509cd32191 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Dec 30, 2025
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: RDMA/efa: Fix wrong resources deallocation order When trying to destroy QP or CQ, we first decrease the refcount and potentially free memory regions allocated for the object and then request the device to destroy the object. If the device fails, the object isn't fully destroyed so the user/IB core can try to destroy the object again which will lead to underflow when trying to decrease an already zeroed refcount. Deallocate resources in reverse order of allocating them to safely free them.
Quoted source text, attributed separately from HOL analysis.