xfs: fix log recovery buffer allocation for the legacy h_size fixup
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.3epss 0.3%
exploitation probability
0.3%top 85% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:H
Affected products
Linux · LinuxReferences
https://git.kernel.org/stable/c/45cf976008ddef4a9c9a30310c9b4fb2a9a6602ahttps://git.kernel.org/stable/c/57835c0e7152e36b03875dd6c56dfeed685c1b1fhttps://git.kernel.org/stable/c/c2389c074973aa94e34992e7f66dac0de37595b5https://git.kernel.org/stable/c/f754591b17d0ee91c2b45fe9509d0cdc420527cbhttps://lists.debian.org/debian-lts-announce/2025/01/msg00001.html