[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022618-CVE-2022-49202-070c@gregkh>
Date: Wed, 26 Feb 2025 02:56:47 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-49202: Bluetooth: hci_uart: add missing NULL check in h5_enqueue
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_uart: add missing NULL check in h5_enqueue
Syzbot hit general protection fault in __pm_runtime_resume(). The problem
was in missing NULL check.
hu->serdev can be NULL and we should not blindly pass &serdev->dev
somewhere, since it will cause GPF.
The Linux kernel CVE team has assigned CVE-2022-49202 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.15 with commit d9dd833cf6d29695682ec7e7924c0d0992b906bc and fixed in 5.15.33 with commit 7235485433d290367d60ae22fcdfc565e61d42ab
Issue introduced in 5.15 with commit d9dd833cf6d29695682ec7e7924c0d0992b906bc and fixed in 5.16.19 with commit e6b6c904c0f88588b6a3ace20e4c0d61eab124f8
Issue introduced in 5.15 with commit d9dd833cf6d29695682ec7e7924c0d0992b906bc and fixed in 5.17.2 with commit 8a3896c30f542439d36303183dc96f65df8cc528
Issue introduced in 5.15 with commit d9dd833cf6d29695682ec7e7924c0d0992b906bc and fixed in 5.18 with commit 32cb08e958696908a9aad5e49a78d74f7e32fffb
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-49202
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/bluetooth/hci_h5.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/7235485433d290367d60ae22fcdfc565e61d42ab
https://git.kernel.org/stable/c/e6b6c904c0f88588b6a3ace20e4c0d61eab124f8
https://git.kernel.org/stable/c/8a3896c30f542439d36303183dc96f65df8cc528
https://git.kernel.org/stable/c/32cb08e958696908a9aad5e49a78d74f7e32fffb
Powered by blists - more mailing lists