CVE-2025-40049

Squashfs: fix uninit-value in squashfs_get_parent

N/A
Published: October 28, 2025 at 11:48 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: Squashfs: fix uninit-value in squashfs_get_parent Syzkaller reports a "KMSAN: uninit-value in squashfs_get_parent" bug. This is caused by open_by_handle_at() being called with a file handle containing an invalid parent inode number. In particular the inode number is that of a symbolic link, rather than a directory. Squashfs_get_parent() gets called with that symbolic link inode, and accesses the parent member field. unsigned int parent_ino = squashfs_i(inode)->parent; Because non-directory inodes in Squashfs do not have a parent value, this is uninitialised, and this causes an uninitialised value access. The fix is to initialise parent with the invalid inode 0, which will cause an EINVAL error to be returned. Regular inodes used to share the parent field with the block_list_start field. This is removed in this commit to enable the parent field to contain the invalid inode number 0.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

122601408d20c77704268f1dea9f9ce4abf997c22.6.29
Vendor states this is fixed in 1b3ccd0019132880c94bb00ca7088c1749308f82 (fixed)
Vendor states this is fixed in 382a47fae449e554ef1e8c198667fd2f3270b945 (fixed)
Vendor states this is fixed in 61d38b5ce2782bff3cacaacbb8164087a73ed1a5 (fixed)
Vendor states this is fixed in 74058c0a9fc8b2b4d5f4a0ef7ee2cfa66a9e49cf (fixed)
Vendor states this is fixed in 81a2bca52d43fc9d9abf07408b91255131c5dc53 (fixed)
Vendor states this is fixed in 91b99db7a92e57ff48a96a1b10fddfd2547e7f53 (fixed)
Vendor states this is fixed in c28b0ca029edf5d0558abcd76cb8c732706cd339 (fixed)
Vendor states this is fixed in f81a5bc9e924ee1950e0dd82bd10749048390f6e (fixed)
Vendor states this is fixed in 2.6.29 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.53 (unaffected)
Vendor states this is fixed in 6.17.3 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.112 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card