● Not verified

How to Fix CVE-2026-43502: Critical Vulnerability in Linux

Q: Is CVE-2026-43502 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-43502?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Linux run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

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

How to Fix CVE-2026-31546: net: bonding: fix NULL deref in Linux — net: bonding: fix NULL deref in Linux
How to Fix CVE-2026-31752: bridge: br_nd_send: validate ND option lengths in Linux — bridge: br_nd_send: validate ND option lengths in Linux
How to Fix CVE-2026-43424: Null Pointer Dereference in Linux , Null Pointer Dereference in Linux
How to Fix CVE-2026-31488: drm/amd/display: Do not skip unrelated mode changes in Linux , drm/amd/display: Do not skip unrelated mode changes in Linux
How to Fix CVE-2026-43296: Security Vulnerability in Linux , Security Vulnerability in Linux

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	Not verified - see advisory
Actively exploited?	Not currently listed in CISA KEV
Affected	0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 3abc8983b2bae3f487f77d9da5527d7d6b210d46, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 14ef6fd18db2494098b21e0471bf27a1d8e9993e, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b, 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 44b550d88b267320459d518c0743a241ab2108fa, 4.17
Fixed in	0, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1-rc3
Type (CWE)	Not verified

What is CVE-2026-43502?

CVE-2026-43502 is a security flaw in Linux. In the Linux kernel, the following vulnerability has been resolved: net/rds: handle zerocopy send cleanup before the message is queued A zerocopy send can fail after user pages have been pinned but before the message is attached to the sending socket. The purge path currently infers zerocopy state from rm->m_rs, so an unqueued message can be cleaned up as if it owned normal payload pages.

Why this CVE matters

Unpatched network-facing software is the leading initial-access vector in public breach reporting. Treat any CVSS-9 class flaw on an internet-reachable system as urgent, regardless of whether public exploit code has been observed yet.

For deployments of Linux that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e
Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 3abc8983b2bae3f487f77d9da5527d7d6b210d46
Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 14ef6fd18db2494098b21e0471bf27a1d8e9993e
Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 0f5c185fc79a59ee9991234dd6d2a3e5afa6e75b
Linux: 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 44b550d88b267320459d518c0743a241ab2108fa
Linux: 4.17

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Run uname -r to read the kernel release. Compare against the affected ranges; on distro kernels, also check the package version with dpkg -l linux-image-$(uname -r) or rpm -q kernel.

How to fix CVE-2026-43502

Read the vendor advisory in full: https://git.kernel.org/stable/c/21d70744e6d3bbf9293aa1ee6fba7c53ad75275e
Upgrade Linux to 0, 6.6.140, 6.12.88, 6.18.30, 7.0.7, 7.1-rc3 or a later version listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Patch via the OS package manager


# CVE-2026-43502 affects Linux 0cebaccef3acbdfbc2d85880a2efb765d2f4e2e3 < 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e. Fixed in 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e.
# Vendor advisory: https://git.kernel.org/stable/c/21d70744e6d3bbf9293aa1ee6fba7c53ad75275e

# Debian / Ubuntu
sudo apt update
sudo apt install --only-upgrade linux

# RHEL / Rocky / AlmaLinux / Fedora
sudo dnf upgrade linux

# openSUSE
sudo zypper update linux

# Alpine
sudo apk upgrade linux

# Verify the running version against 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e.
dpkg -s linux 2>/dev/null | grep -i version || rpm -q linux 2>/dev/null || apk info -v linux


# Re-runnable bash remediation script.
#!/usr/bin/env bash
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-43502-fix.log; }
log "Detecting current linux version"
if command -v dpkg >/dev/null 2>&1; then
    before=$(dpkg-query -W -f='${Version}' linux 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    before=$(rpm -q linux 2>/dev/null || echo "not-installed")
fi
log "Before: $before"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq && sudo apt-get install -y --only-upgrade linux
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y linux
fi
log "Verifying patched version matches 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e"
if command -v dpkg >/dev/null 2>&1; then
    dpkg-query -W -f='${Version}' linux
else
    rpm -q linux
fi

Verify the fix landed


# CVE-2026-43502 verification checklist.

# 1. Confirm the running version matches 21d70744e6d3bbf9293aa1ee6fba7c53ad75275e (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-43502.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://git.kernel.org/stable/c/21d70744e6d3bbf9293aa1ee6fba7c53ad75275e

If you cannot patch immediately

No official workaround exists beyond restricting network exposure to the affected component. Apply the vendor patch as the primary remediation.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-43502.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

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