CVE-2026-98274

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

References (3)

Vendor Advisories for CVE-2026-98274(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version up to 7.2.8-1: fixed in 7.2.8-1
—

Data Freshness Timeline

(refreshed 14× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 14:38 UTCEG score recompute
  4. 2026-10-11 20:32 UTCGHSA enrichmentGHSA-566p-8rmw-5xmj
  5. 2026-10-11 19:10 UTCEG score recompute
  6. 2026-10-11 16:25 UTCEG score recompute
  7. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-11 13:37 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-09 03:05 UTCEG score recompute
  12. 2026-10-09 03:05 UTCGHSA enrichmentGHSA-566p-8rmw-5xmj
  13. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-06 09:39 UTCGHSA enrichmentGHSA-566p-8rmw-5xmj
  17. 2026-10-06 09:28 UTCNVD update
  18. 2026-10-06 08:54 UTCEG score recompute
  19. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98274?
CVE-2026-98274 is a vulnerability whose severity is not yet rated; its CVE record was published on October 6, 2026. In the Linux kernel, the following vulnerability has been resolved: net: psp: avoid conflicts with skb->decrypted and skvalidatexmit_skb() PSP conflicts with TLS ULP in its usage of both skb->decrypted and sk->skvalidatexmit_skb(). Make PSP mutually exclusive with TLS ULP, the only other user of…
When was the CVE record for CVE-2026-98274 published?
The CVE record for CVE-2026-98274 was published on October 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-98274 actively exploited?
CVE-2026-98274 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-98274?
A fix for CVE-2026-98274 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98274 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98274

Explore →

Is Your Infrastructure Affected by CVE-2026-98274?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs