Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-43828ext4: fix infinite loop when replaying fast_commit

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix infinite loop when replaying fast_commit When doing fast_commit replay an infinite loop may occur due to an uninitialized extent_status struct. ext4_ext_determine_insert_hole() does not detect the replay and calls ext4_es_find_extent_range(), which will return immediately without initializing the 'es' variable. Because 'es' contains garbage, an integer overflow may happen causing an infinite loop in this function, easily reproducible using fstest generic/039. This commit fixes this issue by unconditionally initializing the structure in function ext4_es_find_extent_range(). Thanks to Zhang Yi, for figuring out the real problem!

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-43828, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 5ed0496e383cb6de120e56991385dce70bbb87c1
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 0619f7750f2b178a1309808832ab20d85e0ad121
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 181e63cd595c688194e07332f9944b3a63193de2
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < c6e67df64783e99a657ef2b8c834ba2bf54c539c
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 81f819c537d29932e4b9267f02411cbc8b355178
    • affected 8016e29f4362e285f0f7e38fadc61a5b7bdfdfa2 – < 907c3fe532253a6ef4eb9c4d67efb71fab58c706
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.224 – ≤ 5.10.*
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.103 – ≤ 6.1.*
    • unaffected 6.6.44 – ≤ 6.6.*
    • unaffected 6.10.3 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-43828 badge
[![CVE-2024-43828](https://cveledger.app/badge/CVE-2024-43828.svg)](https://cveledger.app/cve/CVE-2024-43828)

Record last updated .