CVE-2026-23388

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-03-25. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
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.1Exploit: 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:

Squashfs: check metadata block offset is within range

Syzkaller reports a "general protection fault in squashfs_copy_data"

This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offset.

This is subsequently passed to squashfs_copy_data (via squashfs_read_metadata) where the negative offset causes an out of bounds access.

The fix is to check that the offset is within range in squashfs_read_metadata. This will trap this and other cases.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

March 25, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

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

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b847d65f5b0065e02080c61fad93d57d6686383
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/60f679f643f3f36a8571ea585e4ce5d93ef952b5
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f68a9457a6190814377577374da75f872e0a013
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b9499e7d677dd4366239a292238489a804936b2
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0c8ab092aec3ac4294940054772d30b511b16713
generic

Squashfs: check metadata block offset is within range - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01ee0bcc29864b78249308e8b35042b09bbf5fe3

Vendor Advisories for CVE-2026-23388(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—osv
linuxKernel @ 6.1.167—osv

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 ... 5.10.92-2 (53 versions)5.10.257-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (117 versions)6.19.8-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 7× in last 7d / 55× 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 201 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23388?
CVE-2026-23388 is a high vulnerability published on March 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Squashfs: check metadata block offset is within range Syzkaller reports a "general protection fault in squashfscopydata" This is ultimately caused by a corrupted index look-up table, which produces a negative metadata block offset.…
When was CVE-2026-23388 disclosed?
CVE-2026-23388 was first published in the National Vulnerability Database on March 25, 2026, with the most recent update on June 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-23388 actively exploited?
CVE-2026-23388 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 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23388?
CVE-2026-23388 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-23388?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23388, 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-23388

Explore →

Is Your Infrastructure Affected by CVE-2026-23388?

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

Start Free Scan →Browse All CVEs