# CVE-2025-40050: bpf: Skip scalar adjustment for BPF_NEG if dst is a pointer

> A flaw in the Linux kernel BPF verifier allows incorrect scalar adjustments for pointer registers, potentially enabling privilege escalation or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2025-40050, GHSA-p3rp-6995-mvj3, UBUNTU-CVE-2025-40050

## What is CVE-2025-40050?

CVE-2025-40050 is a vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2025-40050?


## How do I fix CVE-2025-40050?

Apply the vendor's patch.

## Is CVE-2025-40050 being exploited?

There is no known exploitation of CVE-2025-40050 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40050 and fix it if it is affected.

What it is: CVE-2025-40050 is a vulnerability in Linux, published on 28 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40050 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40050/ (Markdown: https://insights.sbomify.com/CVE-2025-40050/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40050
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40050
- OSV: https://osv.dev/vulnerability/CVE-2025-40050

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40050/
Summaries are generated and may contain mistakes; the official description above is the record.