io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 521861b17a107875c884df9474e7746617f256d5, Kernel 8543a39f03db8816a2d80d0c92c132a19f2afb48 and Kernel 7.3.2.
In the Linux kernel, the following vulnerability has been resolved: io_uring/bpf-ops: clear bpf_ctx while submitting SQEs bpf_io_uring_submit_sqes() calls io_submit_sqes() from inside the loop program, with current->bpf_ctx set, and requests issued inline run with it set too. The socket code uses has_current_bpf_ctx() to recognize calls from bpf_setsockopt() and friends, where the caller holds the socket lock and has already been vetted, and skips both. So a SOCKET_URING_OP_SETSOCKOPT from the SQ passes sockopt_capable() without the capability, and runs without lock_sock(). A task with no capability can set SO_MARK, IP_TRANSPARENT or TCP_REPAIR, and two threads changing IP_OPTIONS on one socket, one through the ring, double free in no time. SOCK_DESTROY via IORING_OP_SENDMSG ends up in tcp_abort() without the lock the same way. Clear the run context around io_submit_sqes(). The SQEs come from userspace and must be issued like those of any other ring. They still run inside the program's RCU tasks trace read section, so a request that sleeps there holds up that grace period, but other request types do that already.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.1, >=890819248a8616558fe12e6c06c918ee1c3a2bc6 <521861b17a107875c884df9474e7746617f256d5, >=890819248a8616558fe12e6c06c918ee1c3a2bc6 <8543a39f03db8816a2d80d0c92c132a19f2afb48 | 521861b17a107875c884df9474e7746617f256d5, 8543a39f03db8816a2d80d0c92c132a19f2afb48 |
| linux-kernel: Kernel | >=7.1.0 <7.3.2 | 7.3.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket