[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025123012-CVE-2022-50809-e4a0@gregkh>
Date: Tue, 30 Dec 2025 13:09:13 +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-50809: xhci: dbc: Fix memory leak in xhci_alloc_dbc()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
xhci: dbc: Fix memory leak in xhci_alloc_dbc()
If DbC is already in use, then the allocated memory for the xhci_dbc struct
doesn't get freed before returning NULL, which leads to a memleak.
The Linux kernel CVE team has assigned CVE-2022-50809 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15.58 with commit d7afb4a13f6c6ee7df7d0bfc67b4ef19ece6d802 and fixed in 5.15.75 with commit 103b459590e1eb4d80b02761eb36c7cae1d9b58e
Issue introduced in 5.18 with commit 534675942e901959b5d8dc11ea526c4e48817d8e and fixed in 5.19.17 with commit 116d6a6964986ea7eb516daa36128d270f1f248d
Issue introduced in 5.18 with commit 534675942e901959b5d8dc11ea526c4e48817d8e and fixed in 6.0.3 with commit 69e67c804d09a6b1bcda1f4f242f151f813eeb4a
Issue introduced in 5.18 with commit 534675942e901959b5d8dc11ea526c4e48817d8e and fixed in 6.1 with commit d591b32e519603524a35b172156db71df9116902
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-50809
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/usb/host/xhci-dbgcap.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/103b459590e1eb4d80b02761eb36c7cae1d9b58e
https://git.kernel.org/stable/c/116d6a6964986ea7eb516daa36128d270f1f248d
https://git.kernel.org/stable/c/69e67c804d09a6b1bcda1f4f242f151f813eeb4a
https://git.kernel.org/stable/c/d591b32e519603524a35b172156db71df9116902
Powered by blists - more mailing lists