[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122456-CVE-2022-50764-45eb@gregkh>
Date: Wed, 24 Dec 2025 14:06:15 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50764: ipv6/sit: use DEV_STATS_INC() to avoid data-races
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ipv6/sit: use DEV_STATS_INC() to avoid data-races
syzbot/KCSAN reported that multiple cpus are updating dev->stats.tx_error
concurrently.
This is because sit tunnels are NETIF_F_LLTX, meaning their ndo_start_xmit()
is not protected by a spinlock.
While original KCSAN report was about tx path, rx path has the same issue.
The Linux kernel CVE team has assigned CVE-2022-50764 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.86 with commit 222cc04356984f3f98acfa756a69d4bed7c501ac
Fixed in 6.0.16 with commit 4eed93bb3e57b8cc78d17166a14e40a73276015a
Fixed in 6.1.2 with commit 207501a986831174df09a36a8cb62a28f92f0dc8
Fixed in 6.2 with commit cb34b7cf17ecf33499c9298943f85af247abc1e9
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-2022-50764
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/ipv6/sit.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/222cc04356984f3f98acfa756a69d4bed7c501ac
https://git.kernel.org/stable/c/4eed93bb3e57b8cc78d17166a14e40a73276015a
https://git.kernel.org/stable/c/207501a986831174df09a36a8cb62a28f92f0dc8
https://git.kernel.org/stable/c/cb34b7cf17ecf33499c9298943f85af247abc1e9
Powered by blists - more mailing lists