Answer in brief
CVE-2026-98274 records a Unknown severity vulnerability in net: psp: avoid conflicts with skb->decrypted and sk_validate_xmit_skb(). 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.
A CVSS score is not reported in the current record. 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 | >=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a13cca5ba5375f13cbdab545abfb5e288bef3f78 || >=6b46ca260e2290e3453d1355ab5b6d283d73d780 <c8c8c18862337c469e325c207601de3279847809 || >=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a41f24c612c3f5139a3143307eb85bbcf1bd4d07 | a13cca5ba5375f13cbdab545abfb5e288bef3f78, c8c8c18862337c469e325c207601de3279847809, a41f24c612c3f5139a3143307eb85bbcf1bd4d07 |
| Linux/Linuxgeneric | 6.18 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
In the Linux kernel, the following vulnerability has been resolved: net: psp: avoid conflicts with skb->decrypted and sk_validate_xmit_skb() PSP conflicts with TLS ULP in its usage of both skb->decrypted and sk->sk_validate_xmit_skb(). Make PSP mutually exclusive with TLS ULP, the only other user of either of these. As other users of skb->decrypted come along, they can be added to sk_has_decrypt_user(). It would make sense to also assert that sk->sk_validate_xmit_skb() is also NULL in both of these setup paths for similar future proofing, but the PSP listener/sk_clone() path is still broken and it could be seen as a regression to not allow rx assoc to run on a child of a listener socket with PSP tx assoc state. Include all TCP ULPs in the sk_has_decrypt_user() check, even though TLS is the only one that conflicts with PSP via the decrypted bit. This is intentional because PSP was not designed to be used with ULPs. It is best to close off surface area that may make bugs reachable, until someone wishes to design and test an actual user of PSP with ULPs.
Quoted source text, attributed separately from HOL analysis.