md/raid5: validate payload size before accessing journal metadata
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b4c625c67362b3940f619c1a836b4e8329106658 · < 73ce72edd113374801045924d4417199963f73a3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
md/raid5: validate payload size before accessing journal metadata
r5c_recovery_analyze_meta_block() and r5l_recovery_verify_data_checksum_for_mb() iterate over payloads in a journal metadata block using on-disk payload size fields without validating them against the remaining space in the metadata block.
A corrupted journal contains payload sizes extending beyond the PAGE_SIZE boundary can cause out-of-bounds reads when accessing payload fields or computing offsets.
Add bounds validation for each payload type to ensure the full payload fits within meta_size before processing.
From the CVE record · Linux
The Linux kernel's md/raid5 journal recovery code does not validate payload sizes against the remaining space in a metadata block. Processing a corrupted journal with payload sizes extending beyond the page boundary can cause out-of-bounds reads. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel should check whether their kernel includes the md/raid5 journal recovery fix; affected versions are not specified.