Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-23388Squashfs: check metadata block offset is within range

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23388, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 60f679f643f3f36a8571ea585e4ce5d93ef952b5
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 3f68a9457a6190814377577374da75f872e0a013
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 0c8ab092aec3ac4294940054772d30b511b16713
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 6b847d65f5b0065e02080c61fad93d57d6686383
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 01ee0bcc29864b78249308e8b35042b09bbf5fe3
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 3b9499e7d677dd4366239a292238489a804936b2
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < fdb24a820a5832ec4532273282cbd4f22c291a0d
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23388 badge
[![CVE-2026-23388](https://cveledger.app/badge/CVE-2026-23388.svg)](https://cveledger.app/cve/CVE-2026-23388)

Record last updated .