CVE-2026-53388

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

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

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

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

fuse: re-lock request before replacing page cache folio

fuse_try_move_folio() unlocks the request on entry but does not re-lock it on the success path. This means fuse_chan_abort() can end the request and free the fuse_io_args (eg fuse_readpages_end()) while the subsequent copy chain logic after fuse_try_move_folio() accesses the fuse_io_args, leading to use-after-free issues.

Fix this by calling lock_request() before replace_page_cache_folio(). This ensures the request is locked on the success path which will prevent the fuse_io_args from being freed while the later copying logic runs, and also ensures that the ap->folios[i]->mapping is never null since ap->folios[i] will always point to the newfolio after replace_page_cache_folio().

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (8)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

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

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c18691e0cfda29672f79bafde8abdb7710674f6
generic

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5927b43a4f8d89e86930f524bf63e9c7e66f61b4
generic

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46473ddccdc5065033e397d6e62c280dbcd3d9c2
generic

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/030fe3e9d8abdee303dd7e9e42f45082d382a407
generic

fuse: re-lock request before replacing page cache folio - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0223f452532d9cd8a5e87c45de828fd93c99bd25

Vendor Advisories for CVE-2026-53388(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 21× 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-07-27 11:17 UTCGHSA enrichment
  2. 2026-07-26 23:14 UTCEG score recompute
  3. 2026-07-26 23:14 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 11:10 UTCEG score recompute
  6. 2026-07-26 11:10 UTCGHSA enrichment
  7. 2026-07-25 14:18 UTCEPSS rescore
  8. 2026-07-24 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:19 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:25 UTCEPSS rescore
  13. 2026-07-20 17:48 UTCEG score recompute
  14. 2026-07-20 17:48 UTCGHSA enrichment
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-20 14:48 UTCEG score recompute▲ 7.80
  17. 2026-07-20 14:48 UTCGHSA enrichment
  18. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  19. 2026-07-19 12:26 UTCNVD update
  20. 2026-07-19 12:15 UTCEG score recompute
  21. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53388?
CVE-2026-53388 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: fuse: re-lock request before replacing page cache folio fusetrymove_folio() unlocks the request on entry but does not re-lock it on the success path. This means fusechanabort() can end the request and free the fuseioargs (eg…
When was CVE-2026-53388 disclosed?
CVE-2026-53388 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53388 actively exploited?
CVE-2026-53388 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53388?
CVE-2026-53388 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53388?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53388, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53388

Explore →

Is Your Infrastructure Affected by CVE-2026-53388?

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

Start Free Scan →Browse All CVEs