{"vulnerability": "CVE-2024-39472", "sightings": [{"uuid": "f03fcfd5-4022-4b37-be6d-d90bd26559fc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-39472", "type": "seen", "source": "https://t.me/cvedetector/85", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-39472 - In the Linux kernel, the following vulnerability h\", \n  \"Content\": \"CVE ID : CVE-2024-39472 \nPublished : July 5, 2024, 7:15 a.m. | 17\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved: \n \nxfs: fix log recovery buffer allocation for the legacy h_size fixup \n \nCommit a70f9fe52daa (\"xfs: detect and handle invalid iclog size set by \nmkfs\") added a fixup for incorrect h_size values used for the initial \numount record in old xfsprogs versions.  Later commit 0c771b99d6c9 \n(\"xfs: clean up calculation of LR header blocks\") cleaned up the log \nreover buffer calculation, but stoped using the fixed up h_size value \nto size the log recovery buffer, which can lead to an out of bounds \naccess when the incorrect h_size does not come from the old mkfs \ntool, but a fuzzer. \n \nFix this by open coding xlog_logrec_hblks and taking the fixed h_size \ninto account for this calculation. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Jul 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-07-05T09:34:11.000000Z"}]}