LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue involves a network driver allocating CPU mask data on the stack in a way that can risk stack overflow on certain kernel builds. The public record does not provide CVSS severity, exploit evidence, or a complete operational impact statement, so urgency depends on whether affected kernels and DPAA2-related systems are present.

Executive priority

Prioritize identification over emergency response. There is no sourced exploitation evidence or severity score, but kernel issues in networking paths can affect availability and embedded infrastructure. Patch through normal kernel maintenance unless your vendor rates it higher.

Technical view

CVE-2024-42093 is in Linux net/dpaa2. The fix changes explicit stack allocation of cpumask variables to cpumask_var APIs so allocation respects CONFIG_CPUMASK_OFFSTACK. Sources describe a potential stack overflow risk, with fixes referenced through Linux stable commits and downstream advisories.

Likely exposure

Exposure is most plausible on Linux systems using affected kernel versions with the DPAA2 networking code present, especially builds using CONFIG_CPUMASK_OFFSTACK=y. The bundle also cites Debian LTS and Siemens advisories, indicating downstream product and distribution relevance, but affected deployments must be confirmed locally.

Exploitation context

The source bundle does not cite active exploitation, public exploit use, KEV listing, or attacker prerequisites. Treat this as a kernel hardening and stability/security update unless vendor advisories for your platform state stronger impact.

Researcher notes

Key evidence is limited to the Linux kernel resolution text and stable commit references. The issue is implementation-specific: stack cpumask allocation in net/dpaa2 was replaced with cpumask_var APIs. Validate branch-specific fixed status against the cited stable commits rather than relying only on flattened version lists.

Mitigation direction

  • Review Linux stable fixes referenced for your maintained kernel branch.
  • Apply vendor or distribution kernel updates when available.
  • Check Debian LTS and Siemens advisories if those products are in scope.
  • Avoid inventing local mitigations; follow kernel vendor guidance.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Identify systems using DPAA2 networking or NXP/Freescale data path hardware.
  • Check kernel configuration for CONFIG_CPUMASK_OFFSTACK=y where available.
  • Confirm whether vendor kernel packages include the referenced stable commits.
  • Track exceptions where appliances depend on Siemens or Debian guidance.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42093 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
3ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98, 93ddf0b211a0a0367d01c9587169c16ed77b4b98unaffected
LinuxLinux4.16, 0, 5.4.279, 5.10.221, 5.15.162, 6.1.97, 6.6.37, 6.9.8, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.