squashfs: Add dictionary size range check to prevent shift-out-of-bounds
Summary
| CVE | CVE-2026-98636 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:17:16 UTC |
| Updated | 2026-10-19 10:19:27 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
squashfs: Add dictionary size range check to prevent shift-out-of-bounds
When an abnormal SquashFS image (COMP_OPTS flag is 1 but dictionary size
is 0) is mounted, and performs shift operations using dictionarysize, the
shift exponent is -1, causing a shift-out-of-bounds.
Detail as below:
squashfs_comp_opts(msblk, buffer, length)
squashfs_xz_comp_opts()
if (comp_opts)
n = ffs(opts->dict_size) - 1;<----opts->dict_size=0, n=-1
if (opts->dict_size != (1 << n) && opts->dict_size !=
(1 << n) + (1 << (n + 1))) <----shift-out-of-bounds
Fix it by adding a dictionary size range check before the shift operation. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 b02948a23455f8190a53887b2d2c13ae1d360cea git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 9d9c5c218ea356a1d88765214ad2919605280ab1 git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 7a1c293e7aa17f1afaee0684e0e931fe23a5a6b1 git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 c68e0068a236f9a7dfc19720bdf11e5d80a85089 git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 88c673a0bd233df44ca0020da82f4fd3876de27a git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 0cb85377daaefb4ce5ce72975f2deb27ee0e0cad git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 e1ca4e3a380ef3e8f46ce006f1146392e3f32c98 git |
Not specified |
| CNA |
Linux |
Linux |
affected ff750311d30acc9564ef577050794953eee59f01 1f7745fb3580152ca902ef181b605f33cabfb1d0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 2.6.39 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 2.6.39 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.10.271 5.10.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.15.222 5.15.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.1.189 6.1.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.6.158 6.6.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.112 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.55 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.9 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/88c673a0bd233df44ca0020da82f4fd3876de27a |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/b02948a23455f8190a53887b2d2c13ae1d360cea |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9d9c5c218ea356a1d88765214ad2919605280ab1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c68e0068a236f9a7dfc19720bdf11e5d80a85089 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/0cb85377daaefb4ce5ce72975f2deb27ee0e0cad |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/1f7745fb3580152ca902ef181b605f33cabfb1d0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/e1ca4e3a380ef3e8f46ce006f1146392e3f32c98 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/7a1c293e7aa17f1afaee0684e0e931fe23a5a6b1 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.