| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2022-48707: cxl/region: Fix null pointer dereference for resetting decoder |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| cxl/region: Fix null pointer dereference for resetting decoder |
| |
| Not all decoders have a reset callback. |
| |
| The CXL specification allows a host bridge with a single root port to |
| have no explicit HDM decoders. Currently the region driver assumes there |
| are none. As such the CXL core creates a special pass through decoder |
| instance without a commit/reset callback. |
| |
| Prior to this patch, the ->reset() callback was called unconditionally when |
| calling cxl_region_decode_reset. Thus a configuration with 1 Host Bridge, |
| 1 Root Port, and one directly attached CXL type 3 device or multiple CXL |
| type 3 devices attached to downstream ports of a switch can cause a null |
| pointer dereference. |
| |
| Before the fix, a kernel crash was observed when we destroy the region, and |
| a pass through decoder is reset. |
| |
| The issue can be reproduced as below, |
| 1) create a region with a CXL setup which includes a HB with a |
| single root port under which a memdev is attached directly. |
| 2) destroy the region with cxl destroy-region regionX -f. |
| |
| The Linux kernel CVE team has assigned CVE-2022-48707 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.0 with commit 176baefb2eb5d7a3ddebe3ff803db1fce44574b5 and fixed in 6.1.12 with commit a04c7d062b537ff787d00da95bdfe343260d4beb |
| Issue introduced in 6.0 with commit 176baefb2eb5d7a3ddebe3ff803db1fce44574b5 and fixed in 6.2 with commit 4fa4302d6dc7de7e8e74dc7405611a2efb4bf54b |
| |
| 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-48707 |
| 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/cxl/core/region.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/a04c7d062b537ff787d00da95bdfe343260d4beb |
| https://git.kernel.org/stable/c/4fa4302d6dc7de7e8e74dc7405611a2efb4bf54b |