Menu

Star on GitHub · 3.2k

CVE-2025-40050

In the Linux kernel, the following vulnerability has been resolved: bpf: Skip scalar adjustment for BPF_NEG if dst is a pointer In check_alu_op(), the verifier currently calls check_reg_arg() and…

Published Oct 28, 2025EPSS 0.22%

Overview

CVE-2025-40050 is a known-severity vulnerability. It was published on October 28, 2025.

Technical description

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

bpf: Skip scalar adjustment for BPF_NEG if dst is a pointer

In check_alu_op(), the verifier currently calls check_reg_arg() and

adjust_scalar_min_max_vals() unconditionally for BPF_NEG operations.

However, if the destination register holds a pointer, these scalar

adjustments are unnecessary and potentially incorrect.

This patch adds a check to skip the adjustment logic when the destination

register contains a pointer.

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

CVE-2025-40050 is a known-severity vulnerability. It was published on October 28, 2025.

How severe is CVE-2025-40050?

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

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

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