← Back to CVE intelligence
CVE intelligence

CVE-2026-98274

Vulnerability intelligence

Published Oct 6, 2026Sources checked Oct 21, 2026
N/ACVSS not listedScore unavailable
What this means

Review the available evidence

CVE-2026-98274. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-98274?

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.

Source: NVD