In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Clean up only new IRQ glue on request_irq() failure The… (CVE-2025-40250)
A vulnerability in the Linux kernel's mlx5 driver was resolved that caused improper cleanup on request_irq() failure. The mlx5_irq_alloc() function could free the entire IRQ mapping (rmap) instead of just the failed allocation, leading to crashes when other threads accessed freed mappings. This issue occurs when IRQ vectors are exhausted and affects configurations with both fwctl and rds enabled. The fix ensures only the newly added IRQ mapping is removed on failure, preventing unintended removal of valid mappings and system crashes.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2025-40250 involves the mlx5_irq_alloc() function in the mlx5 driver. When request_irq() fails due to exhausted IRQ vectors, the function incorrectly frees the entire IRQ mapping (rmap) instead of only the new IRQ glue associated with the failed allocation. This improper cleanup can cause a general protection fault and kernel crash when other threads access the freed mappings. The issue is triggered in environments where both fwctl and rds configurations are enabled. The patch modifies the cleanup logic to precisely remove only the failed IRQ allocation's glue object, preventing crashes and ensuring system stability.
Potential Impact
This vulnerability can cause a kernel crash (general protection fault) due to improper freeing of IRQ mappings when IRQ vector allocation fails. This can lead to denial of service on affected systems running the vulnerable mlx5 driver with specific configurations (fwctl and rds enabled). The impact includes potential system instability and interruption of network or InfiniBand functionality relying on the mlx5 driver.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel to correct the cleanup behavior in mlx5_irq_alloc(). Users should apply the official kernel updates that include this patch to resolve the issue. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the current remediation guidance and apply the update accordingly.
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Clean up only new IRQ glue on request_irq() failure The… (CVE-2025-40250)
Description
A vulnerability in the Linux kernel's mlx5 driver was resolved that caused improper cleanup on request_irq() failure. The mlx5_irq_alloc() function could free the entire IRQ mapping (rmap) instead of just the failed allocation, leading to crashes when other threads accessed freed mappings. This issue occurs when IRQ vectors are exhausted and affects configurations with both fwctl and rds enabled. The fix ensures only the newly added IRQ mapping is removed on failure, preventing unintended removal of valid mappings and system crashes.
CVSS v3.1
Score 7.8high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2025-40250 involves the mlx5_irq_alloc() function in the mlx5 driver. When request_irq() fails due to exhausted IRQ vectors, the function incorrectly frees the entire IRQ mapping (rmap) instead of only the new IRQ glue associated with the failed allocation. This improper cleanup can cause a general protection fault and kernel crash when other threads access the freed mappings. The issue is triggered in environments where both fwctl and rds configurations are enabled. The patch modifies the cleanup logic to precisely remove only the failed IRQ allocation's glue object, preventing crashes and ensuring system stability.
Potential Impact
This vulnerability can cause a kernel crash (general protection fault) due to improper freeing of IRQ mappings when IRQ vector allocation fails. This can lead to denial of service on affected systems running the vulnerable mlx5 driver with specific configurations (fwctl and rds enabled). The impact includes potential system instability and interruption of network or InfiniBand functionality relying on the mlx5 driver.
Mitigation Recommendations
A fix for this vulnerability has been implemented in the Linux kernel to correct the cleanup behavior in mlx5_irq_alloc(). Users should apply the official kernel updates that include this patch to resolve the issue. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor or Linux kernel advisory for the current remediation guidance and apply the update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-fj2x-2whx-fgch
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40250"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d59c2644c7f8479c2a
Added to database: 07/30/2026, 15:50:45 UTC
Last enriched: 07/30/2026, 17:23:46 UTC
Last updated: 09/10/2026, 19:38:48 UTC
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.