CVE-2026-53129

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-38997 (ENISA EUVD) · GHSA-76p3-3v32-9xxh (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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

fs/mbcache: cancel shrink work before destroying the cache

mb_cache_destroy() calls shrinker_free() and then frees all cache entries and the cache itself, but it does not cancel the pending c_shrink_work work item first.

If mb_cache_entry_create() schedules c_shrink_work via schedule_work() and the work item is still pending or running when mb_cache_destroy() runs, mb_cache_shrink_worker() will access the cache after its memory has been freed, causing a use-after-free.

This is only reachable by a privileged user (root or CAP_SYS_ADMIN) who can trigger the last put of a mounted ext2/ext4/ocfs2 filesystem.

Cancel the work item with cancel_work_sync() before calling shrinker_free(), ensuring the worker has finished and will not be rescheduled before the cache is torn down.

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 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.1%
EPSS %ILE
1st
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

June 24, 2026

Last Modified

October 30, 2026

Advisory Details (4)

Auto-updated Jul 6, 2026
Patch available.
Web page

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/mbcache: cancel shrink work before destroying the cache - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0e4eff315d799f5842b95872199b0f0fb8ef5f51

Vendor Advisories for CVE-2026-53129(2)

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

Patch Availability(13)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 14× in last 7d / 48× 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 100 of 316 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. None are among the latest 100 rows. The 216 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-53129?
CVE-2026-53129 is a high-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/mbcache: cancel shrink work before destroying the cache mb_cache_destroy() calls shrinker_free() and then frees all cache entries and the cache itself, but it does not cancel the pending c_shrink_work work item first. If…
When was the CVE record for CVE-2026-53129 published?
The CVE record for CVE-2026-53129 was published on June 24, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-53129 actively exploited?
CVE-2026-53129 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53129?
CVE-2026-53129 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53129?
A fix for CVE-2026-53129 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53129 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-53129

Explore →

Is Your Infrastructure Affected by CVE-2026-53129?

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