Improper Handling of Exceptional Conditions Affecting python3-perf-debuginfo package, versions <0:4.18.0-553.8.1.el8_10

Note: Versions mentioned in the description apply only to the upstream python3-perf-debuginfo package and not the python3-perf-debuginfo 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.

• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-26584
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/EZOU3745CWCDZ7EMKMXB2OEEIB5Q3IWM/
• https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OX4EWCYDZRTOEMC2C6OF7ZACAP23SUB5/
• https://git.kernel.org/stable/c/13eca403876bbea3716e82cdfe6f1e6febb38754
• https://git.kernel.org/stable/c/8590541473188741055d27b955db0777569438e3
• https://git.kernel.org/stable/c/ab6397f072e5097f267abf5cb08a8004e6b17694
• https://git.kernel.org/stable/c/cd1bbca03f3c1d845ce274c0d0a66de8e5929f72
• https://git.kernel.org/stable/c/3ade391adc584f17b5570fd205de3ad029090368