How to Fix CVE-2026-25501: Null pointer dereference in smf

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-25501 is a null pointer dereference in free5gc smf. The fix is to apply the vendor patch noted below.

What is CVE-2026-25501?

free5GC SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics due to nil pointer dereference and the SMF process terminates. This is triggered by a malformed PFCP SessionReportRequest on the SMF PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only). The CVSS base score is 6.6 (Medium). The official advisory is at https://github.com/free5gc/free5gc/security/advisories/GHSA-vq85-8f6p-g9q5.

Am I affected?

Check the version of smf you are running and compare it against the Affected row above (smf <= 1.4.1). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

# Linux package check
dpkg -s smf 2>/dev/null | grep -i ^Version
rpm -q smf 2>/dev/null
command -v smf >/dev/null && smf --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*smf*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "smf" 2>$null

How to fix CVE-2026-25501

Upgrade smf to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade smf
dpkg -s smf | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh smf -y
# or for older releases:
sudo yum update smf -y
rpm -q smf

SUSE / openSUSE

sudo zypper refresh
sudo zypper update smf
rpm -q smf

Node.js / npm

# Update the affected package in your project
npm install smf@latest
npm ls smf
npm audit fix

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-25501 affecting smf
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-25501-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*smf*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\smf-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\smf" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "smf" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "smf"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)

#!/usr/bin/env bash
# Fix script for CVE-2026-25501 affecting smf
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-25501-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s smf 2>/dev/null | grep -i ^Version || echo "smf not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q smf || echo "smf not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-25501-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/smf /etc/smf.d /etc/smf.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y smf
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y smf
elif command -v yum >/dev/null; then
    yum update -y smf
elif command -v zypper >/dev/null; then
    zypper --non-interactive update smf
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s smf 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q smf
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)

# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)

New-NetFirewallRule -DisplayName "Block-CVE-2026-25501" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-25501"

Disable the affected service (Linux)

sudo systemctl stop smf 2>/dev/null || true
sudo systemctl disable smf 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.

# Linux
dpkg -s smf 2>/dev/null | grep -i ^Version
rpm -q smf 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true

# Windows
Get-Package -Name "*smf*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-23737: Deserialization RCE in seroval — Deserialization RCE in seroval
• How to Fix CVE-2026-6474: Format String Flaw in PostgreSQL — Format String Flaw in PostgreSQL
• How to Fix CVE-2026-41056: Cwe-942: permissive cross-domain policy with untrusted in AVideo , Cwe-942: permissive cross-domain policy with untrusted in AVideo
• How to Fix CVE-2026-2480: WP Shortcodes Plugin, Shortcodes Ultimate (Bundle Sibling) , WP Shortcodes Plugin, Shortcodes Ultimate (Bundle Sibling)
• How to Fix CVE-2026-0780: Command Injection in 8180 IP Audio Alerter , Command Injection in 8180 IP Audio Alerter

Is CVE-2026-25501 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-25501?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-25501?

6.6 (Medium). Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U.

Where is the official advisory for CVE-2026-25501?

The vendor advisory is at https://github.com/free5gc/free5gc/security/advisories/GHSA-vq85-8f6p-g9q5. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-25501.

References

• Official vendor advisory: https://github.com/free5gc/free5gc/security/advisories/GHSA-vq85-8f6p-g9q5
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25501
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://github.com/free5gc/free5gc/issues/805

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*