net/dpaa2: Avoid explicit cpumask var allocation on stack
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 93ddf0b211a0a0367d01c9587169c16ed77b4b98 · < 5e4f25091e6d06e99a23f724c839a58a8776a527| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/dpaa2: 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/dpaa2 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 establish whether an attacker can trigger the issue or specify access, authentication, or user-interaction requirements.
Anyone running a Linux kernel with net/dpaa2 and CONFIG_CPUMASK_OFFSTACK=y should check their kernel version against the vendor advisory; affected versions are not specified.