Answer in brief
CVE-2026-46330 records a High severity (CVSS 7.8) vulnerability in Revert "net/smc: Introduce TCP ULP support". The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d7cd421da9da2cc7b4d25b8537f66db5c8331c40 <6c505d95c69e27dbf28fea29dc84d2498d69515c || >=d7cd421da9da2cc7b4d25b8537f66db5c8331c40 <df31a6b0a3057e66994ad6ccf5d95b9b9514f033 | 6c505d95c69e27dbf28fea29dc84d2498d69515c, df31a6b0a3057e66994ad6ccf5d95b9b9514f033 |
| Linux/Linuxgeneric | 5.17 | Not reported |
Published upstream
Jun 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 7, 2026
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.
Quoted source text, attributed separately from HOL analysis.