CVE-2026-98274

TLS record misclassification via shared PSP-TLS state

Published Oct 6, 2026 · Updated Oct 6, 2026

Protocol-state conflict in Linux 6.18 allows context-dependent attackers to disrupt PSP and TLS handling on TCP sockets using both features. PSP association and TCP ULP setup fail to exclude each other, allowing their transmit-validation callbacks to conflict and giving skb->decrypted incompatible meanings. Exposure requires a PSP-capable NIC and a socket configured for both PSP and TLS; software TLS can mistake a PSP-marked packet for a decrypted TLS record.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Protocol-state conflict in Linux 6.18 allows context-dependent attackers to disrupt PSP and TLS handling on TCP sockets using both features. PSP association and TCP ULP setup fail to exclude each other, allowing their transmit-validation callbacks to conflict and giving skb->decrypted incompatible meanings. Exposure requires a PSP-capable NIC and a socket configured for both PSP and TLS; software TLS can mistake a PSP-marked packet for a decrypted TLS record.

The record

CVE
CVE-2026-98274
Published
Oct 6, 2026
Updated
Oct 6, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
Unavailable
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Oct 6, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 6, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=6.18
  2. Affected versionversion=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a13cca5ba5375f13cbdab545abfb5e288bef3f78
  3. Affected versionversion=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a41f24c612c3f5139a3143307eb85bbcf1bd4d07
  4. Affected versionversion=6b46ca260e2290e3453d1355ab5b6d283d73d780 <c8c8c18862337c469e325c207601de3279847809

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=6.18; version=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a13cca5ba5375f13cbdab545abfb5e288bef3f78; version=6b46ca260e2290e3453d1355ab5b6d283d73d780 <a41f24c612c3f5139a3143307eb85bbcf1bd4d07; version=6b46ca260e2290e3453d1355ab5b6d283d73d780 <c8c8c18862337c469e325c207601de3279847809

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started