io_uring/openclose: keep the lock in io_pipe_fixed()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 7299a32764ab875443b58581d929027954dcf24c, Kernel a3d7ee11289f657aa9af826d8f0844221292a27a and Kernel b4b7b2d19dab611f3cf3d052aa19278e7e4c4683.
In the Linux kernel, the following vulnerability has been resolved: io_uring/openclose: keep the lock in io_pipe_fixed() io_pipe_fixed() installs both ends of the pipe in the fixed file table, drops ->uring_lock, and copies the slot numbers to the application. If that faults, it takes the lock again and removes whatever is in these slots. If the request is run by io-wq the lock really is dropped in between, and the slots are visible to everybody else. By the time the error path gets to them, they may have been closed and reused, by IORING_OP_CLOSE and a direct open or accept, or by IORING_REGISTER_FILES_UPDATE. Then a file is removed from the table that has nothing to do with the failed request. Do the copy with the lock held. Faulting in user memory under ->uring_lock is fine, the registration paths do it all the time.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.16, >=53db8a71ecb42c2ec5e9c6925269a750255f9af5 <7299a32764ab875443b58581d929027954dcf24c, >=53db8a71ecb42c2ec5e9c6925269a750255f9af5 <a3d7ee11289f657aa9af826d8f0844221292a27a, >=53db8a71ecb42c2ec5e9c6925269a750255f9af5 <b4b7b2d19dab611f3cf3d052aa19278e7e4c4683 | 7299a32764ab875443b58581d929027954dcf24c, a3d7ee11289f657aa9af826d8f0844221292a27a, b4b7b2d19dab611f3cf3d052aa19278e7e4c4683 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket