EFI/CPER: don't dump the entire memory region
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3d8c11efd528d56972d44ed0de51c4e11a9a4fa9 · < a8419f5f2c5f2d80848ddabb2b95cf0da84a5f91| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
EFI/CPER: don't dump the entire memory region
The current logic at cper_print_fw_err() doesn't check if the error record length is big enough to handle offset. On a bad firmware, if the ofset is above the actual record, length -= offset will underflow, making it dump the entire memory.
The end result can be:
- the logic taking a lot of time dumping large regions of memory; - data disclosure due to the memory dumps; - an OOPS, if it tries to dump an unmapped memory region.
Fix it by checking if the section length is too small before doing a hex dump.
[ rjw: Subject tweaks ]
From the CVE record · Linux
The Linux kernel’s EFI/CPER error-reporting code can underflow a length calculation when a bad firmware error record has an offset beyond its actual length. This can dump large memory regions, disclose data, or cause an OOPS; the input does not establish an attacker path or authentication requirements.
Engineers running Linux kernels with the affected EFI/CPER code should check their vendor’s advisory for affected versions.