How to Fix CVE-2026-31417: Security vulnerability in Linux
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 7.5 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <96fc16370b0bceb289c7e0479bd0540b81e257aa, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <798d613afb64b01a203f448fb0f43c37c6afe79d, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <6e568835ea54a3e1d08e310e34f95d434e739477, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <1734bd85c5e0a7a801295b729efb56b009cb8fc3, 1da177e4c3f41524e886b7f... |
| Fixed in | Linux 96fc16370b0bceb289c7e0479bd0540b81e257aa; Linux 798d613afb64b01a203f448fb0f43c37c6afe79d; Linux 6e568835ea54a3e1d08e310e34f95d434e739477; Linux 1734bd85c5e0a7a801295b729efb56b009cb8fc3 (and 4 more SKUs, see vendor advisory) |
| Type (CWE) | Not verified, see official advisory |
What is CVE-2026-31417?
In the Linux kernel, the following vulnerability has been resolved: net/x25: Fix overflow when accumulating packets Add a check to ensure that x25_sock.fraglen does not overflow. The fraglen also needs to be resetted when purging fragment_queue in x25_clear_queues().
Am I affected?
Run the version check that matches your platform:
# Linux
dpkg -s linux-image-generic 2>/dev/null | grep -i version
rpm -q linux-image-generic 2>/dev/null
linux-image-generic --version 2>/dev/null
Compare what you see against the Affected row above (Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <96fc16370b0bceb289c7e0479bd0540b81e257aa, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <798d613afb64b01a203f448fb0f43c37c6afe79d, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <6e568835ea54a3e1d08e310e34f95d434e739477, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 to <1734bd85c5e0a7a801295b729efb56b009cb8fc3, 1da177e4c3f41524e886b7f...). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-31417
The primary fix is to upgrade Linux to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: Linux 96fc16370b0bceb289c7e0479bd0540b81e257aa; Linux 798d613afb64b01a203f448fb0f43c37c6afe79d; Linux 6e568835ea54a3e1d08e310e34f95d434e739477; Linux 1734bd85c5e0a7a801295b729efb56b009cb8fc3 (and 4 more SKUs, see vendor advisory).
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade linux-image-generic
linux-image-generic --version 2>/dev/null || dpkg -s linux-image-generic | grep -i version
RHEL / CentOS / Rocky / AlmaLinux
sudo dnf upgrade --security linux-image-generic -y
rpm -q linux-image-generic
SUSE / openSUSE
sudo zypper patch --category security
rpm -q linux-image-generic
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-31417 affecting Linux kernel
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-31417-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] Detecting installed version of Linux kernel"
$pkg = winget list --id "Linux_kernel" 2>$null
Write-Host $pkg
Write-Host "[2/4] Backing up configuration"
$backup = "C:\Backup\Linux_kernel-$(Get-Date -Format yyyyMMdd)"
New-Item -ItemType Directory -Force $backup | Out-Null
Get-ChildItem "C:\ProgramData\Linux_kernel" -ErrorAction SilentlyContinue |
Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue
Write-Host "[3/4] Applying upgrade to Linux 96fc16370b0bceb289c7e0479bd0540b81e257aa; Linux 798d613afb64b01a203f448..."
winget upgrade --id "Linux_kernel" --silent --accept-source-agreements --accept-package-agreements
# Fallback: Windows Update for OS-level fixes
if ($LASTEXITCODE -ne 0) {
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
Import-Module PSWindowsUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
}
Write-Host "[4/4] Verifying patched build"
winget list --id "Linux_kernel"
Write-Host "Fix 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-31417 affecting Linux kernel
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-31417-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1
echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
dpkg -s linux-image-generic 2>/dev/null | grep -i version || echo "linux-image-generic not installed via dpkg"
elif command -v rpm >/dev/null; then
rpm -q linux-image-generic || echo "linux-image-generic not installed via rpm"
fi
echo "[2/4] Backing up configuration"
BACKUP="/root/backup-cve-2026-31417-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/linux-image-generic /etc/linux-image-generic.d /etc/linux-image-generic.conf; do
[ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done
echo "[3/4] Applying upgrade (target: Linux 96fc16370b0bceb289c7e0479bd0540b81e257aa; Linux 798d613afb64b01a203f448...)"
if command -v apt-get >/dev/null; then
apt-get update
apt-get install --only-upgrade -y linux-image-generic
elif command -v dnf >/dev/null; then
dnf upgrade --security -y linux-image-generic
elif command -v yum >/dev/null; then
yum update -y linux-image-generic
elif command -v zypper >/dev/null; then
zypper --non-interactive patch --category security
fi
echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
dpkg -s linux-image-generic 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
rpm -q linux-image-generic
fi
echo "Done. Restart any running daemons that loaded the old library."
If you can't patch immediately
If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.
Network restriction (Linux, nftables)
# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset
Service-level fallback
# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop linux-image-generic
sudo systemctl disable linux-image-generic
How to verify the fix worked
# Linux
linux-image-generic --version 2>/dev/null || dpkg -s linux-image-generic | grep -i version
rpm -q linux-image-generic 2>/dev/null || true
# Windows
winget list | findstr /I "linux-image-generic"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
Expected: the reported version is at or above Linux 96fc16370b0bceb289c7e0479bd0540b81e257aa; Linux 798d613afb64b01a203f448fb0f43c37c6afe79d; Linux 6e568835ea54a3e1d08e310e34f95d434e739477; Linux 1734bd85c5e0a7a801295b729efb56b009cb8fc3 (and 4 more SKUs, see vendor advisory). Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.
Frequently asked questions
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-23408: Linux (Bundle Sibling) — Linux (Bundle Sibling)
- How to Fix CVE-2026-43433: Security Vulnerability in Linux — Security Vulnerability in Linux
- How to Fix CVE-2026-43166: Security Vulnerability in Linux , Security Vulnerability in Linux
- How to Fix CVE-2026-23385: Critical Vulnerability in Linux , Critical Vulnerability in Linux
- How to Fix CVE-2026-31657: batman-adv: hold claim backbone gateways by reference in Linux , batman-adv: hold claim backbone gateways by reference in Linux
Is CVE-2026-31417 actually being exploited?
According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.
Do I need to reboot after patching?
For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.
What is the CVSS score?
7.5 (high). Refer to the vendor advisory for the exact vector string.
Where is the official advisory?
See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.
References
- Official vendor advisory: https://git.kernel.org/stable/c/96fc16370b0bceb289c7e0479bd0540b81e257aa
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31417
- https://git.kernel.org/stable/c/798d613afb64b01a203f448fb0f43c37c6afe79d
- https://git.kernel.org/stable/c/6e568835ea54a3e1d08e310e34f95d434e739477
- https://git.kernel.org/stable/c/1734bd85c5e0a7a801295b729efb56b009cb8fc3
- https://git.kernel.org/stable/c/4e2d1bcef78d21247fe8fef13bc7ed95885df2b5
*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.*