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

Published May 1, 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 fillmetaindex().

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. Fillmetaindex() is called to allocate (via emptymetaindex()) 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 fillmetaindex() is subsequently called again on another read operation, locatemetaindex() 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]

Other sources

In the Linux kernel, the following vulnerability has been resolved:

Squashfs: check the inode number is not the invalid value of zero

The Linux kernel CVE team has assigned CVE-2024-26982 to this issue.

Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024050141-CVE-2024-26982-8675@gregkh/T

Red Hat

Affected Software

16 affected componentsFixes available
IBM Security Verify Governance<=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
Linux Linux kernel<6.6.30
Linux Linux kernel>=6.7<6.8.8
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Linux Linux kernel=6.9-rc3
Linux Linux kernel=6.9-rc4
debian/linux<=5.10.223-1, <=5.10.234-1, <=6.1.129-1
6.1.135-16.12.22-16.12.25-1
redhat/kernel<6.8.8
6.8.8
redhat/kernel<6.9
6.9
Microsoft cbl2 kernel 5.15.182.1-1
Microsoft cbl2 kernel 5.15.182.1-1
Microsoft cbl2 kernel 5.15.179.1-1

Event History

May 1, 2024
CVE Published
via MITRE·05:27 AM
Data Sourced
via MITRE·05:27 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·07:27 PM
DescriptionSeverityAffected Software
Jul 11, 2024
Data Sourced
via Launchpad·07:45 PM
Description
Apr 27, 2025
Data Sourced
via Ubuntu·12:16 AM
RemedyDescriptionSeverityAffected Software
Sep 4, 2025
Data Sourced
via Microsoft·02:33 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·02:33 AM
Affected Software
Updated
via Microsoft·02:33 AM
DescriptionSeverity

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

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.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203