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-90203Squashfs: check block offset is not negative

Description

In the Linux kernel, the following vulnerability has been resolved: Squashfs: check block offset is not negative If a negative offset is read off disk (for example the offset into the decompressed fragment block), this will cause squashfs_copy_data() to perform an out of bounds access. Fix by checking if offset is negative, and returning 0. This matches existing behaviour where an offset beyond the block returns 0 bytes copied. To trigger this out of bounds access requires a crafted Squashfs filesystem and CAP_SYS_ADMIN to mount it. Unprivileged users will not be able to mount such a filesystem, but once mounted, an unprivileged user can trigger the out of bounds access by reading the crafted file with the negative offset.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days 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-90203, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
NVDNVD · Received3.1High7.1CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (13 Nov 2026)
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 – < b169185d5c672b989985c6c2e38cafab2548ba88
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < c2a126fca820ae74872da28de68dc74d4595dc4b
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 95dadf366c117dcdca78a570e6832071deab1ecd
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < 3d2f0cb66c909ea2312cdef465165bb9a3ba2d84
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < bbb2218eb072b0a15dc063929200183bd23c2344
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < d0a3729d464fcf516416a41cf304c0c92126ee03
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < e4afd90bc7bf3dd477970c6c42bdd29ad3fda7fe
    • affected f400e12656ab518be107febfe2315fb1eab5a342 – < e300eb5002925b29be803d2661af07266cfa267e
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .