CVE-2026-53388

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM 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 — 4 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

A fix is available — apply it.

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(medium)
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

August 17, 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-07ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)7.0.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Showing the most recent 100 of 194 total refreshes for this CVE.

  1. 2026-09-10 09:35 UTCEPSS rescore
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-07 23:47 UTCEG score recompute
  4. 2026-09-07 23:47 UTCVendor advisory
  5. 2026-09-07 23:47 UTCGHSA enrichment
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-06 13:18 UTCVendor advisory
  9. 2026-09-06 13:18 UTCGHSA enrichment
  10. 2026-09-05 20:21 UTCEG score recompute
  11. 2026-09-05 20:21 UTCVendor advisory
  12. 2026-09-05 20:21 UTCGHSA enrichment
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-31 03:49 UTCEG score recompute
  18. 2026-08-31 03:49 UTCVendor advisory
  19. 2026-08-31 03:49 UTCGHSA enrichment
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 15:45 UTCVendor advisory
  22. 2026-08-30 15:45 UTCGHSA enrichment
  23. 2026-08-30 03:05 UTCEG score recompute
  24. 2026-08-30 03:05 UTCVendor advisory
  25. 2026-08-30 03:05 UTCGHSA enrichment
Show 75 more
  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-28 21:41 UTCEPSS rescore
  3. 2026-08-28 01:46 UTCEG score recompute
  4. 2026-08-28 01:46 UTCVendor advisory
  5. 2026-08-28 01:46 UTCGHSA enrichment
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-27 13:15 UTCVendor advisory
  8. 2026-08-27 13:15 UTCGHSA enrichment
  9. 2026-08-27 01:00 UTCEG score recompute
  10. 2026-08-27 01:00 UTCVendor advisory
  11. 2026-08-27 01:00 UTCGHSA enrichment
  12. 2026-08-26 14:46 UTCEPSS rescore
  13. 2026-08-26 12:57 UTCVendor advisory
  14. 2026-08-26 12:57 UTCGHSA enrichment
  15. 2026-08-26 00:53 UTCEG score recompute
  16. 2026-08-26 00:53 UTCVendor advisory
  17. 2026-08-26 00:53 UTCGHSA enrichment
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-25 12:49 UTCVendor advisory
  20. 2026-08-25 12:49 UTCGHSA enrichment
  21. 2026-08-25 00:41 UTCEG score recompute
  22. 2026-08-25 00:41 UTCVendor advisory
  23. 2026-08-25 00:41 UTCGHSA enrichment
  24. 2026-08-24 12:31 UTCEG score recompute
  25. 2026-08-24 12:31 UTCVendor advisory
  26. 2026-08-24 12:31 UTCGHSA enrichment
  27. 2026-08-24 00:25 UTCVendor advisory
  28. 2026-08-24 00:25 UTCGHSA enrichment
  29. 2026-08-23 12:20 UTCEG score recompute
  30. 2026-08-23 12:20 UTCVendor advisory
  31. 2026-08-23 12:20 UTCGHSA enrichment
  32. 2026-08-23 00:19 UTCEPSS rescore
  33. 2026-08-23 00:17 UTCVendor advisory
  34. 2026-08-23 00:17 UTCGHSA enrichment
  35. 2026-08-22 12:13 UTCEG score recompute
  36. 2026-08-22 12:13 UTCVendor advisory
  37. 2026-08-22 12:13 UTCGHSA enrichment
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-21 23:48 UTCVendor advisory
  40. 2026-08-21 23:48 UTCGHSA enrichment
  41. 2026-08-21 11:44 UTCVendor advisory
  42. 2026-08-21 11:44 UTCGHSA enrichment
  43. 2026-08-20 23:25 UTCEG score recompute
  44. 2026-08-20 23:25 UTCVendor advisory
  45. 2026-08-20 23:25 UTCGHSA enrichment
  46. 2026-08-20 22:55 UTCEPSS rescore
  47. 2026-08-20 11:22 UTCVendor advisory
  48. 2026-08-20 11:22 UTCGHSA enrichment
  49. 2026-08-19 23:18 UTCEG score recompute
  50. 2026-08-19 23:18 UTCVendor advisory
  51. 2026-08-19 23:18 UTCGHSA enrichment
  52. 2026-08-19 17:04 UTCEPSS rescore
  53. 2026-08-19 07:55 UTCVendor advisory
  54. 2026-08-19 07:55 UTCGHSA enrichment
  55. 2026-08-18 19:51 UTCEG score recompute
  56. 2026-08-18 19:51 UTCVendor advisory
  57. 2026-08-18 19:51 UTCGHSA enrichment
  58. 2026-08-18 05:55 UTCGHSA enrichment
  59. 2026-08-17 17:38 UTCEG score recompute
  60. 2026-08-17 17:38 UTCVendor advisory
  61. 2026-08-17 17:37 UTCGHSA enrichment
  62. 2026-08-17 13:47 UTCEPSS rescore
  63. 2026-08-17 05:24 UTCVendor advisory
  64. 2026-08-17 05:24 UTCGHSA enrichment
  65. 2026-08-17 02:56 UTCEG score recompute
  66. 2026-08-17 02:56 UTCVendor advisory
  67. 2026-08-17 02:56 UTCGHSA enrichment
  68. 2026-08-16 14:56 UTCEPSS rescore
  69. 2026-08-16 14:53 UTCVendor advisory
  70. 2026-08-16 14:53 UTCGHSA enrichment
  71. 2026-08-16 02:50 UTCEG score recompute
  72. 2026-08-16 02:50 UTCVendor advisory
  73. 2026-08-16 02:50 UTCGHSA enrichment
  74. 2026-08-16 02:14 UTCEPSS rescore
  75. 2026-08-15 14:47 UTCVendor advisory

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 August 17, 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.9% 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

See which npm, PyPI, Go, and Maven packages are affected by 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