Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 32c114a58236fe67141634774559f21f1dc96fd7, 4a1b6f89825e267e156ccaeba3d235edcac77f94, 5b99dea79650b50909c50aba24fbae00f203f013; cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 5.15.179.1-1; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 32c114a58236fe67141634774559f21f1dc96fd7, 4a1b6f89825e267e156ccaeba3d235edcac77f94, 5b99dea79650b50909c50aba24fbae00f203f013; cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0 5.15.179.1-1; cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0 CBL-Mariner Releases or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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]

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
May 1, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 20th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-26982

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernelbefore 6.6.30
  • linux linux kernel6.7 and later · before 6.8.8
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.29affected
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before 32c114a58236fe67141634774559f21f1dc96fd7affected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before 4a1b6f89825e267e156ccaeba3d235edcac77f94affected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before cf46f88b92cfc0e32bd8a21ba1273cff13b8745faffected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before 5b99dea79650b50909c50aba24fbae00f203f013affected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before be383effaee3d89034f0828038f95065b518772eaffected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before 7def00ebc9f2d6a581ddf46ce4541f84a10680e5affected · git
    • 6545b246a2c815a8fcd07d58240effb6ec3481b1 and later · before 9253c54e01b6505d348afbc02abaa4d9f8a01395affected · git
    • before 2.6.29not affected · semver
    • 5.4.291 and later · up to and including 5.4.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.28.1.el9_47.3.0-427.28.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.28.1.el9_45.14.0-427.28.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-26973May 1, 2024 · fat: fix uninitialized field in nostale filehandles
    22Monitor
  • ← EarlierCVE-2024-26974May 1, 2024 · crypto: qat - resolve race condition during AER recovery
    28Monitor
  • Later →CVE-2024-26988May 1, 2024 · init/main.c: Fix potential static_command_line memory overflow
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux32c114a58236fe67141634774559f21f1dc96fd7Vendor (CNA)
Linux Linux4a1b6f89825e267e156ccaeba3d235edcac77f94Vendor (CNA)
Linux Linux5b99dea79650b50909c50aba24fbae00f203f013Vendor (CNA)
Linux Linux7def00ebc9f2d6a581ddf46ce4541f84a10680e5Vendor (CNA)
Linux Linux9253c54e01b6505d348afbc02abaa4d9f8a01395Vendor (CNA)
Linux Linuxbe383effaee3d89034f0828038f95065b518772eVendor (CNA)
Linux Linuxcf46f88b92cfc0e32bd8a21ba1273cff13b8745fVendor (CNA)
cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.05.15.179.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.28.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.137-1~deb11u1 · Debian:11Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.28.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+7

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (14 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records