# CVE-2026-98274: net: psp: avoid conflicts with skb->decrypted and sk_validate_xmit_skb()

> A logic conflict in the Linux kernel PSP implementation with TLS ULP could lead to undefined behavior, requiring specific network configurations to exploit.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98274, DEBIAN-CVE-2026-98274, GHSA-566p-8rmw-5xmj, UBUNTU-CVE-2026-98274

## What is CVE-2026-98274?

CVE-2026-98274 is a vulnerability in Linux, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98274?


## How do I fix CVE-2026-98274?

Apply the vendor's patch.

## Is CVE-2026-98274 being exploited?

There is no known exploitation of CVE-2026-98274 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98274 and fix it if it is affected.

What it is: CVE-2026-98274 is a vulnerability in Linux, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98274 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98274/ (Markdown: https://insights.sbomify.com/CVE-2026-98274/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98274
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98274
- OSV: https://osv.dev/vulnerability/CVE-2026-98274

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98274/
Summaries are generated and may contain mistakes; the official description above is the record.