CVE-2026-98231

UNRATEDCVSS · not yet scoredTrending — 4 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:

xfrm: serialize state GC with device state flush

The deferred-device pass in xfrm_dev_state_flush() finds states under xfrm_state_dev_gc_lock, but drops the lock before calling xfrm_dev_state_free() because the driver callback may sleep. The device GC list does not hold an xfrm_state reference, so the state GC worker can destroy the same state concurrently.

The race can proceed as follows:

CPU 0 CPU 1 find x on the device GC list drop xfrm_state_dev_gc_lock read x->xso.dev xfrm_state_gc_destroy(x) xfrm_dev_state_free(x) xfrm_state_free(x) continue xfrm_dev_state_free(x)

Both paths can invoke the driver callback and drop the device reference. CPU 0 can also access the xfrm_state after CPU 1 has freed it.

KASAN reported:

BUG: KASAN: slab-use-after-free in xfrm_dev_state_free+0x24c/0x2a0 Read of size 8 at addr ffff88810bbaa960 by task poc/102

Call Trace: xfrm_dev_state_free+0x24c/0x2a0 xfrm_dev_state_flush+0x353/0x400 xfrm_dev_event+0x26d/0x3a0 notifier_call_chain+0xc0/0x280 __dev_notify_flags+0x169/0x250 netif_change_flags+0xe7/0x160 dev_change_flags+0x96/0x220 devinet_ioctl+0x7f4/0x1880

Allocated by task 87: xfrm_state_alloc+0x1e/0x5c0 xfrm_add_sa+0xe7f/0x5820 xfrm_user_rcv_msg+0x4f3/0x940

Freed by task 57: kmem_cache_free+0xcb/0x3d0 xfrm_state_gc_task+0x4a8/0x650 process_one_work+0x63a/0x1070

Serialize xfrm_state destruction against the deferred-device pass with a mutex. Keep xfrm_state_dev_gc_lock limited to list operations and retain the existing callback and device-reference release ordering.

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
9th
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 (5)

Vendor Advisories for CVE-2026-98231(2)

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (183 versions)
  • every version on: no fix on record
—
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 16× in last 7d / 21× 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% · 9th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-12 14:38 UTCEG score recompute
  4. 2026-10-12 03:07 UTCVendor advisory
  5. 2026-10-12 03:06 UTCGHSA enrichmentGHSA-8c3r-c85m-88vq
  6. 2026-10-11 19:10 UTCEG score recompute
  7. 2026-10-11 16:25 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-11 13:37 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-09 06:27 UTCEG score recompute
  13. 2026-10-09 06:27 UTCVendor advisory
  14. 2026-10-09 06:27 UTCGHSA enrichmentGHSA-8c3r-c85m-88vq
  15. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-06 09:49 UTCGHSA enrichmentGHSA-8c3r-c85m-88vq
  19. 2026-10-06 09:28 UTCNVD update
  20. 2026-10-06 08:55 UTCEG score recompute
  21. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-98231?
CVE-2026-98231 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: xfrm: serialize state GC with device state flush The deferred-device pass in xfrmdevstate_flush() finds states under xfrmstatedevgclock, but drops the lock before calling xfrmdevstate_free() because the driver callback may sleep.…
When was the CVE record for CVE-2026-98231 published?
The CVE record for CVE-2026-98231 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-98231 actively exploited?
CVE-2026-98231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-98231?
A fix for CVE-2026-98231 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-98231 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-98231

Explore →

Is Your Infrastructure Affected by CVE-2026-98231?

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

Book a Demo →Browse All CVEs