rxrpc: Fix missing locking causing hanging calls
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 996a7208dadbf2cdda8d51444d5ee1fdd1ccbc92, Kernel b1fdb0bb3b6513f5bd26f92369fd6ac1a2422d8b and Kernel fc9de52de38f656399d2ce40f7349a6b5f86e787.
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix missing locking causing hanging calls If a call gets aborted (e.g. because kafs saw a signal) between it being queued for connection and the I/O thread picking up the call, the abort will be prioritised over the connection and it will be removed from local->new_client_calls by rxrpc_disconnect_client_call() without a lock being held. This may cause other calls on the list to disappear if a race occurs. Fix this by taking the client_call_lock when removing a call from whatever list its ->wait_link happens to be on.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.2, >=9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d <996a7208dadbf2cdda8d51444d5ee1fdd1ccbc92, >=9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d <b1fdb0bb3b6513f5bd26f92369fd6ac1a2422d8b, >=9d35d880e0e4a3ab32d8c12f9e4d76198aadd42d <fc9de52de38f656399d2ce40f7349a6b5f86e787 | 996a7208dadbf2cdda8d51444d5ee1fdd1ccbc92, b1fdb0bb3b6513f5bd26f92369fd6ac1a2422d8b, fc9de52de38f656399d2ce40f7349a6b5f86e787 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket