net/iucv: Avoid explicit cpumask var allocation on stack
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2356f4cb191100a5e92d537f13e5efdbc697e9cb · < 724e7965af054079242b8d6f7e50ee226730a756| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/iucv: Avoid explicit cpumask var allocation on stack
For CONFIG_CPUMASK_OFFSTACK=y kernel, explicit allocation of cpumask variable on stack is not recommended since it can cause potential stack overflow.
Instead, kernel code should always use *cpumask_var API(s) to allocate cpumask var in config-neutral way, leaving allocation strategy to CONFIG_CPUMASK_OFFSTACK.
Use *cpumask_var API(s) to address it.
From the CVE record · Linux
The Linux kernel's net/iucv code explicitly allocates a cpumask variable on the stack, which can cause a potential stack overflow when CONFIG_CPUMASK_OFFSTACK=y. The input does not specify whether an attacker can trigger it or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels with CONFIG_CPUMASK_OFFSTACK=y should check their kernels; affected versions were not provided.