Description
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.
Published: 2026-10-06
Score: n/a
EPSS: < 1% Very Low
KEV: No
Impact: Potential incorrect packet handling due to conflicting internal state between PSP and TLS ULP
Action: Immediate patch
AI Analysis

Impact

The Linux kernel had a conflict between the Private Socket Protocol (PSP) and TLS User-Defined Protocol Layer (TLS ULP) in their use of shared state variables: the skb->decrypted flag and the sk_validate_xmit_skb() pointer. Because these components were not mutually exclusive, the kernel could incorrectly validate packets when both PSP and TLS ULP were present. The change makes PSP mutually exclusive with TLS ULP, ensures proper initialization of these state variables, and closes off surface area that might otherwise expose bugs.

Affected Systems

This issue impacts all Linux kernel users that are running a kernel build prior to the commit that introduces PSP/TLS ULP conflict remediation. Versions of the kernel compiled with PSP support and TLS ULP enabled are affected, regardless of distribution or kernel variant.

Risk and Exploitability

The EPSS score of <1% indicates a very low likelihood of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The flaw involves shared state used during packet validation between PSP and TLS ULP. Based on the description, it is inferred that an attacker who can send crafted network traffic to a socket that has both PSP and TLS ULP enabled might be able to trigger a misvalidation or crash, implying a possible network-based attack vector. While no exploit has been documented, the low exploitation probability and absence of public vulnerability reports suggest the overall risk remains low, although applying the patch removes the potential for incorrect packet handling.

Generated by OpenCVE AI on October 7, 2026 at 05:49 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update the Linux kernel to a build that includes the PSP/TLS ULP conflict remediation commit (for example, the patch referenced by commit a13cca5 or a41f24c).
  • If custom PSP or TLS ULP modules are in use, temporarily disable or unload them until the kernel update is applied.
  • After applying the fix, monitor system logs for socket validation errors or abnormal packet drops that may indicate residual issues.

Generated by OpenCVE AI on October 7, 2026 at 05:49 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 07 Oct 2026 06:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Wed, 07 Oct 2026 04:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Tue, 06 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-665

Tue, 06 Oct 2026 09:00:00 +0000

Type Values Removed Values Added
Description 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.
Title net: psp: avoid conflicts with skb->decrypted and sk_validate_xmit_skb()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-10-19T09:16:45.903Z

Reserved: 2026-09-25T10:25:14.334Z

Link: CVE-2026-98274

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-06T09:18:17.077

Modified: 2026-10-19T10:18:28.740

Link: CVE-2026-98274

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-07T06:00:08Z

Weaknesses