CVE-2026-99173

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-28. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-111925 (ENISA EUVD) · GHSA-fx9f-7wc6-cjjx (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

eventfs: Free the eventfs_inode after an rcu grace period too

tracefs_d_revalidate() reads ->is_freed of the eventfs_inode that dentry->d_fsdata points to, and ->d_revalidate() is called in rcu pathwalk mode with nothing but rcu_read_lock() held. The dentry itself stays around for such a walker, but tracefs_d_release() drops its reference to the eventfs_inode when the dentry is killed, and release_ei() then frees it after a grace period of eventfs_srcu. An SRCU grace period doesn't wait for rcu_read_lock() sections, so the walker can read an eventfs_inode that is already gone.

With a pathwalk held up in tracefs_d_revalidate() while the dentry goes away:

BUG: KASAN: slab-use-after-free in tracefs_d_revalidate+0x76/0x90 Read of size 1 at addr ff1100010152d8d0 by task walker/97 Call Trace: tracefs_d_revalidate+0x76/0x90 lookup_fast+0x320/0x640 path_lookupat+0x160/0xb00 filename_lookup+0x1f1/0x5b0 vfs_statx+0xd7/0x3b0 vfs_fstatat+0x4d/0x90 __do_sys_newfstatat+0xa0/0x100 do_syscall_64+0x10e/0x5e0 entry_SYSCALL_64_after_hwframe+0x77/0x7f [...] Allocated by task 1: __kmalloc_cache_noprof+0x249/0x560 eventfs_create_dir+0x7a/0x590 event_create_dir+0x2fb/0xcf0 trace_add_event_call+0xbf/0x150 [...] Freed by task 11: kfree+0x1db/0x5b0 srcu_invoke_callbacks+0x3a3/0x620 process_one_work+0x937/0x1810 worker_thread+0x4f1/0xd60

Before commit 8e556432477e ("eventfs: Use SRCU for freeing eventfs_inodes") release_ei() used call_rcu(), which covered the walker, while eventfs_iterate() needs the SRCU grace period. Wait for both and chain call_rcu() from the SRCU callback.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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.

The score's inputs: 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 28, 2026

Last Modified

October 31, 2026

Advisory Details (5)

Auto-updated Oct 31, 2026
Patch available.
Web page

eventfs: Free the eventfs_inode after an rcu grace period too - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2cd88c498ecff8e22bf4c397b8eb226db70ac343
Web page

eventfs: Free the eventfs_inode after an rcu grace period too - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45fcfd5d9c10e0aa977ed5b9bd445707e01bb107
Web page

eventfs: Free the eventfs_inode after an rcu grace period too - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4586ef24ce390e8becb9f3e5852d5d3978b01c33
Web page

eventfs: Free the eventfs_inode after an rcu grace period too - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dd2c767814a876be0f16f0b7f98a403dc176f51e
Web page

eventfs: Free the eventfs_inode after an rcu grace period too - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5819018dc29fb2ac2fd4865d507f9893c89c0624

Vendor Advisories for CVE-2026-99173(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 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (192 versions)
  • every version up to 7.2.13-1: fixed in 7.2.13-1
—

Data Freshness Timeline

(refreshed 6× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-11-16 16:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-15 21:24 UTCEchelonGraph re-scored
  7. 2026-11-15 21:24 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-11-13 16:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-09 16:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-11-08 16:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-11-08 04:34 UTCEchelonGraph re-scored
  17. 2026-11-08 04:34 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-31 13:27 UTCEchelonGraph re-scored
Show 15 more
  1. 2026-10-31 13:27 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx
  2. 2026-10-31 12:49 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
  3. 2026-10-31 12:48 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx
  4. 2026-10-31 12:48 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-30 13:42 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx
  7. 2026-10-30 13:27 UTCNVD update
  8. 2026-10-30 12:51 UTCEchelonGraph re-scored
  9. 2026-10-30 12:51 UTCGHSA enrichmentGHSA-fx9f-7wc6-cjjx
  10. 2026-10-30 12:50 UTCMITRE cvelistV5
  11. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-28 11:26 UTCNVD update
  13. 2026-10-28 11:01 UTCENISA EUVD ID recordedEUVD-2026-111925 · Source: ENISA EUVD
  14. 2026-10-28 10:45 UTCEchelonGraph re-scored
  15. 2026-10-28 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-99173?
CVE-2026-99173 is a high-severity vulnerability; its CVE record was published on October 28, 2026. In the Linux kernel, the following vulnerability has been resolved: eventfs: Free the eventfs_inode after an rcu grace period too tracefs_d_revalidate() reads ->is_freed of the eventfs_inode that dentry->d_fsdata points to, and ->d_revalidate() is called in rcu pathwalk mode with nothing but…
When was the CVE record for CVE-2026-99173 published?
The CVE record for CVE-2026-99173 was published on October 28, 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 31, 2026; the record at its source may have been updated since.
Is CVE-2026-99173 actively exploited?
CVE-2026-99173 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-99173?
CVE-2026-99173 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-99173?
A fix for CVE-2026-99173 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99173 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-99173

Explore →

Is Your Infrastructure Affected by CVE-2026-99173?

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