Go to homepageCyberStrike

Menu

Star on GitHub · 3.3k
Sign inDownload

CVE-2024-26877

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: crypto: xilinx - call finalize with bh disabled When calling crypto_finalize_request, BH should be disabled to avoid triggering…

Published Apr 17, 2024EPSS 0.73%

Overview

CVE-2024-26877 is a critical-severity vulnerability. It was published on April 17, 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:

crypto: xilinx - call finalize with bh disabled

When calling crypto_finalize_request, BH should be disabled to avoid

triggering the following calltrace:

------------[ cut here ]------------

WARNING: CPU: 2 PID: 74 at crypto/crypto_engine.c:58 crypto_finalize_request+0xa0/0x118

Modules linked in: cryptodev(O)

CPU: 2 PID: 74 Comm: firmware:zynqmp Tainted: G O 6.8.0-rc1-yocto-standard #323

Hardware name: ZynqMP ZCU102 Rev1.0 (DT)

pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)

pc : crypto_finalize_request+0xa0/0x118

lr : crypto_finalize_request+0x104/0x118

sp : ffffffc085353ce0

x29: ffffffc085353ce0 x28: 0000000000000000 x27: ffffff8808ea8688

x26: ffffffc081715038 x25: 0000000000000000 x24: ffffff880100db00

x23: ffffff880100da80 x22: 0000000000000000 x21: 0000000000000000

x20: ffffff8805b14000 x19: ffffff880100da80 x18: 0000000000010450

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/03e6d4e948432a61b35783323b6ab2be071d2619Refgit.kernel.org/stable/c/23bc89fdce71124cd2126fc919c7076e7cb489cfRefgit.kernel.org/stable/c/8a01335aedc50a66d04dd39203c89f4bc8042596Refgit.kernel.org/stable/c/9db89b1fb85557892e6681724b367287de5f9f20Refgit.kernel.org/stable/c/a71f66bd5f7b9b35a8aaa49e29565eca66299399Refgit.kernel.org/stable/c/a853450bf4c752e664abab0b2fad395b7ad7701cRefgit.kernel.org/stable/c/dbf291d8ffffb70f48286176a15c6c54f0bb0743Refgit.kernel.org/stable/c/03e6d4e948432a61b35783323b6ab2be071d2619Refgit.kernel.org/stable/c/23bc89fdce71124cd2126fc919c7076e7cb489cfRefgit.kernel.org/stable/c/8a01335aedc50a66d04dd39203c89f4bc8042596

How CyberStrike helps

Frequently asked questions

What is CVE-2024-26877?

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

How severe is CVE-2024-26877?

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-26877?

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-26877?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2024-26877 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
LiveWatch live →