[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024110940-CVE-2024-50260-db68@gregkh>
Date: Sat, 9 Nov 2024 11:16:08 +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-50260: sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
sock_map: fix a NULL pointer dereference in sock_map_link_update_prog()
The following race condition could trigger a NULL pointer dereference:
sock_map_link_detach(): sock_map_link_update_prog():
mutex_lock(&sockmap_mutex);
...
sockmap_link->map = NULL;
mutex_unlock(&sockmap_mutex);
mutex_lock(&sockmap_mutex);
...
sock_map_prog_link_lookup(sockmap_link->map);
mutex_unlock(&sockmap_mutex);
<continue>
Fix it by adding a NULL pointer check. In this specific case, it makes
no sense to update a link which is being released.
The Linux kernel CVE team has assigned CVE-2024-50260 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.10 with commit 699c23f02c65 and fixed in 6.11.7 with commit 9afe35fdda16
Issue introduced in 6.10 with commit 699c23f02c65 and fixed in 6.12-rc6 with commit 740be3b9a6d7
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-50260
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:
net/core/sock_map.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/9afe35fdda16e09d5bd3c49a68ba8c680dd678bd
https://git.kernel.org/stable/c/740be3b9a6d73336f8c7d540842d0831dc7a808b
Powered by blists - more mailing lists