Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-26704: ext4: fix double-free of blocks due to wrong extents moved_len

Noroxi assessment

Priority: Monitor (action score 31/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.26% (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 185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1, 2883940b19c38d5884c8626483811acf4d7e148f, 55583e899a5357308274601364741a83e78d6ac4.
  • Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1, 2883940b19c38d5884c8626483811acf4d7e148f, 55583e899a5357308274601364741a83e78d6ac4 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: ext4: fix double-free of blocks due to wrong extents moved_len In ext4_move_extents(), moved_len is only updated when all moves are successfully executed, and only discards orig_inode and donor_inode preallocations when moved_len is not zero. When the loop fails to exit after successfully moving some extents, moved_len is not updated and remains at 0, so it does not discard the preallocations. If the moved extents overlap with the preallocated extents, the overlapped extents are freed twice in ext4_mb_release_inode_pa() and ext4_process_freed_data() (as described in commit 94d7c16cbbbd ("ext4: Fix double-free of blocks with EXT4_IOC_MOVE_EXT")), and bb_free is incremented twice. Hence when trim is executed, a zero-division bug is triggered in mb_update_avg_fragment_size() because bb_free is not zero and bb_fragments is zero. Therefore, update move_len after each extent move to avoid the issue.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 3, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 19th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 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.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-26704

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

  • 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.

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
debiandebian linux

Affected versions

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

  • debian debian linux10.0
  • linux linux kernel4.20 and later · before 5.4.269
  • linux linux kernel5.5 and later · before 5.10.210
  • linux linux kernel5.11 and later · before 5.15.149
  • linux linux kernel3.18 and later · before 4.19.307
  • linux linux kernel6.2 and later · before 6.6.18
  • linux linux kernel6.7 and later · before 6.7.6
  • linux linux kernel5.16 and later · before 6.1.79
  • linux linux kernel6.8

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

    • 3.18affected
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before b4fbb89d722cbb16beaaea234b7230faaaf68c71affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before afbcad9ae7d6d11608399188f03a837451b6b3a1affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before d033a555d9a1cf53dbf3301af7199cc4a4c8f537affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before afba9d11320dad5ce222ac8964caf64b7b4bedb1affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before 185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before 2883940b19c38d5884c8626483811acf4d7e148faffected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before 559ddacb90da1d8786dd8ec4fd76bbfa404eaef6affected · git
    • fcf6b1b729bcd23f2b49a84fb33ffbb44712ee6a and later · before 55583e899a5357308274601364741a83e78d6ac4affected · git
    • before 3.18not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.7-16.7.7-1
Red Hat:rhel_aus:8.6::baseosbpftoolbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseosbpftool-debuginfobefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernelbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-abi-stablelistsbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-corebefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debugbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-corebefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-debuginfobefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-develbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modulesbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debug-modules-extrabefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfobefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-develbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-docbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modulesbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-modules-extrabefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-toolsbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-debuginfobefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseoskernel-tools-libsbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseosperfbefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6
Red Hat:rhel_aus:8.6::baseosperf-debuginfobefore 0:4.18.0-372.123.1.el8_60:4.18.0-372.123.1.el8_6

+96

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-26702Apr 3, 2024 · iio: magnetometer: rm3100: add boundary check for the value read from RM3100_REG_TMRC
    22Monitor
  • ← EarlierCVE-2024-26703Apr 3, 2024 · tracing/timerlat: Move hrtimer_init to timerlat_fd open()
    22Monitor
  • Later →CVE-2024-26705Apr 3, 2024 · parisc: BTLB: Fix crash when setting up BTLB at CPU bringup
    22Monitor

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 Linux185eab30486ba3e7bf8b9c2e049c79a06ffd2bc1Vendor (CNA)
Linux Linux2883940b19c38d5884c8626483811acf4d7e148fVendor (CNA)
Linux Linux55583e899a5357308274601364741a83e78d6ac4Vendor (CNA)
Linux Linux559ddacb90da1d8786dd8ec4fd76bbfa404eaef6Vendor (CNA)
Linux Linuxafba9d11320dad5ce222ac8964caf64b7b4bedb1Vendor (CNA)
Linux Linuxafbcad9ae7d6d11608399188f03a837451b6b3a1Vendor (CNA)
Linux Linuxb4fbb89d722cbb16beaaea234b7230faaaf68c71Vendor (CNA)
Linux Linuxd033a555d9a1cf53dbf3301af7199cc4a4c8f537Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.47.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

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.

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.

  • CVE-2024-3581444 days apartswiotlb: Fix double-allocation of slots due to broken alignment handling
    35Monitor
  • CVE-2024-266940 days apartwifi: iwlwifi: fix double-free bug
    31Monitor
  • CVE-2024-267480 days apartusb: cdns3: fix memory double free when handle zero packet
    31Monitor
  • CVE-2024-267821 days apartmptcp: fix double-free on socket dismantle
    31Monitor
  • CVE-2024-267921 days apartbtrfs: fix double free of anonymous device after snapshot creation failure
    31Monitor
  • CVE-2024-266532 days apartusb: misc: ljca: Fix double free in error handling path
    31Monitor

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
high · data or configuration can be modified
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
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

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

References

All records