| 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-49314: tty: Fix a possible resource leak in icom_probe |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| tty: Fix a possible resource leak in icom_probe |
| |
| When pci_read_config_dword failed, call pci_release_regions() and |
| pci_disable_device() to recycle the resource previously allocated. |
| |
| The Linux kernel CVE team has assigned CVE-2022-49314 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Fixed in 4.9.318 with commit f4c836d90da1ece88905d62ce2ce39a962f25d1a |
| Fixed in 4.14.283 with commit d703d912a985c1c5b50dd38c3181fc3540fa77cb |
| Fixed in 4.19.247 with commit a2df0b4d080cc770b4da7bff487048c803dfd07e |
| Fixed in 5.4.198 with commit 8c014373f178a4f13a08e045ef63bdb23f62e892 |
| Fixed in 5.10.122 with commit cb7147afd328c07edeeee287710d8d96ac0459f5 |
| Fixed in 5.15.47 with commit 5f9b2e4ca88cab1a96b86ecd45544e488ca43faf |
| Fixed in 5.17.15 with commit 23e155b51d403c0ccedc60c0d6c3c452afed07fe |
| Fixed in 5.18.4 with commit 9a8305f357a8d03698fc7bc855ff9c6865d5486b |
| Fixed in 5.19 with commit ee157a79e7c82b01ae4c25de0ac75899801f322c |
| |
| 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-49314 |
| 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/tty/serial/icom.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/f4c836d90da1ece88905d62ce2ce39a962f25d1a |
| https://git.kernel.org/stable/c/d703d912a985c1c5b50dd38c3181fc3540fa77cb |
| https://git.kernel.org/stable/c/a2df0b4d080cc770b4da7bff487048c803dfd07e |
| https://git.kernel.org/stable/c/8c014373f178a4f13a08e045ef63bdb23f62e892 |
| https://git.kernel.org/stable/c/cb7147afd328c07edeeee287710d8d96ac0459f5 |
| https://git.kernel.org/stable/c/5f9b2e4ca88cab1a96b86ecd45544e488ca43faf |
| https://git.kernel.org/stable/c/23e155b51d403c0ccedc60c0d6c3c452afed07fe |
| https://git.kernel.org/stable/c/9a8305f357a8d03698fc7bc855ff9c6865d5486b |
| https://git.kernel.org/stable/c/ee157a79e7c82b01ae4c25de0ac75899801f322c |