xfs: fix log recovery buffer allocation for the legacy h_size fixup
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 45cf976008ddef4a9c9a30310c9b4fb2a9a6602a, Kernel 57835c0e7152e36b03875dd6c56dfeed685c1b1f, Kernel c2389c074973aa94e34992e7f66dac0de37595b5 and 1 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.10, >=0c771b99d6c9a0552fea5cc43669b726dad8f659 <45cf976008ddef4a9c9a30310c9b4fb2a9a6602a, >=0c771b99d6c9a0552fea5cc43669b726dad8f659 <57835c0e7152e36b03875dd6c56dfeed685c1b1f, >=0c771b99d6c9a0552fea5cc43669b726dad8f659 <c2389c074973aa94e34992e7f66dac0de37595b5, >=0c771b99d6c9a0552fea5cc43669b726dad8f659 <f754591b17d0ee91c2b45fe9509d0cdc420527cb | 45cf976008ddef4a9c9a30310c9b4fb2a9a6602a, 57835c0e7152e36b03875dd6c56dfeed685c1b1f, c2389c074973aa94e34992e7f66dac0de37595b5, f754591b17d0ee91c2b45fe9509d0cdc420527cb |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket