mm: vmalloc: check if a hash-index is in cpu_possible_mask
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.416.9.106.10In the Linux kernel, the following vulnerability has been resolved:
mm: vmalloc: check if a hash-index is in cpu_possible_mask
The problem is that there are systems where cpu_possible_mask has gaps between set CPUs, for example SPARC. In this scenario addr_to_vb_xa() hash function can return an index which accesses to not-possible and not setup CPU area using per_cpu() macro. This results in an oops on SPARC.
A per-cpu vmap_block_queue is also used as hash table, incorrectly assuming the cpu_possible_mask has no gaps. Fix it by adjusting an index to a next possible CPU.
From the CVE record · Linux
The Linux kernel’s vmalloc code can access an uninitialized per-CPU area when the possible-CPU mask has gaps, causing an oops on SPARC. The input does not describe an attacker-controlled trigger, access requirements, or user interaction.
Engineers running Linux kernels on systems whose possible-CPU mask has gaps, including SPARC, should check their installations; affected versions are not specified.