CVE-2025-21751
Last modified
CVE-2025-21751 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.21% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | < 6.13.3 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21751?
How severe is CVE-2025-21751?
How do I fix CVE-2025-21751?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-21746In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-21747In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21748In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21749In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2175A vulnerability was found in libzvbi up to 0.2.43. It has be…6.5
- CVE-2025-21750In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21752In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21753In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21754In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21755Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2025-21756In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21757Rejected reason: This CVE ID has been rejected or withdrawn …
Are you affected by CVE-2025-21751?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
