| From bippy-1.1.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2023-53055: fscrypt: destroy keyring after security_sb_delete() |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| fscrypt: destroy keyring after security_sb_delete() |
| |
| fscrypt_destroy_keyring() must be called after all potentially-encrypted |
| inodes were evicted; otherwise it cannot safely destroy the keyring. |
| Since inodes that are in-use by the Landlock LSM don't get evicted until |
| security_sb_delete(), this means that fscrypt_destroy_keyring() must be |
| called *after* security_sb_delete(). |
| |
| This fixes a WARN_ON followed by a NULL dereference, only possible if |
| Landlock was being used on encrypted files. |
| |
| The Linux kernel CVE team has assigned CVE-2023-53055 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.15.78 with commit e6f4fd85ef1ee6ab356bfbd64df28c1cb73aee7e and fixed in 5.15.105 with commit 992a3f3e8a0c92151dfdf65fc85567c865fd558a |
| Issue introduced in 6.1 with commit d7e7b9af104c7b389a0c21eb26532511bce4b510 and fixed in 6.1.22 with commit d77531fac6a1fd9f1db0195438ba5419d72b96c4 |
| Issue introduced in 6.1 with commit d7e7b9af104c7b389a0c21eb26532511bce4b510 and fixed in 6.2.9 with commit 497ab5d9c7852dfedab2c9de75e41b60e54b7c5d |
| Issue introduced in 6.1 with commit d7e7b9af104c7b389a0c21eb26532511bce4b510 and fixed in 6.3 with commit ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a |
| Issue introduced in 5.10.154 with commit 391cceee6d435e616f68631e68f5b32d480b1e67 |
| Issue introduced in 6.0.8 with commit 68d15d6558a386f46d815a6ac39edecad713a1bf |
| |
| 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-53055 |
| 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: |
| fs/super.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/992a3f3e8a0c92151dfdf65fc85567c865fd558a |
| https://git.kernel.org/stable/c/d77531fac6a1fd9f1db0195438ba5419d72b96c4 |
| https://git.kernel.org/stable/c/497ab5d9c7852dfedab2c9de75e41b60e54b7c5d |
| https://git.kernel.org/stable/c/ccb820dc7d2236b1af0d54ae038a27b5b6d5ae5a |
