CVE-2026-53392

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: 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:

NFSv4/flexfiles: reject zero filehandle version count

ff_layout_alloc_lseg() decodes the filehandle-version array count from the flexfiles layout body. The value is used as the count for kzalloc_objs(), and the current code only rejects NULL.

A zero count yields ZERO_SIZE_PTR, which can be stored in dss_info->fh_versions even though later flexfiles paths assume that at least one filehandle version exists.

Reject fh_count == 0 before the allocation, matching the existing zero version_count validation in the flexfiles GETDEVICEINFO parser.

A QEMU/KASAN run with a malformed flexfiles layout hit:

KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:ff_layout_encode_ff_layoutupdate.isra.0+0x15f/0x750 ff_layout_encode_layoutreturn+0x683/0x970 nfs4_xdr_enc_layoutreturn+0x278/0x3a0 Kernel panic - not syncing: Fatal exception

The patched kernel rejects the malformed layout without KASAN/oops/panic, and a valid fh_count=1 regression still opens, reads, and unmounts cleanly.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (4)

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

NFSv4/flexfiles: reject zero filehandle version count - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/flexfiles: reject zero filehandle version count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7779c85028a0676fb190cde4f0c540f4f8e97761
generic

NFSv4/flexfiles: reject zero filehandle version count - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/flexfiles: reject zero filehandle version count - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2131ed64b767ffa8bcdb3677d90f3964e39aabc8

Vendor Advisories for CVE-2026-53392(2)

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

Affected Packages

(6 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (55 versions)5.10.262-1
linux-6.16.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions)6.1.180-1~deb11u1
Debian:12(2)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
linux-6.126.12.100-1~deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (154 versions)7.1.3-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 142× 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 179 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53392?
CVE-2026-53392 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSv4/flexfiles: reject zero filehandle version count fflayoutalloc_lseg() decodes the filehandle-version array count from the flexfiles layout body. The value is used as the count for kzalloc_objs(), and the current code only…
When was CVE-2026-53392 disclosed?
CVE-2026-53392 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-53392 actively exploited?
CVE-2026-53392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.5% of all scored CVEs.
What is the CVSS score of CVE-2026-53392?
CVE-2026-53392 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53392?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53392, 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-53392

Explore →

Is Your Infrastructure Affected by CVE-2026-53392?

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