Improper Handling of Exceptional Conditions Affecting kernel-rt-debug-devel package, versions <0:4.18.0-553.8.1.rt7.349.el8_10


Severity

Recommended
high

Based on Rocky Linux security rating.

Threat Intelligence

EPSS
0.04% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ROCKY8-KERNELRTDEBUGDEVEL-7455622
  • published16 Jul 2024
  • disclosed21 Feb 2024

Introduced: 21 Feb 2024

CVE-2024-26584  (opens in a new tab)
CWE-755  (opens in a new tab)

How to fix?

Upgrade Rocky-Linux:8 kernel-rt-debug-devel to version 0:4.18.0-553.8.1.rt7.349.el8_10 or higher.
This issue was patched in RLSA-2024:4352.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-devel package and not the kernel-rt-debug-devel package as distributed by Rocky-Linux. See How to fix? for Rocky-Linux:8 relevant fixed versions and status.

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.

CVSS Scores

version 3.1