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-39472xfs: fix log recovery buffer allocation for the legacy h_size fixup

Description

In the Linux kernel, the following vulnerability has been resolved: xfs: fix log recovery buffer allocation for the legacy h_size fixup Commit a70f9fe52daa ("xfs: detect and handle invalid iclog size set by mkfs") added a fixup for incorrect h_size values used for the initial umount record in old xfsprogs versions. Later commit 0c771b99d6c9 ("xfs: clean up calculation of LR header blocks") cleaned up the log reover buffer calculation, but stoped using the fixed up h_size value to size the log recovery buffer, which can lead to an out of bounds access when the incorrect h_size does not come from the old mkfs tool, but a fuzzer. Fix this by open coding xlog_logrec_hblks and taking the fixed h_size into account for this calculation.

Timeline

  1. ID reserved

    By Linux

  2. · 10 days later

    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-39472, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:H
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.25% · top 83% of all CVEs (13 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: High 7.3.

Affected products

  • Linux · Linux

    • affected 0c771b99d6c9a0552fea5cc43669b726dad8f659 – < f754591b17d0ee91c2b45fe9509d0cdc420527cb
    • affected 0c771b99d6c9a0552fea5cc43669b726dad8f659 – < 57835c0e7152e36b03875dd6c56dfeed685c1b1f
    • affected 0c771b99d6c9a0552fea5cc43669b726dad8f659 – < c2389c074973aa94e34992e7f66dac0de37595b5
    • affected 0c771b99d6c9a0552fea5cc43669b726dad8f659 – < 45cf976008ddef4a9c9a30310c9b4fb2a9a6602a
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.15.165 – ≤ 5.15.*
    • unaffected 6.1.105 – ≤ 6.1.*
    • unaffected 6.6.46 – ≤ 6.6.*
    • unaffected 6.10 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .