Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-42094, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 2b085521be5292016097b5e7ca81b26be3f7098d
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 842afb47d84536fc976fece8fb6c54bea711ad1a
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 9dadab0db7d904413ea1cdaa13f127da05c31e71
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 0af718a690acc089aa1bbb95a93df833d864ef53
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < d85ca8179a54ff8cf1e1f8c3c9e3799831319bae
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 724e7965af054079242b8d6f7e50ee226730a756
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < 2d090c7f7be3b26fcb80ac04d08a4a8062b1d959
    • affected 2356f4cb191100a5e92d537f13e5efdbc697e9cb – < be4e1304419c99a164b4c0e101c7c2a756b635b9
  • Linux · Linux

    • affected 2.6.21
    • unaffected < 2.6.21
    • unaffected 4.19.317 – ≤ 4.19.*
    • unaffected 5.4.279 – ≤ 5.4.*
    • unaffected 5.10.221 – ≤ 5.10.*
    • unaffected 5.15.162 – ≤ 5.15.*
    • unaffected 6.1.97 – ≤ 6.1.*
    • unaffected 6.6.37 – ≤ 6.6.*
    • unaffected 6.9.8 – ≤ 6.9.*
    • unaffected 6.10 – ≤ *

References

References12

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-42094 badge
[![CVE-2024-42094](https://cveledger.app/badge/CVE-2024-42094.svg)](https://cveledger.app/cve/CVE-2024-42094)

Record last updated .