How to Fix CVE-2026-1584: Null pointer dereference in Red Hat Enterprise Linux 10
By Sai Kiran Pandrala. Last verified: 2026-05-25.
| Severity | 7.5 (High) |
|---|---|
| Actively exploited? | No public listing in CISA KEV |
| Affected | Red Hat |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-476: NULL Pointer Dereference |
What is CVE-2026-1584?
A flaw was found in gnutls. A remote, unauthenticated attacker can exploit this vulnerability by sending a specially crafted ClientHello message with an invalid Pre-Shared Key (PSK) binder value during the TLS handshake. This can lead to a NULL pointer dereference, causing the server to crash and resulting in a remote Denial of Service (DoS) condition.
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 (Red Hat). If your build sits inside that range, you are exposed and should patch.
How to fix CVE-2026-1584
The primary fix is to upgrade Red Hat Enterprise Linux 10 to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: 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
Docker / Kubernetes
# Vendor advisory: https://access.redhat.com/errata/RHSA-2026:7477
# Pull the patched image
docker pull linuxkernel:latest
# Or pin to the patched tag from the vendor's registry
# Rolling update in Kubernetes
kubectl set image deployment/linuxkernel linuxkernel=linuxkernel:<patched-tag>
kubectl rollout status deployment/linuxkernel
Complete PowerShell remediation script (Windows)
# Fix script for CVE-2026-1584 affecting Linux kernel
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.
$ErrorActionPreference = "Stop"
$LogPath = "C:\Logs\CVE-2026-1584-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 latest"
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-1584 affecting Linux kernel
# Detect -> backup -> upgrade -> verify -> log.
set -euo pipefail
LOG="/var/log/cve-2026-1584-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-1584-$(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: latest)"
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 the patched build documented in the 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-43466: Security Vulnerability in Linux — Security Vulnerability in Linux
- How to Fix CVE-2026-23000: Critical Vulnerability in Linux — Critical Vulnerability in Linux
- How to Fix CVE-2026-31779: wifi: iwlwifi: mvm: fix potential out-of-bounds read in Linux , wifi: iwlwifi: mvm: fix potential out-of-bounds read in Linux
- How to Fix CVE-2026-23230: Critical Vulnerability in Linux , Critical Vulnerability in Linux
- How to Fix CVE-2026-23107: Critical Vulnerability in Linux , Critical Vulnerability in Linux
Is CVE-2026-1584 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://access.redhat.com/errata/RHSA-2026:7477
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1584
- https://access.redhat.com/security/cve/CVE-2026-1584
- https://bugzilla.redhat.com/show_bug.cgi?id=2435258
*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.*