7.1
HIGH CVSS 3.1
CVE-2026-23388
Squashfs: 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.

INFO

Published Date :

March 25, 2026, 11:16 a.m.

Last Modified :

April 24, 2026, 6:45 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2026-23388 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Apply kernel updates to fix metadata block offset checks and prevent out-of-bounds access.
  • Update the Linux kernel to the latest version.
  • Apply the patch for squashfs_read_metadata offset check.
  • Verify metadata integrity on systems using Squashfs.
  • Restart affected services or systems.
Public PoC/Exploit Available at Github

CVE-2026-23388 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-23388 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-23388 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

DSA and DLA for Debian last 14 days

Python

Updated: 10 hours, 26 minutes ago
0 stars 1 fork 1 watcher
Born at : Feb. 12, 2025, 2:08 p.m. This repo has been linked 606 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-23388 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-23388 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Apr. 24, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
    Added CWE CWE-125
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:2.6.29:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.7 *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.17 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.130 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.77 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.203 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.167 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.29.1 up to (excluding) 5.10.253
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/01ee0bcc29864b78249308e8b35042b09bbf5fe3 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/0c8ab092aec3ac4294940054772d30b511b16713 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/3b9499e7d677dd4366239a292238489a804936b2 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/3f68a9457a6190814377577374da75f872e0a013 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/60f679f643f3f36a8571ea585e4ce5d93ef952b5 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/6b847d65f5b0065e02080c61fad93d57d6686383 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/fdb24a820a5832ec4532273282cbd4f22c291a0d Types: Patch
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Apr. 18, 2026

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/3f68a9457a6190814377577374da75f872e0a013
    Added Reference https://git.kernel.org/stable/c/60f679f643f3f36a8571ea585e4ce5d93ef952b5
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Mar. 25, 2026

    Action Type Old Value New Value
    Added 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.
    Added Reference https://git.kernel.org/stable/c/01ee0bcc29864b78249308e8b35042b09bbf5fe3
    Added Reference https://git.kernel.org/stable/c/0c8ab092aec3ac4294940054772d30b511b16713
    Added Reference https://git.kernel.org/stable/c/3b9499e7d677dd4366239a292238489a804936b2
    Added Reference https://git.kernel.org/stable/c/6b847d65f5b0065e02080c61fad93d57d6686383
    Added Reference https://git.kernel.org/stable/c/9e9fa5ad37c9cbad73c165c7ff1e76e650825e7c
    Added Reference https://git.kernel.org/stable/c/fdb24a820a5832ec4532273282cbd4f22c291a0d
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.