| 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-48628: ceph: drop messages from MDS when unmounting |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ceph: drop messages from MDS when unmounting |
| |
| When unmounting all the dirty buffers will be flushed and after |
| the last osd request is finished the last reference of the i_count |
| will be released. Then it will flush the dirty cap/snap to MDSs, |
| and the unmounting won't wait the possible acks, which will ihold |
| the inodes when updating the metadata locally but makes no sense |
| any more, of this. This will make the evict_inodes() to skip these |
| inodes. |
| |
| If encrypt is enabled the kernel generate a warning when removing |
| the encrypt keys when the skipped inodes still hold the keyring: |
| |
| WARNING: CPU: 4 PID: 168846 at fs/crypto/keyring.c:242 fscrypt_destroy_keyring+0x7e/0xd0 |
| CPU: 4 PID: 168846 Comm: umount Tainted: G S 6.1.0-rc5-ceph-g72ead199864c #1 |
| Hardware name: Supermicro SYS-5018R-WR/X10SRW-F, BIOS 2.0 12/17/2015 |
| RIP: 0010:fscrypt_destroy_keyring+0x7e/0xd0 |
| RSP: 0018:ffffc9000b277e28 EFLAGS: 00010202 |
| RAX: 0000000000000002 RBX: ffff88810d52ac00 RCX: ffff88810b56aa00 |
| RDX: 0000000080000000 RSI: ffffffff822f3a09 RDI: ffff888108f59000 |
| RBP: ffff8881d394fb88 R08: 0000000000000028 R09: 0000000000000000 |
| R10: 0000000000000001 R11: 11ff4fe6834fcd91 R12: ffff8881d394fc40 |
| R13: ffff888108f59000 R14: ffff8881d394f800 R15: 0000000000000000 |
| FS: 00007fd83f6f1080(0000) GS:ffff88885fd00000(0000) knlGS:0000000000000000 |
| CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 |
| CR2: 00007f918d417000 CR3: 000000017f89a005 CR4: 00000000003706e0 |
| DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 |
| DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 |
| Call Trace: |
| <TASK> |
| generic_shutdown_super+0x47/0x120 |
| kill_anon_super+0x14/0x30 |
| ceph_kill_sb+0x36/0x90 [ceph] |
| deactivate_locked_super+0x29/0x60 |
| cleanup_mnt+0xb8/0x140 |
| task_work_run+0x67/0xb0 |
| exit_to_user_mode_prepare+0x23d/0x240 |
| syscall_exit_to_user_mode+0x25/0x60 |
| do_syscall_64+0x40/0x80 |
| entry_SYSCALL_64_after_hwframe+0x63/0xcd |
| RIP: 0033:0x7fd83dc39e9b |
| |
| Later the kernel will crash when iput() the inodes and dereferencing |
| the "sb->s_master_keys", which has been released by the |
| generic_shutdown_super(). |
| |
| The Linux kernel CVE team has assigned CVE-2022-48628 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.34 with commit 9030aaf9bf0a1eee47a154c316c789e959638b0f and fixed in 6.1.56 with commit 89744b64914426cbabceb3d8a149176b5dafdfb5 |
| Issue introduced in 2.6.34 with commit 9030aaf9bf0a1eee47a154c316c789e959638b0f and fixed in 6.5.6 with commit 47f82395f04a976d4fa97de7f2acffa1c1096571 |
| Issue introduced in 2.6.34 with commit 9030aaf9bf0a1eee47a154c316c789e959638b0f and fixed in 6.6 with commit e3dfcab2080dc1f9a4b09cc1327361bc2845bfcd |
| |
| 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-48628 |
| 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/ceph/caps.c |
| fs/ceph/mds_client.c |
| fs/ceph/mds_client.h |
| fs/ceph/quota.c |
| fs/ceph/snap.c |
| fs/ceph/super.c |
| fs/ceph/super.h |
| |
| |
| 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/89744b64914426cbabceb3d8a149176b5dafdfb5 |
| https://git.kernel.org/stable/c/47f82395f04a976d4fa97de7f2acffa1c1096571 |
| https://git.kernel.org/stable/c/e3dfcab2080dc1f9a4b09cc1327361bc2845bfcd |
