Revert "net/smc: Introduce TCP ULP support"
CVE-2026-46330 · published 9 Jun 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-46330?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: d7cd421da9da2cc7b4d25b8537f66db5c8331c40 to < 74d33525db50d9d95156c79cc874752654e66e70, d7cd421da9da2cc7b4d25b8537f66db5c8331c40 to < dc824ffc28e5c9d0020b6bee2651b4aceed5b2bf, d7cd421da9da2cc7b4d25b8537f66db5c8331c40 to < dc24e03be0e4bb2aad1a9b272c4f86de3b11969a, d7cd421da9da2cc7b4d25b8537f66db5c8331c40 to < 6c505d95c69e27dbf28fea29dc84d2498d69515c
- Linux Linux: 5.17
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
Revert "net/smc: Introduce TCP ULP support"
This reverts commit d7cd421da9da2cc7b4d25b8537f66db5c8331c40.
As reported by Al Viro, the TCP ULP support for SMC is fundamentally
broken. The implementation attempts to convert an active TCP socket
into an SMC socket by modifying the underlying `struct file`, dentry,
and inode in-place, which violates core VFS invariants that assume
these structures are immutable for an open file, creating a risk of
use after free errors and general system instability.
Given the severity of this design flaw and the fact that cleaner
alternatives (e.g., LD_PRELOAD, BPF) exist for legacy application
transparency, the correct course of action is to remove this feature
entirely.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/74d33525db50d9d95156c79cc874752654e66e70
- git.kernel.org/stable/c/dc824ffc28e5c9d0020b6bee2651b4aceed5b2bf
- git.kernel.org/stable/c/dc24e03be0e4bb2aad1a9b272c4f86de3b11969a
- git.kernel.org/stable/c/6c505d95c69e27dbf28fea29dc84d2498d69515c
- git.kernel.org/stable/c/df31a6b0a3057e66994ad6ccf5d95b9b9514f033
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON