CVE-2024-26982

I

n 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. [[email protected]: whitespace fix]

Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*

History

04 Nov 2025, 18:15

Type Values Removed Values Added
References
  • () https://lists.fedoraproject.org/archives/list/[email protected]/message/4EZ6PJW7VOZ224TD7N4JZNU6KV32ZJ53/ -
  • () https://lists.fedoraproject.org/archives/list/[email protected]/message/DAMSOZXJEPUOXW33WZYWCVAY7Z5S7OOY/ -
  • () https://lists.fedoraproject.org/archives/list/[email protected]/message/GCBZZEC7L7KTWWAS2NLJK6SO3IZIL4WW/ -

03 Nov 2025, 20:16

Type Values Removed Values Added
References
  • () https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html -
  • () https://lists.debian.org/debian-lts-announce/2025/05/msg00045.html -

16 Apr 2025, 19:15

Type Values Removed Values Added
Summary (en) 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. [[email protected]: whitespace fix] Link: https://lkml.kernel.org/r/[email protected] (en) 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. [[email protected]: whitespace fix]

13 Mar 2025, 13:15

Type Values Removed Values Added
CPE cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 7.1
First Time Linux
Linux linux Kernel
References
  • () https://git.kernel.org/stable/c/32c114a58236fe67141634774559f21f1dc96fd7 -
  • () https://git.kernel.org/stable/c/4a1b6f89825e267e156ccaeba3d235edcac77f94 -
  • () https://git.kernel.org/stable/c/5b99dea79650b50909c50aba24fbae00f203f013 -
  • () https://git.kernel.org/stable/c/cf46f88b92cfc0e32bd8a21ba1273cff13b8745f -
References () https://git.kernel.org/stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5 - () https://git.kernel.org/stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5 - Mailing List, Patch
References () https://git.kernel.org/stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395 - () https://git.kernel.org/stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395 - Mailing List, Patch
References () https://git.kernel.org/stable/c/be383effaee3d89034f0828038f95065b518772e - () https://git.kernel.org/stable/c/be383effaee3d89034f0828038f95065b518772e - Mailing List, Patch
CWE CWE-125

21 Nov 2024, 09:03

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5 - () https://git.kernel.org/stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5 -
References () https://git.kernel.org/stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395 - () https://git.kernel.org/stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395 -
References () https://git.kernel.org/stable/c/be383effaee3d89034f0828038f95065b518772e - () https://git.kernel.org/stable/c/be383effaee3d89034f0828038f95065b518772e -

03 May 2024, 06:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-05-01 06:15

Updated : 2025-11-04 18:15


NVD link : CVE-2024-26982

Mitre link : CVE-2024-26982

CVE.ORG link : CVE-2024-26982


JSON object : View

Products Affected
CWE
CWE-125

Out-of-bounds Read