Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: always prune wait queue entry in io_waitid_wait() For a… (CVE-2025-40047)
In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: always prune wait queue entry in io_waitid_wait() For a successful return, always remove our entry from the wait queue entry list. Previously this was skipped if a cancelation was in progress, but this can race with another invocation of the wait queue entry callback.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2025-40047 involves the io_uring subsystem's wait queue management in the io_waitid_wait() function. The issue was that the wait queue entry was not always removed upon successful return if a cancellation was in progress, leading to a race condition with concurrent wait queue callbacks. This could result in severe consequences affecting system confidentiality, integrity, and availability. The vulnerability has been resolved by modifying the code to always prune the wait queue entry regardless of cancellation state.
Potential Impact
This vulnerability has a high severity rating with potential impacts on confidentiality, integrity, and availability of the affected system. Exploitation could allow an attacker with local privileges to cause race conditions that may lead to system instability or unauthorized access to kernel resources.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by ensuring the wait queue entry is always pruned in io_waitid_wait(). Users and administrators should apply the official kernel updates that include this patch once available. Patch status is not yet confirmed in this data; verify with the Linux kernel vendor advisory for current remediation guidance.
Linux hwe edge: In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: always prune wait queue entry in io_waitid_wait() For a… (CVE-2025-40047)
Description
In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: always prune wait queue entry in io_waitid_wait() For a successful return, always remove our entry from the wait queue entry list. Previously this was skipped if a cancelation was in progress, but this can race with another invocation of the wait queue entry callback.
CVSS v3.1
Score 7.8high
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2025-40047 involves the io_uring subsystem's wait queue management in the io_waitid_wait() function. The issue was that the wait queue entry was not always removed upon successful return if a cancellation was in progress, leading to a race condition with concurrent wait queue callbacks. This could result in severe consequences affecting system confidentiality, integrity, and availability. The vulnerability has been resolved by modifying the code to always prune the wait queue entry regardless of cancellation state.
Potential Impact
This vulnerability has a high severity rating with potential impacts on confidentiality, integrity, and availability of the affected system. Exploitation could allow an attacker with local privileges to cause race conditions that may lead to system instability or unauthorized access to kernel resources.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this vulnerability by ensuring the wait queue entry is always pruned in io_waitid_wait(). Users and administrators should apply the official kernel updates that include this patch once available. Patch status is not yet confirmed in this data; verify with the Linux kernel vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2r8v-pxwr-9h89
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-40047"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d79c2644c7f847b4e3
Added to database: 07/30/2026, 15:50:47 UTC
Last enriched: 07/30/2026, 16:10:13 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 30
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.