[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024102142-CVE-2022-48959-6120@gregkh>
Date: Mon, 21 Oct 2024 22:05:51 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-48959: net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions()
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: dsa: sja1105: fix memory leak in sja1105_setup_devlink_regions()
When dsa_devlink_region_create failed in sja1105_setup_devlink_regions(),
priv->regions is not released.
The Linux kernel CVE team has assigned CVE-2022-48959 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.10 with commit bf425b82059e and fixed in 5.10.159 with commit 4be43e46c3f9
Issue introduced in 5.10 with commit bf425b82059e and fixed in 5.15.83 with commit f3b5dda26cd0
Issue introduced in 5.10 with commit bf425b82059e and fixed in 6.0.13 with commit e5e59629654b
Issue introduced in 5.10 with commit bf425b82059e and fixed in 6.1 with commit 78a9ea43fc1a
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-48959
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:
drivers/net/dsa/sja1105/sja1105_devlink.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/4be43e46c3f945fc7dd9e23c73a7a66927a3b814
https://git.kernel.org/stable/c/f3b5dda26cd0535aac09ed09c5d83f19b979ec9f
https://git.kernel.org/stable/c/e5e59629654b8826f0167dae480d0e3fa0f8f038
https://git.kernel.org/stable/c/78a9ea43fc1a7c06a420b132d2d47cbf4344a5df
Powered by blists - more mailing lists