[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024111958-CVE-2024-50294-0ac7@gregkh>
Date: Tue, 19 Nov 2024 02:32:49 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50294: rxrpc: Fix missing locking causing hanging calls
Description
===========
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.
The Linux kernel CVE team has assigned CVE-2024-50294 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 9d35d880e0e4 and fixed in 6.6.61 with commit 996a7208dadb
Issue introduced in 6.2 with commit 9d35d880e0e4 and fixed in 6.11.8 with commit b1fdb0bb3b65
Issue introduced in 6.2 with commit 9d35d880e0e4 and fixed in 6.12 with commit fc9de52de38f
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2024-50294
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
include/trace/events/rxrpc.h
net/rxrpc/conn_client.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/996a7208dadbf2cdda8d51444d5ee1fdd1ccbc92
https://git.kernel.org/stable/c/b1fdb0bb3b6513f5bd26f92369fd6ac1a2422d8b
https://git.kernel.org/stable/c/fc9de52de38f656399d2ce40f7349a6b5f86e787
Powered by blists - more mailing lists