Answer in brief
CVE-2025-21751 records a High severity (CVSS 7.8) vulnerability in net/mlx5: HWS, change error flow on matcher disconnect. 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 | >=472dd792348f6601ccaa97d5626ee4faff891901 <5682aad0276ff9b9b0eff3188eb6a1f504d6b436 || >=472dd792348f6601ccaa97d5626ee4faff891901 <23a86c76a1a197e8fbbbd0ce3e826eb58c471624 || >=472dd792348f6601ccaa97d5626ee4faff891901 <1ce840c7a659aa53a31ef49f0271b4fd0dc10296 | 5682aad0276ff9b9b0eff3188eb6a1f504d6b436, 23a86c76a1a197e8fbbbd0ce3e826eb58c471624, 1ce840c7a659aa53a31ef49f0271b4fd0dc10296 |
| Linux/Linuxgeneric | 6.12 | Not reported |
Published upstream
Feb 27, 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: net/mlx5: HWS, change error flow on matcher disconnect Currently, when firmware failure occurs during matcher disconnect flow, the error flow of the function reconnects the matcher back and returns an error, which continues running the calling function and eventually frees the matcher that is being disconnected. This leads to a case where we have a freed matcher on the matchers list, which in turn leads to use-after-free and eventual crash. This patch fixes that by not trying to reconnect the matcher back when some FW command fails during disconnect. Note that we're dealing here with FW error. We can't overcome this problem. This might lead to bad steering state (e.g. wrong connection between matchers), and will also lead to resource leakage, as it is the case with any other error handling during resource destruction. However, the goal here is to allow the driver to continue and not crash the machine with use-after-free error.
Quoted source text, attributed separately from HOL analysis.