EDAC/bluefield: Fix potential integer overflow
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 82413e562ea6eadfb6de946dcc6f74af31d64e7f · < fdb90006184aa84c7b4e09144ed0936d4e1891a7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
EDAC/bluefield: Fix potential integer overflow
The 64-bit argument for the "get DIMM info" SMC call consists of mem_ctrl_idx left-shifted 16 bits and OR-ed with DIMM index. With mem_ctrl_idx defined as 32-bits wide the left-shift operation truncates the upper 16 bits of information during the calculation of the SMC argument.
The mem_ctrl_idx stack variable must be defined as 64-bits wide to prevent any potential integer overflow, i.e. loss of data from upper 16 bits.
From the CVE record · Linux
In the Linux kernel’s EDAC/bluefield code, a 32-bit memory-controller index can lose its upper 16 bits when shifted to form the argument for a “get DIMM info” SMC call. The input does not describe what an attacker could do, how the issue could be reached, or whether authentication or user interaction is required.
Engineers running Linux kernels with EDAC/bluefield should check their deployments; affected versions are not specified.