UBUNTU-CVE-2024-50047
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] <TASK> [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it's always going to be a synchronous operation.
02 / AFFECTED SOFTWARE
Affected packages
28 explicit affected versions
26 explicit affected versions
14 explicit affected versions
7 explicit affected versions
2 explicit affected versions
10 explicit affected versions
57 explicit affected versions
57 explicit affected versions
13 explicit affected versions
11 explicit affected versions
18 explicit affected versions
6 explicit affected versions
35 explicit affected versions
11 explicit affected versions
40 explicit affected versions
106 explicit affected versions
66 explicit affected versions
50 explicit affected versions
12 explicit affected versions
19 explicit affected versions
6 explicit affected versions
76 explicit affected versions
19 explicit affected versions
61 explicit affected versions
61 explicit affected versions
78 explicit affected versions
69 explicit affected versions
68 explicit affected versions
56 explicit affected versions
10 explicit affected versions
11 explicit affected versions
17 explicit affected versions
7 explicit affected versions
67 explicit affected versions
14 explicit affected versions
13 explicit affected versions
16 explicit affected versions
18 explicit affected versions
27 explicit affected versions
64 explicit affected versions
19 explicit affected versions
108 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
24 explicit affected versions
12 explicit affected versions
111 explicit affected versions
1 explicit affected versions
21 explicit affected versions
16 explicit affected versions
10 explicit affected versions
62 explicit affected versions
22 explicit affected versions
20 explicit affected versions
7 explicit affected versions
12 explicit affected versions
1 explicit affected versions
12 explicit affected versions
14 explicit affected versions
1 explicit affected versions
7 explicit affected versions
1 explicit affected versions
11 explicit affected versions
95 explicit affected versions
12 explicit affected versions
94 explicit affected versions
12 explicit affected versions
14 explicit affected versions
10 explicit affected versions
6 explicit affected versions
10 explicit affected versions
37 explicit affected versions
1 explicit affected versions
13 explicit affected versions
43 explicit affected versions
1 explicit affected versions
26 explicit affected versions
13 explicit affected versions
73 explicit affected versions
15 explicit affected versions
29 explicit affected versions
98 explicit affected versions
13 explicit affected versions
13 explicit affected versions
89 explicit affected versions
68 explicit affected versions
31 explicit affected versions
33 explicit affected versions
23 explicit affected versions
37 explicit affected versions
10 explicit affected versions
1 explicit affected versions
11 explicit affected versions
12 explicit affected versions
3 explicit affected versions
26 explicit affected versions
7 explicit affected versions
12 explicit affected versions
53 explicit affected versions
69 explicit affected versions
10 explicit affected versions
1 explicit affected versions
46 explicit affected versions
10 explicit affected versions
23 explicit affected versions
13 explicit affected versions
19 explicit affected versions
66 explicit affected versions
16 explicit affected versions
70 explicit affected versions
22 explicit affected versions
119 explicit affected versions
20 explicit affected versions
1 explicit affected versions
1 explicit affected versions
2 explicit affected versions
51 explicit affected versions
7 explicit affected versions
12 explicit affected versions
59 explicit affected versions
56 explicit affected versions
27 explicit affected versions
62 explicit affected versions
4 explicit affected versions
43 explicit affected versions
109 explicit affected versions
1 explicit affected versions
15 explicit affected versions
8 explicit affected versions
33 explicit affected versions
5 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
18 explicit affected versions
13 explicit affected versions
98 explicit affected versions
13 explicit affected versions
12 explicit affected versions
16 explicit affected versions
96 explicit affected versions
69 explicit affected versions
38 explicit affected versions
13 explicit affected versions
26 explicit affected versions
43 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
45 explicit affected versions
37 explicit affected versions
23 explicit affected versions
14 explicit affected versions
9 explicit affected versions
11 explicit affected versions
13 explicit affected versions
7 explicit affected versions
69 explicit affected versions
7 explicit affected versions
58 explicit affected versions
1 explicit affected versions
1 explicit affected versions
1 explicit affected versions
67 explicit affected versions
43 explicit affected versions
64 explicit affected versions
106 explicit affected versions
10 explicit affected versions
8 explicit affected versions
17 explicit affected versions
76 explicit affected versions
14 explicit affected versions
4 explicit affected versions
78 explicit affected versions
1 explicit affected versions
110 explicit affected versions
14 explicit affected versions
58 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix UAF in async decryption Doing an async decryption (large read) crashes with a slab-use-after-free way down in the crypto API. Reproducer: # mount.cifs -o ...,seal,esize=1 //srv/share /mnt # dd if=/mnt/largefile of=/dev/null ... [ 194.196391] ================================================================== [ 194.196844] BUG: KASAN: slab-use-after-free in gf128mul_4k_lle+0xc1/0x110 [ 194.197269] Read of size 8 at addr ffff888112bd0448 by task kworker/u77:2/899 [ 194.197707] [ 194.197818] CPU: 12 UID: 0 PID: 899 Comm: kworker/u77:2 Not tainted 6.11.0-lku-00028-gfca3ca14a17a-dirty #43 [ 194.198400] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.2-3-gd478f380-prebuilt.qemu.org 04/01/2014 [ 194.199046] Workqueue: smb3decryptd smb2_decrypt_offload [cifs] [ 194.200032] Call Trace: [ 194.200191] <TASK> [ 194.200327] dump_stack_lvl+0x4e/0x70 [ 194.200558] ? gf128mul_4k_lle+0xc1/0x110 [ 194.200809] print_report+0x174/0x505 [ 194.201040] ? __pfx__raw_spin_lock_irqsave+0x10/0x10 [ 194.201352] ? srso_return_thunk+0x5/0x5f [ 194.201604] ? __virt_addr_valid+0xdf/0x1c0 [ 194.201868] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202128] kasan_report+0xc8/0x150 [ 194.202361] ? gf128mul_4k_lle+0xc1/0x110 [ 194.202616] gf128mul_4k_lle+0xc1/0x110 [ 194.202863] ghash_update+0x184/0x210 [ 194.203103] shash_ahash_update+0x184/0x2a0 [ 194.203377] ? __pfx_shash_ahash_update+0x10/0x10 [ 194.203651] ? srso_return_thunk+0x5/0x5f [ 194.203877] ? crypto_gcm_init_common+0x1ba/0x340 [ 194.204142] gcm_hash_assoc_remain_continue+0x10a/0x140 [ 194.204434] crypt_message+0xec1/0x10a0 [cifs] [ 194.206489] ? __pfx_crypt_message+0x10/0x10 [cifs] [ 194.208507] ? srso_return_thunk+0x5/0x5f [ 194.209205] ? srso_return_thunk+0x5/0x5f [ 194.209925] ? srso_return_thunk+0x5/0x5f [ 194.210443] ? srso_return_thunk+0x5/0x5f [ 194.211037] decrypt_raw_data+0x15f/0x250 [cifs] [ 194.212906] ? __pfx_decrypt_raw_data+0x10/0x10 [cifs] [ 194.214670] ? srso_return_thunk+0x5/0x5f [ 194.215193] smb2_decrypt_offload+0x12a/0x6c0 [cifs] This is because TFM is being used in parallel. Fix this by allocating a new AEAD TFM for async decryption, but keep the existing one for synchronous READ cases (similar to what is done in smb3_calc_signature()). Also remove the calls to aead_request_set_callback() and crypto_wait_req() since it's always going to be a synchronous operation.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/b0abcd65ec545701b8793e12bc27dc98042b151a
- https://git.kernel.org/stable/c/0809fb86ad13b29e1d6d491364fc7ea4fb545995
- https://git.kernel.org/stable/c/538c26d9bf70c90edc460d18c81008a4e555925a
- https://git.kernel.org/stable/c/b0abcd65ec545701b8793e12bc27dc98042b151a
- https://ubuntu.com/security/CVE-2024-50047
- https://ubuntu.com/security/notices/USN-7276-1
- https://ubuntu.com/security/notices/USN-7277-1
- https://ubuntu.com/security/notices/USN-7310-1
- https://ubuntu.com/security/notices/USN-7383-1
- https://ubuntu.com/security/notices/USN-7383-2
- https://ubuntu.com/security/notices/USN-7384-1
- https://ubuntu.com/security/notices/USN-7384-2
- https://ubuntu.com/security/notices/USN-7385-1
- https://ubuntu.com/security/notices/USN-7386-1
- https://ubuntu.com/security/notices/USN-7403-1
- https://ubuntu.com/security/notices/USN-7451-1
- https://ubuntu.com/security/notices/USN-7468-1
- https://ubuntu.com/security/notices/USN-7523-1
- https://ubuntu.com/security/notices/USN-7524-1
- https://ubuntu.com/security/notices/USN-7608-1
- https://ubuntu.com/security/notices/USN-7608-2
- https://ubuntu.com/security/notices/USN-7608-3
- https://ubuntu.com/security/notices/USN-7608-4
- https://ubuntu.com/security/notices/USN-7608-5
- https://ubuntu.com/security/notices/USN-7608-6
- https://ubuntu.com/security/notices/USN-7608-7
- https://ubuntu.com/security/notices/USN-7655-1
- https://ubuntu.com/security/notices/USN-7671-1
- https://ubuntu.com/security/notices/USN-7671-2
- https://ubuntu.com/security/notices/USN-7671-3
- https://ubuntu.com/security/notices/USN-7686-1
- https://ubuntu.com/security/notices/USN-7712-1
- https://ubuntu.com/security/notices/USN-7712-2
- https://www.cve.org/CVERecord?id=CVE-2024-50047