high
7.1
CWE
125
Advisory Published
CVE Published
Updated

CVE-2024-26982: Squashfs: check the inode number is not the invalid value of zero

First published: Wed May 01 2024(Updated: )

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] Link:

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel<6.6.30
Linux Kernel>=6.7<6.8.8
Linux Kernel=6.9-rc1
Linux Kernel=6.9-rc2
Linux Kernel=6.9-rc3
Linux Kernel=6.9-rc4
redhat/kernel<6.8.8
6.8.8
redhat/kernel<6.9
6.9
IBM Security Verify Governance - Identity Manager<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Software Stack<=ISVG 10.0.2
IBM Security Verify Governance, Identity Manager Virtual Appliance<=ISVG 10.0.2
IBM Security Verify Governance Identity Manager Container<=ISVG 10.0.2
debian/linux<=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.128-1
6.12.21-1
6.12.22-1

Remedy

https://git.kernel.org/stable/c/7def00ebc9f2d6a581ddf46ce4541f84a10680e5

Remedy

https://git.kernel.org/stable/c/9253c54e01b6505d348afbc02abaa4d9f8a01395

Remedy

https://git.kernel.org/stable/c/be383effaee3d89034f0828038f95065b518772e

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2024-26982?

    The severity level of CVE-2024-26982 is classified as high due to its potential for causing out of bounds access in the Linux kernel.

  • How do I fix CVE-2024-26982?

    To fix CVE-2024-26982, update your kernel to the specified versions, such as Red Hat kernel 6.8.8 or 6.9, or Debian linux versions 6.12.12-1 or 6.12.15-1.

  • Which systems are affected by CVE-2024-26982?

    CVE-2024-26982 affects certain versions of the Linux kernel, specifically those prior to the patched releases mentioned.

  • What does CVE-2024-26982 exploit?

    CVE-2024-26982 exploits an out of bounds access in the fill_meta_index() function, which is triggered by an invalid inode number.

  • Is there a workaround for CVE-2024-26982?

    There are no known workarounds for CVE-2024-26982; the only solution is to apply the necessary updates to the kernel.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203