Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2024-26800

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: tls: fix use-after-free on failed backlog decryption When the decrypt request goes to the backlog and crypto_aead_decrypt retur…

Published Apr 4, 2024CWE-416EPSS 0.74%

Overview

CVE-2024-26800 is a critical-severity vulnerability. It was published on April 4, 2024 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

tls: fix use-after-free on failed backlog decryption

When the decrypt request goes to the backlog and crypto_aead_decrypt

returns -EBUSY, tls_do_decryption will wait until all async

decryptions have completed. If one of them fails, tls_do_decryption

will return -EBADMSG and tls_decrypt_sg jumps to the error path,

releasing all the pages. But the pages have been passed to the async

callback, and have already been released by tls_decrypt_done.

The only true async case is when crypto_aead_decrypt returns

-EINPROGRESS. With -EBUSY, we already waited so we can tell

tls_sw_recvmsg that the data is available for immediate copy, but we

need to notify tls_decrypt_sg (via the new ->async_done flag) that the

memory has already been released.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/13114dc5543069f7b97991e3b79937b6da05f5b0Refgit.kernel.org/stable/c/1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1Refgit.kernel.org/stable/c/81be85353b0f5a7b660635634b655329b429eefeRefgit.kernel.org/stable/c/f2b85a4cc763841843de693bbd7308fe9a2c4c89Refgit.kernel.org/stable/c/13114dc5543069f7b97991e3b79937b6da05f5b0Refgit.kernel.org/stable/c/1ac9fb84bc7ecd4bc6428118301d9d864d2a58d1Refgit.kernel.org/stable/c/81be85353b0f5a7b660635634b655329b429eefeRefgit.kernel.org/stable/c/f2b85a4cc763841843de693bbd7308fe9a2c4c89

How CyberStrike helps

Frequently asked questions

What is CVE-2024-26800?

CVE-2024-26800 is a critical-severity vulnerability. It was published on April 4, 2024 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2024-26800?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2024-26800?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2024-26800?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-26800 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related CRITICAL CVEs from 2024

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999