How to Fix CVE-2026-43314: Security Vulnerability in Linux

Related fixes

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

• How to Fix CVE-2026-31579: wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in Linux — wireguard: device: use exit_rtnl callback instead of manual rtnl_lock in Linux
• How to Fix CVE-2026-23307: Critical Vulnerability in Linux — Critical Vulnerability in Linux
• How to Fix CVE-2026-43175: Security Vulnerability in Linux , Security Vulnerability in Linux
• How to Fix CVE-2026-23144: Critical Vulnerability in Linux , Critical Vulnerability in Linux
• How to Fix CVE-2026-31472: xfrm: iptfs: validate inner IPv4 header length in Linux , xfrm: iptfs: validate inner IPv4 header length in Linux

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-43314 is a security vulnerability 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-43314?

CVE-2026-43314 is a security vulnerability in Linux. In the Linux kernel, the following vulnerability has been resolved:

dm: remove fake timeout to avoid leak request

Since commit 15f73f5b3e59 ("blk-mq: move failure injection out of

blk_mq_complete_request"), drivers are responsible for calling

blk_should_fake_timeout() at appropriate code paths and opportunities. Full technical detail is in the vendor advisory and the NVD entry.

Why this CVE matters

The security vulnerability 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

# Network appliance CLI
show version    # then compare against the 'Affected' row above

How to fix CVE-2026-43314

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.

Network appliance CLI

# Vendor advisory: https://git.kernel.org/stable/c/ece6720de9403260088209b0b92d45e0b49ff856
# 1. Confirm the running firmware
show version

# 2. Download the patched image from the vendor support portal, verify SHA256
sha256sum <patched-image>

# 3. Apply via vendor upgrade procedure (TFTP/SCP/USB)
# 4. Reboot, then re-run the version command to confirm the patched build loaded

PowerShell detect/upgrade/verify/log (Windows)

# CVE-2026-43314 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-43314-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-43314-$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-43314 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-43314-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-43314-$(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.

Restrict network exposure (iptables / nftables)

# Replace 10.0.0.0/8 with your management network.
sudo iptables -I INPUT -p tcp --dport 443 -s 10.0.0.0/8 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4

# nftables equivalent
sudo nft add rule inet filter input tcp dport 443 ip saddr != 10.0.0.0/8 drop

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-43314. 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-43314 being exploited in the wild?

At time of writing, CVE-2026-43314 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-43314?

The vendor record does not include a CVSS score yet. Check the NVD entry for the analyst score once it lands.

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

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/ece6720de9403260088209b0b92d45e0b49ff856
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-43314
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Additional reference: https://git.kernel.org/stable/c/8200fca818c1e2f65bc6cb16d934ff6049302197
• Additional reference: https://git.kernel.org/stable/c/b307b6307f6459841312432bd4bc9519cbac97f5
• Additional reference: https://git.kernel.org/stable/c/4f9e7ca933a9fbf9912a384b061a00c77332cbf0
• Additional reference: https://git.kernel.org/stable/c/cf2d06c9fd4b6521ea5b7f73c99c64c2c6f5e224

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