| 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-2023-52983: block, bfq: fix uaf for bfqq in bic_set_bfqq() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| block, bfq: fix uaf for bfqq in bic_set_bfqq() |
| |
| After commit 64dc8c732f5c ("block, bfq: fix possible uaf for 'bfqq->bic'"), |
| bic->bfqq will be accessed in bic_set_bfqq(), however, in some context |
| bic->bfqq will be freed, and bic_set_bfqq() is called with the freed |
| bic->bfqq. |
| |
| Fix the problem by always freeing bfqq after bic_set_bfqq(). |
| |
| The Linux kernel CVE team has assigned CVE-2023-52983 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.15.86 with commit 094f3d9314d67691cb21ba091c1b528f6e3c4893 and fixed in 5.15.93 with commit 511c922c5bf6c8a166bea826e702336bc2424140 |
| Issue introduced in 6.1.2 with commit 761564d93c8265f65543acf0a576b32d66bfa26a and fixed in 6.1.11 with commit cb1876fc33af26d00efdd473311f1b664c77c44e |
| Issue introduced in 6.0.16 with commit b22fd72bfebda3956efc4431b60ddfc0a51e03e0 |
| |
| 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-2023-52983 |
| 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: |
| block/bfq-cgroup.c |
| block/bfq-iosched.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/7f77f3dab5066a7c9da73d72d1eee895ff84a8d5 |
| https://git.kernel.org/stable/c/511c922c5bf6c8a166bea826e702336bc2424140 |
| https://git.kernel.org/stable/c/cb1876fc33af26d00efdd473311f1b664c77c44e |
| https://git.kernel.org/stable/c/b600de2d7d3a16f9007fad1bdae82a3951a26af2 |
