NULL Pointer Dereference Affecting github.com/free5gc/smf/internal/pfcp/handler package, versions <1.4.2
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-GOLANG-GITHUBCOMFREE5GCSMFINTERNALPFCPHANDLER-15364907
- published28 Feb 2026
- disclosed24 Feb 2026
- creditZiyu Lin
Introduced: 24 Feb 2026
CVE-2026-25501 (opens in a new tab)How to fix?
Upgrade github.com/free5gc/smf/internal/pfcp/handler to version 1.4.2 or higher.
Overview
Affected versions of this package are vulnerable to NULL Pointer Dereference via the PFCP SessionReportRequest process when ReportType.DLDR is set but the DownlinkDataReport information element is missing. An attacker can cause the process to terminate unexpectedly by sending a specially crafted PFCP message to the SMF PFCP (UDP/8805) interface.
Workaround
This vulnerability can be mitigated by restricting access to the PFCP interface using ACLs or firewalls to allow only trusted UPF IPs, inspecting or dropping malformed PFCP SessionReportRequest messages at the network edge, or adding recover() around PFCP handler dispatch to prevent whole-process termination.