Menu

Star on GitHub · 3.2k

CVE-2025-40022

In the Linux kernel, the following vulnerability has been resolved: crypto: af_alg - Fix incorrect boolean values in af_alg_ctx Commit 1b34cbbf4f01 ("crypto: af_alg - Disallow concurrent writes i…

Published Oct 24, 2025EPSS 0.24%

Overview

CVE-2025-40022 is a known-severity vulnerability. It was published on October 24, 2025.

Technical description

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

crypto: af_alg - Fix incorrect boolean values in af_alg_ctx

Commit 1b34cbbf4f01 ("crypto: af_alg - Disallow concurrent writes in

af_alg_sendmsg") changed some fields from bool to 1-bit bitfields of

type u32.

However, some assignments to these fields, specifically 'more' and

'merge', assign values greater than 1. These relied on C's implicit

conversion to bool, such that zero becomes false and nonzero becomes

true.

With a 1-bit bitfields of type u32 instead, mod 2 of the value is taken

instead, resulting in 0 being assigned in some cases when 1 was intended.

Fix this by restoring the bool type.

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.

Frequently asked questions

What is CVE-2025-40022?

CVE-2025-40022 is a known-severity vulnerability. It was published on October 24, 2025.

How severe is CVE-2025-40022?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2025-40022?

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-2025-40022?

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