Squashfs: check the inode number is not the invalid value of zero
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.4.291, 5.10.235, 5.15.179, 6.1.130, 6.6.30, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: Squashfs: check the inode number is not the invalid value of zero Syskiller has produced an out of bounds access in fill_meta_index(). That out of bounds access is ultimately caused because the inode has an inode number with the invalid value of zero, which was not checked. The reason this causes the out of bounds access is due to following sequence of events: 1. Fill_meta_index() is called to allocate (via empty_meta_index()) and fill a metadata index. It however suffers a data read error and aborts, invalidating the newly returned empty metadata index. It does this by setting the inode number of the index to zero, which means unused (zero is not a valid inode number). 2. When fill_meta_index() is subsequently called again on another read operation, locate_meta_index() returns the previous index because it matches the inode number of 0. Because this index has been returned it is expected to have been filled, and because it hasn't been, an out of bounds access is performed. This patch adds a sanity check which checks that the inode number is not zero when the inode is created and returns -EINVAL if it is. [phillip@squashfs.org.uk: whitespace fix]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in 32c114a58236fe67141634774559f21f1dc96fd7; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in 4a1b6f89825e267e156ccaeba3d235edcac77f94; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in cf46f88b92cfc0e32bd8a21ba1273cff13b8745f; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in 5b99dea79650b50909c50aba24fbae00f203f013; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in be383effaee3d89034f0828038f95065b518772e; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in 7def00ebc9f2d6a581ddf46ce4541f84a10680e5; From 6545b246a2c815a8fcd07d58240effb6ec3481b1 · fixed in 9253c54e01b6505d348afbc02abaa4d9f8a01395
- Linux Linux
2.6.29
- KernelLinux
From 2.6.29 · fixed in 5.4.291; From 5.5.0 · fixed in 5.10.235; From 5.11.0 · fixed in 5.15.179; From 5.16.0 · fixed in 6.1.130; From 6.2.0 · fixed in 6.6.30; From 6.7.0 · fixed in 6.8.8
References 7
git.kernel.org
- stable/c/32c114a58236fe67141634774559f21f1dc96fd7
- stable/c/4a1b6f89825e267e156ccaeba3d235edcac77f94
- stable/c/cf46f88b92cfc0e32bd8a21ba1273cff13b8745f
- stable/c/5b99dea79650b50909c50aba24fbae00f203f013
- stable/c/be383effaee3d89034f0828038f95065b518772e
- stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5
- stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395