CVE-2026-97594

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

landlock: Fix use-after-free of the source's parent directory

current_check_refer_path() reads old_dentry->d_parent without holding a reference nor a lock on it, and then dereferences it in collect_domain_accesses() and in the audit record.

A reference on a child does not pin its parent: __d_move() reassigns dentry->d_parent and drops the reference the child held on its former parent. hook_path_rename() is not affected because the rename path calls lock_rename() before the hook, so the source cannot be reparented under it. hook_path_link() has no such protection: filename_linkat() holds a reference on the source dentry but neither locks nor references its parent, so a concurrent rename(2) can reparent the source while security_path_link() runs, and the former parent can then be removed and freed while the hook walks it.

A process can trigger this after entering a Landlock domain that handles at least one filesystem access right. The process can then race a linkat(2) loop against rename(2) and rmdir(2):

BUG: KASAN: slab-use-after-free in collect_domain_accesses+0x278/0x290 Read of size 4 at addr ffff888160bd53f4 by task llrepro2/549 collect_domain_accesses+0x278/0x290 current_check_refer_path+0x952/0x1120 security_path_link+0x1be/0x320 filename_linkat+0x342/0x6d0 __x64_sys_linkat+0xfa/0x150 Freed by task 562: kmem_cache_free+0x139/0x4c0 i_callback+0x4b/0x80 rcu_core+0x7dc/0x10a0

Take a reference on the dentry selected as the source parent, using dget() for the common-mount-root case and dget_parent() otherwise. Release it after the hierarchy walk and synchronous audit logging.

[mic: Clarify the caller, reachability, and reference handling]

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

landlock: Fix use-after-free of the source's parent directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c6dc792538260a8087ac5b22c31b3b8e47c85d6
generic

landlock: Fix use-after-free of the source's parent directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba29c46ccfe3ebadfb8aa18149186c49f84b14f8
generic

landlock: Fix use-after-free of the source's parent directory - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/379efd2ce8b26fd35feb13ccc2f671ff105a5052

Vendor Advisories for CVE-2026-97594(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
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 (180 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 43× in last 7d / 61× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 00:32 UTCEG score recompute
  2. 2026-10-05 00:32 UTCVendor advisory
  3. 2026-10-05 00:32 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 12:09 UTCVendor advisory
  6. 2026-10-04 12:09 UTCGHSA enrichment
  7. 2026-10-03 23:47 UTCEG score recompute
  8. 2026-10-03 23:47 UTCVendor advisory
  9. 2026-10-03 23:47 UTCGHSA enrichment
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-03 11:23 UTCEG score recompute
  12. 2026-10-03 11:23 UTCVendor advisory
  13. 2026-10-03 11:23 UTCGHSA enrichment
  14. 2026-10-03 09:45 UTCVendor advisory
  15. 2026-10-03 09:44 UTCGHSA enrichment
  16. 2026-10-02 21:17 UTCEG score recompute
  17. 2026-10-02 21:17 UTCVendor advisory
  18. 2026-10-02 21:17 UTCGHSA enrichment
  19. 2026-10-02 17:57 UTCEPSS rescore
  20. 2026-10-02 08:54 UTCVendor advisory
  21. 2026-10-02 08:54 UTCGHSA enrichment
  22. 2026-10-01 20:31 UTCEG score recompute
  23. 2026-10-01 20:31 UTCVendor advisory
  24. 2026-10-01 20:30 UTCGHSA enrichment
  25. 2026-10-01 19:51 UTCEPSS rescore
Show 36 more
  1. 2026-10-01 07:56 UTCVendor advisory
  2. 2026-10-01 07:56 UTCGHSA enrichment
  3. 2026-09-30 19:34 UTCEG score recompute
  4. 2026-09-30 19:34 UTCGHSA enrichment
  5. 2026-09-30 15:04 UTCEPSS rescore
  6. 2026-09-30 07:12 UTCVendor advisory
  7. 2026-09-30 07:12 UTCGHSA enrichment
  8. 2026-09-29 18:49 UTCEG score recompute
  9. 2026-09-29 18:49 UTCVendor advisory
  10. 2026-09-29 18:49 UTCGHSA enrichment
  11. 2026-09-29 06:22 UTCEG score recompute
  12. 2026-09-29 06:22 UTCVendor advisory
  13. 2026-09-29 06:22 UTCGHSA enrichment
  14. 2026-09-28 18:00 UTCEG score recompute
  15. 2026-09-28 18:00 UTCVendor advisory
  16. 2026-09-28 17:59 UTCGHSA enrichment
  17. 2026-09-28 13:52 UTCEPSS rescore
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 05:24 UTCGHSA enrichment
  20. 2026-09-27 17:02 UTCEG score recompute
  21. 2026-09-27 17:02 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 04:39 UTCGHSA enrichment
  24. 2026-09-26 16:16 UTCEG score recompute
  25. 2026-09-26 16:15 UTCGHSA enrichment
  26. 2026-09-26 15:59 UTCEPSS rescore
  27. 2026-09-26 03:51 UTCEG score recompute
  28. 2026-09-26 03:50 UTCGHSA enrichment
  29. 2026-09-25 15:24 UTCEG score recompute
  30. 2026-09-25 15:24 UTCGHSA enrichment
  31. 2026-09-25 14:53 UTCEG score recompute▲ 7.80
  32. 2026-09-25 14:52 UTCGHSA enrichment
  33. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  34. 2026-09-25 11:29 UTCNVD update
  35. 2026-09-25 10:39 UTCEG score recompute
  36. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-97594?
CVE-2026-97594 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: landlock: Fix use-after-free of the source's parent directory currentcheckreferpath() reads olddentry->d_parent without holding a reference nor a lock on it, and then dereferences it in collectdomainaccesses() and in the audit…
When was CVE-2026-97594 disclosed?
CVE-2026-97594 was first published on September 25, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97594 actively exploited?
CVE-2026-97594 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97594?
CVE-2026-97594 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-97594?
No fix for CVE-2026-97594 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-97594 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-97594

Explore →

Is Your Infrastructure Affected by CVE-2026-97594?

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

Book a Demo →Browse All CVEs