How to Fix CVE-2026-31507: net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-23410: Linux (Bundle Sibling) — Linux (Bundle Sibling)
- How to Fix CVE-2026-23263: io_uring/zcrx: fix page array leak in Linux — io_uring/zcrx: fix page array leak in Linux
- How to Fix CVE-2026-23218: Critical Vulnerability in Linux , Critical Vulnerability in Linux
- How to Fix CVE-2026-31591: KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish in Linux , KVM: SEV: Lock all vCPUs when synchronzing VMSAs for SNP launch finish in Linux
- How to Fix CVE-2026-31543: crash_dump: don't log dm-crypt key bytes in Linux , crash_dump: don't log dm-crypt key bytes in Linux
Last verified: 2026-05-25
CVE-2026-31507 is a net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer in Linux Linux. Fix it by upgrading to 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.
| Severity | CVSS 7.8 - High |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) 7e8916f46c2f48607f907fd401590093753a6bc5; Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) ae5575e660410c8d2c5d38fb28a0f37aea945676; Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) 98ba5cb274768146e25ffbfde47753652c1c20d3; Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) 81acbd345d405994875d419d43b319fee0b9ad62; Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) 7bcb974c771c863e8588cea0012ac204443a7126; Linux 9014db202cb764b8e14c53e7bacc81f9a1a2ba7f up to (excluding) 54c87a730157868543ebdfa0ecb21b4590ed23a5 |
| Fixed in | 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21 |
| Type (CWE) | Not verified |
What is CVE-2026-31507?
CVE-2026-31507 is a net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer flaw in Linux Linux. It carries a CVSS base score of 7.8 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: In the Linux kernel, the following vulnerability has been resolved:
net/smc: fix double-free of smc_spd_priv when tee() duplicates splice pipe buffer
smc_rx_splice() allocates one smc_spd_priv per pipe_buffer and stores
the pointer in pipe_buffer.private. The pipe_buf_operations for these
buffers used .get = generic_pipe_buf_get, which only increments the page
reference count when tee(2) duplicates a pipe buffer. The smc_spd_priv
pointer itself was not handled, so after tee() both the original and the
cloned pipe_buffer share the same smc_spd_priv *.
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of Linux matches a version listed in the Affected row above.
# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux
How to fix CVE-2026-31507
Apply the vendor patch. Target the build named in the Fixed in row above (5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21). The runnable command set below covers the most common deployment patterns for Linux.
Ubuntu / Debian
sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version
RHEL / CentOS / Rocky
sudo dnf upgrade linux -y
rpm -q linux
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux
Expected: a version at or above 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-31507 being exploited in the wild?
As of 2026-05-25, CVE-2026-31507 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-31507?
The CVSS base score is 7.8 (High).
What version fixes this?
Upgrade to 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://git.kernel.org/stable/c/7e8916f46c2f48607f907fd401590093753a6bc5
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-31507
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://git.kernel.org/stable/c/ae5575e660410c8d2c5d38fb28a0f37aea945676
- Additional reference: https://git.kernel.org/stable/c/98ba5cb274768146e25ffbfde47753652c1c20d3
- Additional reference: https://git.kernel.org/stable/c/81acbd345d405994875d419d43b319fee0b9ad62
- Additional reference: https://git.kernel.org/stable/c/7bcb974c771c863e8588cea0012ac204443a7126
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*