Answer in brief
CVE-2023-54238 records a Unknown severity vulnerability in mlx5: fix skb leak while fifo resync and push. 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 | >=58a518948f60153e8f6cb8361d2712aa3a1af94a <234cffda95e1049f58e8ec136ef105c633f0ed19 || >=58a518948f60153e8f6cb8361d2712aa3a1af94a <68504c66d08c70fb92799722e25a932d311d74fd || >=58a518948f60153e8f6cb8361d2712aa3a1af94a <e435941b1da1a0be4ff8a7ae425774c76a5ac514 | 234cffda95e1049f58e8ec136ef105c633f0ed19, 68504c66d08c70fb92799722e25a932d311d74fd, e435941b1da1a0be4ff8a7ae425774c76a5ac514 |
| Linux/Linuxgeneric | 6.0 | 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: mlx5: fix skb leak while fifo resync and push During ptp resync operation SKBs were poped from the fifo but were never freed neither by napi_consume nor by dev_kfree_skb_any. Add call to napi_consume_skb to properly free SKBs. Another leak was happening because mlx5e_skb_fifo_has_room() had an error in the check. Comparing free running counters works well unless C promotes the types to something wider than the counter. In this case counters are u16 but the result of the substraction is promouted to int and it causes wrong result (negative value) of the check when producer have already overlapped but consumer haven't yet. Explicit cast to u16 fixes the issue.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-54238 records a Unknown severity vulnerability in mlx5: fix skb leak while fifo resync and push. 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 | >=58a518948f60153e8f6cb8361d2712aa3a1af94a <234cffda95e1049f58e8ec136ef105c633f0ed19 || >=58a518948f60153e8f6cb8361d2712aa3a1af94a <68504c66d08c70fb92799722e25a932d311d74fd || >=58a518948f60153e8f6cb8361d2712aa3a1af94a <e435941b1da1a0be4ff8a7ae425774c76a5ac514 | 234cffda95e1049f58e8ec136ef105c633f0ed19, 68504c66d08c70fb92799722e25a932d311d74fd, e435941b1da1a0be4ff8a7ae425774c76a5ac514 |
| Linux/Linuxgeneric | 6.0 | 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: mlx5: fix skb leak while fifo resync and push During ptp resync operation SKBs were poped from the fifo but were never freed neither by napi_consume nor by dev_kfree_skb_any. Add call to napi_consume_skb to properly free SKBs. Another leak was happening because mlx5e_skb_fifo_has_room() had an error in the check. Comparing free running counters works well unless C promotes the types to something wider than the counter. In this case counters are u16 but the result of the substraction is promouted to int and it causes wrong result (negative value) of the check when producer have already overlapped but consumer haven't yet. Explicit cast to u16 fixes the issue.
Quoted source text, attributed separately from HOL analysis.