How to Fix CVE-2026-23237: Security vulnerability in Linux

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

CVE-2026-23237 is a security vulnerability in Linux Linux. The fix is to upgrade to Linux 0; Linux 5.10.251; Linux 5.15.201; Linux 6.1.164; Linux 6.12.74; Linux 6.18.13.

What is CVE-2026-23237?

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: classmate-laptop: Add missing NULL pointer checks

In a few places in the Classmate laptop driver, code using the accel

object may run before that object's address is stored in the driver

data of the input device using it.

For example, cmpc_accel_sensitivity_store_v4() is the "show" method

of cmpc_accel_sensitivity_attr_v4 which is added in cmpc_accel_add_v4(),

before calling dev_set_drvdata() for inputdev->dev. If the sysfs

attribute is accessed prematurely, the dev_get_drvdata(&inputdev->dev)

call in in cmpc_accel_sensitivity_store_v4() returns NULL which

leads to a NULL pointer dereference going forward.

sysfs attributes using the input device are added before

initializing that device by cmpc_add_acpi_notify_device() and if one

of them is accessed before running that function, a NULL pointer

dereference will occur.

For example, cmpc_accel_sensitivity_attr_v4 is added before calling

cmpc_add_acpi_notify_device() and if it is read prematurely, the

dev_get_drvdata(&acpi->dev) call in cmpc_accel_sensitivity_show_v4()

returns NULL which leads to a NULL pointer dereference going forward.

Fix this by adding NULL pointer checks in all of the relevant places. The official advisory is at https://git.kernel.org/stable/c/993708fc18d0d0919db438361b4e8c1f980a8d1b.

Am I affected?

Check the version of Linux you are running and compare it against the Affected row above (Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <993708fc18d0d0919db438361b4e8c1f980a8d1b; Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <af673209d43b46257540997aba042b90ef3258c0; Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <eb214804f03c829decf10998e9b7dd26f4c8ab9e; Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <9cf4b9b8ad09d6e05307abc4e951cabdff4be652; Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <da6e06a5fdbabea3870d18c227734b5dea5b3be6; Linux 529aa8cb0a59367d08883f818e8c47028e819d0d to <97528b1622b8f129574d29a571c32a3c85eafa3c). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

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

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

How to fix CVE-2026-23237

Upgrade Linux to a patched build: Linux 0; Linux 5.10.251; Linux 5.15.201; Linux 6.1.164; Linux 6.12.74; Linux 6.18.13. 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 linux
dpkg -s linux | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

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

SUSE / openSUSE

sudo zypper refresh
sudo zypper update linux
rpm -q linux

Node.js / npm

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

Complete PowerShell remediation script (Windows)

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

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-23237-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 "*Linux*" -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\linux-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Linux" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to Linux 0; Linux 5.10.251; Linux 5.15.201; Linux 6.1.164; Linux 6.12.74; Linux 6.18.13"
    winget upgrade --name "Linux" --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 "Linux"
    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-23237 affecting Linux
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-23237-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 linux 2>/dev/null | grep -i ^Version || echo "linux not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q linux || echo "linux not installed via rpm"
fi

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

echo "[3/4] Apply the upgrade (target: Linux 0; Linux 5.10.251; Linux 5.15.201; Linux 6.1.164; Linux 6.12.74; Linux 6.18.13)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y linux
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y linux
elif command -v yum >/dev/null; then
    yum update -y linux
elif command -v zypper >/dev/null; then
    zypper --non-interactive update linux
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s linux 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q linux
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-23237" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-23237"

Disable the affected service (Linux)

sudo systemctl stop linux 2>/dev/null || true
sudo systemctl disable linux 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 linux 2>/dev/null | grep -i ^Version
rpm -q linux 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 "*Linux*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Linux 0; Linux 5.10.251; Linux 5.15.201; Linux 6.1.164; Linux 6.12.74; Linux 6.18.13. 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-43408: Race Condition in Linux — Race Condition in Linux
• How to Fix CVE-2026-31696: rxrpc: Fix missing validation of ticket length in Linux — rxrpc: Fix missing validation of ticket length in Linux
• How to Fix CVE-2026-43165: Security Vulnerability in Linux , Security Vulnerability in Linux
• How to Fix CVE-2026-23195: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-23077: Critical Vulnerability in Linux , Critical Vulnerability in Linux

Is CVE-2026-23237 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-23237?

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-23237?

Not published in the verified data we ingested. Check the NVD entry linked in the References section for the latest score.

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

The vendor advisory is at https://git.kernel.org/stable/c/993708fc18d0d0919db438361b4e8c1f980a8d1b. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-23237.

References

• Official vendor advisory: https://git.kernel.org/stable/c/993708fc18d0d0919db438361b4e8c1f980a8d1b
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23237
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/af673209d43b46257540997aba042b90ef3258c0
• Additional reference: https://git.kernel.org/stable/c/eb214804f03c829decf10998e9b7dd26f4c8ab9e
• Additional reference: https://git.kernel.org/stable/c/9cf4b9b8ad09d6e05307abc4e951cabdff4be652

*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.*