CVE-2026-89767

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-11. 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
Trending — 3 sources updated this week
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:

ovl: fix double end_creating() on the casefold-mismatch path

ovl_create_real() releases the new dentry twice when the casefold consistency check fails. The S_IFDIR branch calls end_creating() and sets err, then falls through to the common out: label which calls end_creating() on the same dentry again:

case S_IFDIR: newdentry = ovl_do_mkdir(ofs, dir, newdentry, attr->mode); err = PTR_ERR_OR_ZERO(newdentry); if (!err && ofs->casefold != ovl_dentry_casefolded(newdentry)) { pr_warn_ratelimited(...); end_creating(newdentry); /* first */ err = -EINVAL; } break; ... if (err) goto out; ... out: if (err) { end_creating(newdentry); /* second, same dentry */ return ERR_PTR(err); }

end_creating() is end_dirop(), which does inode_unlock() on the parent and dput() on the dentry, so the parent directory's i_rwsem is unlocked twice and the dentry is put twice. The second unlock releases a lock that is not held, which is what wedges every later creation under that parent, and the second dput() drops a reference that was never taken.

The branch was added by commit dfc7da402ccc ("ovl: Check for casefold consistency when creating new dentries") as a bare dput(), which already released the reference twice; commit fe497f0759e0 ("VFS: change vfs_mkdir() to unlock on failure.") converted both sites to end_creating(), adding the double unlock.

This is reachable by an unprivileged user. The casefold consistency of the layers is validated at mount time in ovl_parse_layer(), and again on every lookup in ovl_lookup_single(), but ofs->workdir is the internal "work" subdirectory created inside the user-supplied workdir, and that subdirectory is not re-checked. Marking it casefolded after the mount therefore makes every ovl_create_temp() inherit the wrong state - and that path reaches ovl_create_real() through ovl_start_creating_temp(), which uses start_creating() with a generated name and so never runs the lookup-time check.

unshare -Urm mount -t tmpfs -o casefold=utf8-12.1.0 tmpfs mnt mkdir -p mnt/lower/d mnt/upper mnt/work mnt/merged mount -t overlay ovl -o lowerdir=mnt/lower,\ upperdir=mnt/upper,workdir=mnt/work mnt/merged chattr +F mnt/work/work mkdir mnt/merged/d/sub # directory copy-up

overlayfs: wrong inherited casefold (work/#5)

and the next copy-up blocks forever on the parent's i_rwsem:

mkdir D start_creating+0x65/0xb0 ovl_start_creating_temp+0xb0/0xe0 [overlay] ovl_create_temp+0xa3/0x1d0 [overlay] ovl_copy_up_one+0x1f1c/0x21c0 [overlay] ovl_copy_up_flags+0xf5/0x140 [overlay] ovl_create_object+0xb7/0x220 [overlay] ovl_mkdir+0x23/0x40 [overlay]

Drop the end_creating() from the branch and let out: own the cleanup, which is what every other error path in this function already does.

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

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 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
6th
KEV
Not listed

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.

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

September 11, 2026

Last Modified

September 13, 2026

Advisory Details (3)

Auto-updated Sep 13, 2026
Patch available.
Web page

ovl: fix double end_creating() on the casefold-mismatch path - kernel/git/stable/linux.git - Linux kernel stable tree

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

ovl: fix double end_creating() on the casefold-mismatch path - kernel/git/stable/linux.git - Linux kernel stable tree

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

ovl: fix double end_creating() on the casefold-mismatch path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/077ab8985ee278c3d8618182d335b0f0cd919e16

Vendor Advisories for CVE-2026-89767(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 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 25× in last 7d / 113× 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.

Showing the most recent 99 of 126 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  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:48 UTCEG score recompute
  4. 2026-10-12 09:09 UTCEG score recompute
  5. 2026-10-12 09:09 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-11 19:56 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-11 19:15 UTCEG score recompute
  8. 2026-10-11 16:31 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-11 13:47 UTCEG score recompute
  11. 2026-10-11 06:47 UTCEG score recompute
  12. 2026-10-11 06:47 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-10 15:10 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-10 03:47 UTCEG score recompute
  16. 2026-10-10 03:47 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-09 16:26 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-08 23:10 UTCEG score recompute
  20. 2026-10-08 23:10 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-08 06:59 UTCEG score recompute
  23. 2026-10-08 06:59 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-07 19:38 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
Show 74 more
  1. 2026-10-07 08:03 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-06 20:41 UTCEG score recompute
  3. 2026-10-06 20:41 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-06 09:19 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-05 21:59 UTCEG score recompute
  7. 2026-10-05 21:58 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-05 10:03 UTCEG score recompute
  10. 2026-10-05 10:03 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-04 22:41 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-04 11:19 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-03 23:58 UTCEG score recompute
  15. 2026-10-03 23:57 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-03 12:05 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-03 00:05 UTCEG score recompute
  18. 2026-10-03 00:05 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-02 12:35 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-02 00:20 UTCEG score recompute
  21. 2026-10-02 00:20 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-01 12:14 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-01 00:53 UTCEG score recompute
  25. 2026-10-01 00:53 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-30 13:32 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-09-30 01:39 UTCEG score recompute
  29. 2026-09-30 01:39 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  30. 2026-09-29 10:56 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-09-28 23:35 UTCEG score recompute
  32. 2026-09-28 23:35 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-28 12:14 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-09-28 00:52 UTCEG score recompute
  36. 2026-09-28 00:52 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-27 13:30 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-09-27 02:06 UTCEG score recompute
  40. 2026-09-27 02:06 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  42. 2026-09-26 14:45 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-09-26 03:03 UTCEG score recompute
  44. 2026-09-26 03:03 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-09-25 15:37 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-09-25 04:16 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-09-24 16:54 UTCEG score recompute
  48. 2026-09-24 16:54 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-09-24 05:32 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-09-23 18:10 UTCEG score recompute
  52. 2026-09-23 18:10 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  54. 2026-09-23 06:49 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-22 19:27 UTCEG score recompute
  56. 2026-09-22 19:27 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  58. 2026-09-22 08:06 UTCEG score recompute
  59. 2026-09-22 08:05 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  61. 2026-09-21 20:44 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-21 09:22 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  63. 2026-09-20 22:01 UTCEG score recompute
  64. 2026-09-20 22:01 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  66. 2026-09-20 10:39 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-19 23:15 UTCEG score recompute
  68. 2026-09-19 23:15 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-09-19 11:54 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-19 00:33 UTCEG score recompute
  71. 2026-09-19 00:33 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  73. 2026-09-18 13:12 UTCGHSA enrichmentGHSA-mvh9-78p9-62x7 · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-09-18 01:51 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-89767?
CVE-2026-89767 is a high-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: ovl: fix double end_creating() on the casefold-mismatch path ovlcreatereal() releases the new dentry twice when the casefold consistency check fails. The SIFDIR branch calls endcreating() and sets err, then falls through to the…
When was the CVE record for CVE-2026-89767 published?
The CVE record for CVE-2026-89767 was published on September 11, 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 September 13, 2026; the record at its source may have been updated since.
Is CVE-2026-89767 actively exploited?
CVE-2026-89767 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).
What is the CVSS score of CVE-2026-89767?
CVE-2026-89767 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-89767?
A fix for CVE-2026-89767 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89767 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-89767

Explore →

Is Your Infrastructure Affected by CVE-2026-89767?

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