CVE-2024-49856: Linux kernel · x86/sgx: Fix deadlock in SGX NUMA node search
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 5.15.0-1073.79~20.04.1 : update Linux kernel when convenient.
Data as of 29 Oct 2026, 22:34 UTC
- Patch
- Available – fixed in 5.15.0-1073.79~20.04.1, 5.15.0-1078.87~20.04.1, 5.15.0-1072.80~20.04.1 +58
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7304-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-nvidiapkg:deb/ubuntu/linux-azure-nvidia?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
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.
References
- ubuntu.com/security/CVE-2024-49856 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-49856 (opens in a new tab)
- git.kernel.org/linus/9c936844010466535bd46ea4ce4656ef17653644 (opens in a new tab)
- git.kernel.org/stable/c/40fb64257dab507d86b5f1f2a62f3669ef0c91a8 (opens in a new tab)
- git.kernel.org/stable/c/20c96d0aaabfe361fc2a11c173968dc67feadbbf (opens in a new tab)
- git.kernel.org/stable/c/fb2d057539eda67ec7cfc369bf587e6518a9b99d (opens in a new tab)
- git.kernel.org/stable/c/0f89fb4042c08fd143bfc28af08bf6c8a0197eea (opens in a new tab)
- git.kernel.org/stable/c/8132510c915815e6b537ab937d94ed66893bc7b8 (opens in a new tab)
- git.kernel.org/stable/c/9c936844010466535bd46ea4ce4656ef17653644 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7194-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7166-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-7276-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7277-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7301-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7303-1 (opens in a new tab)