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-49856x86/sgx: Fix deadlock in SGX NUMA node search

Description

In the Linux kernel, the following vulnerability has been resolved: x86/sgx: Fix deadlock in SGX NUMA node search When the current node doesn't have an EPC section configured by firmware and all other EPC sections are used up, CPU can get stuck inside the while loop that looks for an available EPC page from remote nodes indefinitely, leading to a soft lockup. Note how nid_of_current will never be equal to nid in that while loop because nid_of_current is not set in sgx_numa_mask. Also worth mentioning is that it's perfectly fine for the firmware not to setup an EPC section on a node. While setting up an EPC section on each node can enhance performance, it is not a requirement for functionality. Rework the loop to start and end on *a* node that has SGX memory. This avoids the deadlock looking for the current SGX-lacking node to show up in the loop when it never will.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 19 months 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-49856, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 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: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < 40fb64257dab507d86b5f1f2a62f3669ef0c91a8
    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < 20c96d0aaabfe361fc2a11c173968dc67feadbbf
    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < fb2d057539eda67ec7cfc369bf587e6518a9b99d
    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < 0f89fb4042c08fd143bfc28af08bf6c8a0197eea
    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < 8132510c915815e6b537ab937d94ed66893bc7b8
    • affected 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 – < 9c936844010466535bd46ea4ce4656ef17653644
  • Linux · Linux

    • affected 5.13
    • unaffected < 5.13
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .