Linux Kernel up to 4.15/6.8-rc4 TLS net/tls/tls_sw.c tls_decrypt_done privilege escalation

Summaryinfo

A vulnerability was found in Linux Kernel up to 4.15/6.8-rc4. It has been rated as problematic. This issue affects the function tls_decrypt_done of the file net/tls/tls_sw.c of the component TLS Handler. This manipulation causes an unknown weakness. This vulnerability is handled as CVE-2024-26584. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in Linux Kernel up to 4.15/6.8-rc4 (Operating System). It has been declared as problematic. Affected by this vulnerability is the function tls_decrypt_done of the file net/tls/tls_sw.c of the component TLS Handler. The impact remains unknown. The summary by CVE is:

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.

The weakness was released 02/21/2024. The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2024-26584 since 02/19/2024. Technical details are known, but no exploit is available.

Upgrading to version 4.16 or 6.8-rc5 eliminates this vulnerability. Applying the patch 859054147318 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11
• 4.12
• 4.13
• 4.14
• 4.15
• 6.8-rc1
• 6.8-rc2
• 6.8-rc3
• 6.8-rc4

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion