Skip to main content
← Vulnerabilities

io_uring/waitid: prevent cancel reference wrap

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

7.8HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only
Published
Last modified
Published
Not listed in CISA KEV
38/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

The io_uring waitid subsystem in the Linux kernel can be made to complete the same request twice when cancellation is repeatedly attempted. The result is a memory-safety problem in the kernel, which could lead to crashes or other unpredictable behavior, including potential privilege escalation.

Read the original description

In the Linux kernel, the following vulnerability has been resolved: io_uring/waitid: prevent cancel reference wrap io_waitid packs the cancellation state into bit 31 of ->refs and uses bits 30:0 as a 31-bit reference counter: #define IO_WAITID_CANCEL_FLAG BIT(31) #define IO_WAITID_REF_MASK GENMASK(30, 0) __io_waitid_cancel() marks a request canceled, then increments the low bits of ->refs to claim completion ownership. When another path owns the request, the increment remains even though cancellation returns false. The request remains discoverable by cancellation, so repeated failed attempts can wrap the 31-bit reference field to zero. A later cancellation can claim ownership and complete the request a second time. Use atomic_fetch_or() when setting the cancel flag and inspect the old flag value. The first cancel attempt continues to the existing ownership increment, preserving its wake and issuer handoff semantics. Later attempts see the cancel flag and return without incrementing the reference field. This makes repeated failed cancellation attempts idempotent while leaving the first-cancel state transitions unchanged.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • Linux Linux

    Version range not reported

  • Linux Linux

    6.7

Evidence 4

  1. Link
  2. Link
  3. Link
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.