# CVE-2025-65566: Null dereference in n/a

> An attacker can crash the UPF process by sending malformed PFCP messages, causing a denial of service for user-plane services.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-qxmc-xmp5-2rhf

## What is CVE-2025-65566?

CVE-2025-65566 is a high-severity vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A denial-of-service vulnerability exists in the omec-project UPF (pfcpiface component) in version upf-epc-pfcpiface:2.1.3-dev. When the UPF receives a PFCP Session Report Response that is missing the mandatory Cause Information Element, the session report handler dereferences a nil pointer instead of rejecting the malformed message. This triggers a panic and terminates the UPF process. An attacker who can send PFCP Session Report Response messages to the UPF's N4/PFCP endpoint can exploit this flaw to repeatedly crash the UPF and disrupt user-plane services.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linuxfoundation Upf.

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

No fix has been published for CVE-2025-65566 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-65566 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65566 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65566 is a high-severity vulnerability in n/a, published on 18 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65566 exists.

Affected product: n/a. 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-65566/ (Markdown: https://insights.sbomify.com/CVE-2025-65566/index.md)
```

## Sources

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

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