x86/MCE/AMD: Use an u64 for bank_map
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ a0bc32b3cacf194dc479b342f006203fd1e1941a · < 4c1cdec319b9aadb65737c3eb1f5cb74bd6aa156| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/MCE/AMD: Use an u64 for bank_map
Thee maximum number of MCA banks is 64 (MAX_NR_BANKS), see
a0bc32b3cacf ("x86/mce: Increase maximum number of banks to 64").
However, the bank_map which contains a bitfield of which banks to initialize is of type unsigned int and that overflows when those bit numbers are >= 32, leading to UBSAN complaining correctly:
UBSAN: shift-out-of-bounds in arch/x86/kernel/cpu/mce/amd.c:1365:38 shift exponent 32 is too large for 32-bit type 'int'
Change the bank_map to a u64 and use the proper BIT_ULL() macro when modifying bits in there.
[ bp: Rewrite commit message. ]
From the CVE record · Linux
The Linux kernel's AMD x86 machine-check code uses a 32-bit bank map even though it supports up to 64 banks. Initializing bank numbers 32 or higher can cause an out-of-bounds shift reported by UBSAN. The input does not establish whether an attacker can trigger this or specify access or user-interaction requirements.
Engineers running the Linux kernel should check affected versions against the vendor advisory; no versions are specified in the input.