Squashfs: fix uninit-value in squashfs_get_parent
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 1b3ccd0019132880c94bb00ca7088c1749308f82, Kernel 382a47fae449e554ef1e8c198667fd2f3270b945, Kernel 61d38b5ce2782bff3cacaacbb8164087a73ed1a5 and 5 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =2.6.29, >=122601408d20c77704268f1dea9f9ce4abf997c2 <1b3ccd0019132880c94bb00ca7088c1749308f82, >=122601408d20c77704268f1dea9f9ce4abf997c2 <382a47fae449e554ef1e8c198667fd2f3270b945, >=122601408d20c77704268f1dea9f9ce4abf997c2 <61d38b5ce2782bff3cacaacbb8164087a73ed1a5, >=122601408d20c77704268f1dea9f9ce4abf997c2 <74058c0a9fc8b2b4d5f4a0ef7ee2cfa66a9e49cf, >=122601408d20c77704268f1dea9f9ce4abf997c2 <81a2bca52d43fc9d9abf07408b91255131c5dc53, >=122601408d20c77704268f1dea9f9ce4abf997c2 <91b99db7a92e57ff48a96a1b10fddfd2547e7f53, >=122601408d20c77704268f1dea9f9ce4abf997c2 <c28b0ca029edf5d0558abcd76cb8c732706cd339, >=122601408d20c77704268f1dea9f9ce4abf997c2 <f81a5bc9e924ee1950e0dd82bd10749048390f6e | 1b3ccd0019132880c94bb00ca7088c1749308f82, 382a47fae449e554ef1e8c198667fd2f3270b945, 61d38b5ce2782bff3cacaacbb8164087a73ed1a5, 74058c0a9fc8b2b4d5f4a0ef7ee2cfa66a9e49cf, 81a2bca52d43fc9d9abf07408b91255131c5dc53, 91b99db7a92e57ff48a96a1b10fddfd2547e7f53, c28b0ca029edf5d0558abcd76cb8c732706cd339, f81a5bc9e924ee1950e0dd82bd10749048390f6e |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket