How to Fix CVE-2026-43376: Use-After-Free in Linux

Related fixes

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

• How to Fix CVE-2026-43284: Write-what-where Condition in Linux — Write-what-where Condition in Linux
• How to Fix CVE-2026-31599: media: vidtv: fix NULL pointer dereference in Linux — media: vidtv: fix NULL pointer dereference in Linux
• How to Fix CVE-2026-23034: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-31432: ksmbd: fix OOB write in Linux , ksmbd: fix OOB write in Linux
• How to Fix CVE-2026-31422: Security vulnerability in Linux , Security vulnerability in Linux

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-43376 is a use-after-free in Linux from Linux. Upgrade to the patched build named in the Linux advisory. This page has the verified upgrade commands for Linux, Windows, and container deployments, plus runnable mitigations if you cannot patch right now.

What is CVE-2026-43376?

CVE-2026-43376 is a use-after-free in Linux. In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix use-after-free by using call_rcu() for oplock_info

ksmbd currently frees oplock_info immediately using kfree(), even

though it is accessed under RCU read-side critical sections in places

like opinfo_get() and proc_show_files(). Full technical detail is in the vendor advisory and the NVD entry.

Why this CVE matters

The use-after-free class of flaw against Linux is the kind of issue attackers chain into broader access once they get a foothold. Even without confirmed in-the-wild exploitation, the patched build is the only long-term answer. Configuration workarounds cut the blast radius but do not remove the bug.

Am I affected?

Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.

# Linux package check
dpkg -s linux-image-generic 2>/dev/null | grep -i version    # Debian / Ubuntu
rpm -q linux-image-generic 2>/dev/null                       # RHEL / Rocky

How to fix CVE-2026-43376

Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms; adapt the package name and target version to your environment.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade linux-image-generic
dpkg -s linux-image-generic | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh linux-image-generic -y
rpm -q linux-image-generic

Container image

# Vendor advisory: https://git.kernel.org/stable/c/302fef75512b2c8329a3f5efab1ae7ba2562387a
docker pull <your-registry>/linux-image-generic:<patched-tag>
docker build -t <your-app>:patched .
docker stop <your-app> && docker rm <your-app>
docker run -d --name <your-app> <your-app>:patched

PowerShell detect/upgrade/verify/log (Windows)

# CVE-2026-43376 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-43376-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'Linux' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-43376-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Linux' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)

#!/usr/bin/env bash
# CVE-2026-43376 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-43376-fix.log; }

log "Detect: current linux-image-generic version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' linux-image-generic 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' linux-image-generic 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-43376-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/linux-image-generic ] && cp -a /etc/linux-image-generic "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade linux-image-generic
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y linux-image-generic
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y linux-image-generic
fi

log "Verify: re-reading linux-image-generic version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' linux-image-generic)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' linux-image-generic)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: linux-image-generic upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

After the upgrade, restart any service that loads the patched binary so the new code is actually running.

If you can't patch immediately

Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled. They do not remove the vulnerability.

# No vendor-published workaround for CVE-2026-43376 beyond the patch.
# Reduce the blast radius until the patched build is deployed:
#   - Restrict network access to the affected service to known admin hosts
#   - Disable the vulnerable feature in config if the product allows it
#   - Increase logging on the affected endpoints and watch for IoCs

How to verify the fix worked

After applying the patched build, confirm the version string matches the fixed release named in the Linux advisory.

dpkg -s linux-image-generic | grep -i version       # Debian / Ubuntu
rpm -q linux-image-generic                          # RHEL / Rocky

Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-43376. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.

Frequently asked questions

Is CVE-2026-43376 being exploited in the wild?

At time of writing, CVE-2026-43376 is not on CISA's KEV list. Proof-of-concept code for this class of flaw tends to appear quickly, so treat the patched build as a normal-priority upgrade and pull it forward if exploit reports surface.

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

The CVSS base score is 9.8 (Critical). Full vector detail is on the NVD entry.

Will a firewall rule or WAF signature fully mitigate CVE-2026-43376?

No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.

Do I need to assume compromise if the affected service was internet-facing and unpatched?

Not automatically, but log review is cheap insurance. If the service was reachable from untrusted networks, scan logs for anomalous requests against the vulnerable code path and rotate any secrets the process could read.

References

• Official vendor advisory: https://git.kernel.org/stable/c/302fef75512b2c8329a3f5efab1ae7ba2562387a
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-43376
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/08aa9f3c8cf4d0bee44df540dfe34e8d64069f2c
• Additional reference: https://git.kernel.org/stable/c/1d6abf145615dbfe267ce3b0a271f95e3780e18e
• Additional reference: https://git.kernel.org/stable/c/ce8507ee82c888126d8e7565e27c016308d24cde
• Additional reference: https://git.kernel.org/stable/c/1dfd062caa165ec9d7ee0823087930f3ab8a6294

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*