UBUNTU-CVE-2024-26584
In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API, crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example, when the cryptd queue for AESNI is full (easy to trigger with an artificially low cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case, the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical.
02 / AFFECTED SOFTWARE
Affected packages
16 explicit affected versions
6 explicit affected versions
11 explicit affected versions
7 explicit affected versions
4 explicit affected versions
29 explicit affected versions
43 explicit affected versions
50 explicit affected versions
6 explicit affected versions
12 explicit affected versions
52 explicit affected versions
38 explicit affected versions
62 explicit affected versions
49 explicit affected versions
38 explicit affected versions
7 explicit affected versions
45 explicit affected versions
7 explicit affected versions
91 explicit affected versions
46 explicit affected versions
89 explicit affected versions
9 explicit affected versions
35 explicit affected versions
16 explicit affected versions
10 explicit affected versions
5 explicit affected versions
14 explicit affected versions
18 explicit affected versions
7 explicit affected versions
33 explicit affected versions
13 explicit affected versions
4 explicit affected versions
23 explicit affected versions
21 explicit affected versions
9 explicit affected versions
46 explicit affected versions
7 explicit affected versions
12 explicit affected versions
36 explicit affected versions
12 explicit affected versions
10 explicit affected versions
7 explicit affected versions
79 explicit affected versions
12 explicit affected versions
5 explicit affected versions
94 explicit affected versions
102 explicit affected versions
12 explicit affected versions
90 explicit affected versions
10 explicit affected versions
10 explicit affected versions
37 explicit affected versions
9 explicit affected versions
10 explicit affected versions
25 explicit affected versions
1 explicit affected versions
32 explicit affected versions
26 explicit affected versions
13 explicit affected versions
4 explicit affected versions
10 explicit affected versions
29 explicit affected versions
82 explicit affected versions
13 explicit affected versions
49 explicit affected versions
78 explicit affected versions
47 explicit affected versions
94 explicit affected versions
9 explicit affected versions
33 explicit affected versions
23 explicit affected versions
10 explicit affected versions
11 explicit affected versions
12 explicit affected versions
30 explicit affected versions
7 explicit affected versions
12 explicit affected versions
93 explicit affected versions
37 explicit affected versions
12 explicit affected versions
46 explicit affected versions
10 explicit affected versions
26 explicit affected versions
28 explicit affected versions
1 explicit affected versions
13 explicit affected versions
52 explicit affected versions
16 explicit affected versions
49 explicit affected versions
39 explicit affected versions
3 explicit affected versions
1 explicit affected versions
2 explicit affected versions
59 explicit affected versions
51 explicit affected versions
2 explicit affected versions
12 explicit affected versions
35 explicit affected versions
10 explicit affected versions
27 explicit affected versions
21 explicit affected versions
1 explicit affected versions
8 explicit affected versions
8 explicit affected versions
1 explicit affected versions
10 explicit affected versions
9 explicit affected versions
82 explicit affected versions
13 explicit affected versions
46 explicit affected versions
7 explicit affected versions
41 explicit affected versions
12 explicit affected versions
81 explicit affected versions
44 explicit affected versions
16 explicit affected versions
3 explicit affected versions
13 explicit affected versions
26 explicit affected versions
35 explicit affected versions
37 explicit affected versions
14 explicit affected versions
38 explicit affected versions
39 explicit affected versions
9 explicit affected versions
38 explicit affected versions
46 explicit affected versions
8 explicit affected versions
7 explicit affected versions
20 explicit affected versions
53 explicit affected versions
1 explicit affected versions
1 explicit affected versions
44 explicit affected versions
10 explicit affected versions
43 explicit affected versions
47 explicit affected versions
10 explicit affected versions
8 explicit affected versions
14 explicit affected versions
82 explicit affected versions
4 explicit affected versions
71 explicit affected versions
7 explicit affected versions
1 explicit affected versions
03 / CONNECTIONS
Connected vulnerabilities
04 / EVIDENCE
Source records
In the Linux kernel, the following vulnerability has been resolved: net: tls: handle backlogging of crypto requests Since we're setting the CRYPTO_TFM_REQ_MAY_BACKLOG flag on our requests to the crypto API, crypto_aead_{encrypt,decrypt} can return -EBUSY instead of -EINPROGRESS in valid situations. For example, when the cryptd queue for AESNI is full (easy to trigger with an artificially low cryptd.cryptd_max_cpu_qlen), requests will be enqueued to the backlog but still processed. In that case, the async callback will also be called twice: first with err == -EINPROGRESS, which it seems we can just ignore, then with err == 0. Compared to Sabrina's original patch this version uses the new tls_*crypt_async_wait() helpers and converts the EBUSY to EINPROGRESS to avoid having to modify all the error handling paths. The handling is identical.
05 / REFERENCES
Further evidence
- https://git.kernel.org/linus/8590541473188741055d27b955db0777569438e3
- https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
- https://ubuntu.com/security/CVE-2024-26584
- https://ubuntu.com/security/notices/USN-6818-1
- https://ubuntu.com/security/notices/USN-6818-2
- https://ubuntu.com/security/notices/USN-6818-3
- https://ubuntu.com/security/notices/USN-6818-4
- https://ubuntu.com/security/notices/USN-6819-1
- https://ubuntu.com/security/notices/USN-6819-2
- https://ubuntu.com/security/notices/USN-6819-3
- https://ubuntu.com/security/notices/USN-6819-4
- https://ubuntu.com/security/notices/USN-6820-1
- https://ubuntu.com/security/notices/USN-6820-2
- https://ubuntu.com/security/notices/USN-6821-1
- https://ubuntu.com/security/notices/USN-6821-2
- https://ubuntu.com/security/notices/USN-6821-3
- https://ubuntu.com/security/notices/USN-6821-4
- https://ubuntu.com/security/notices/USN-6828-1
- https://ubuntu.com/security/notices/USN-6871-1
- https://ubuntu.com/security/notices/USN-6892-1
- https://ubuntu.com/security/notices/USN-6919-1
- https://ubuntu.com/security/notices/USN-6924-1
- https://ubuntu.com/security/notices/USN-6924-2
- https://ubuntu.com/security/notices/USN-6953-1
- https://ubuntu.com/security/notices/USN-6979-1
- https://www.cve.org/CVERecord?id=CVE-2024-26584