LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42094: net/iucv: Avoid explicit cpumask var allocation on stack

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2024-42094 is a Linux kernel issue where IUCV networking code could place a CPU mask object on the kernel stack in configurations where that is discouraged, creating a potential stack overflow risk. The public record does not provide CVSS, impact scope, or exploitation evidence.

Executive priority

Handle through the normal kernel security update process unless affected critical infrastructure or vendor appliances are in scope. The business urgency is uncertain because severity and exploitability are not established in the provided sources.

Technical view

The fix changes net/iucv code to use cpumask_var allocation APIs instead of explicit stack allocation when CONFIG_CPUMASK_OFFSTACK=y. The source describes this as config-neutral allocation to avoid potential kernel stack overflow. Multiple stable kernel commits are referenced as fixes.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions or downstream kernels that include the vulnerable net/iucv code. Systems using vendor-maintained kernels should follow their distribution or device vendor advisories, including Debian LTS and Siemens notices cited in the record.

Exploitation context

The source bundle says KEV is false and provides no cited evidence of active exploitation, public exploit availability, or attacker prerequisites. Treat exploitation status as unconfirmed rather than absent.

Researcher notes

The core issue is defensive allocation hygiene in net/iucv, not a fully characterized exploit chain. Useful follow-up is mapping affected kernel branches and downstream backports, especially where IUCV and CONFIG_CPUMASK_OFFSTACK are enabled.

Mitigation direction

  • Update to a kernel containing the referenced stable fixes.
  • Apply distribution or appliance vendor kernel updates when available.
  • Review Debian LTS and Siemens advisories if those environments apply.
  • If no vendor fix is listed, monitor vendor guidance for backports.

Validation and detection

  • Inventory Linux kernel versions across affected servers and appliances.
  • Check kernel configuration for CONFIG_CPUMASK_OFFSTACK where configuration data is available.
  • Confirm whether deployed kernels include the referenced stable commits or vendor backports.
  • Review vendor advisories for affected Siemens or Debian LTS products.
Prepared
Confidence
medium
Sources
12

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-42094 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
13Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cb, 2356f4cb191100a5e92d537f13e5efdbc697e9cbunaffected
LinuxLinux2.6.21, 0, 4.19.317, 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.