Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-49856: x86/sgx: Fix deadlock in SGX NUMA node search

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0f89fb4042c08fd143bfc28af08bf6c8a0197eea, 20c96d0aaabfe361fc2a11c173968dc67feadbbf, 40fb64257dab507d86b5f1f2a62f3669ef0c91a8; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 0f89fb4042c08fd143bfc28af08bf6c8a0197eea, 20c96d0aaabfe361fc2a11c173968dc67feadbbf, 40fb64257dab507d86b5f1f2a62f3669ef0c91a8; azl3 kernel 6.6.51.1-5 on Azure Linux 3.0 6.6.56.1-5; azl3 kernel 6.6.56.1-5 on Azure Linux 3.0 6.6.56.1-5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-49856

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.13 and later · before 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.54
  • linux linux kernel6.7 and later · before 6.10.13
  • linux linux kernel6.11 and later · before 6.11.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before 40fb64257dab507d86b5f1f2a62f3669ef0c91a8affected · git
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before 20c96d0aaabfe361fc2a11c173968dc67feadbbfaffected · git
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before fb2d057539eda67ec7cfc369bf587e6518a9b99daffected · git
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before 0f89fb4042c08fd143bfc28af08bf6c8a0197eeaaffected · git
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before 8132510c915815e6b537ab937d94ed66893bc7b8affected · git
    • 901ddbb9ecf5425183ea0c09d10c2fd7868dce54 and later · before 9c936844010466535bd46ea4ce4656ef17653644affected · git
    • before 5.13not affected · semver
    • 5.15.168 and later · up to and including 5.15.*not affected · semver
    • 6.1.113 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.2-16.11.2-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-49854Oct 21, 2024 · block, bfq: fix uaf for accessing waker_bfqq after splitting
    31Monitor
  • ← EarlierCVE-2024-49855Oct 21, 2024 · nbd: fix race between timeout and normal completion
    28Monitor
  • Later →CVE-2024-49857Oct 21, 2024 · wifi: iwlwifi: mvm: set the cipher for secured NDP ranging
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0f89fb4042c08fd143bfc28af08bf6c8a0197eeaVendor (CNA)
Linux Linux20c96d0aaabfe361fc2a11c173968dc67feadbbfVendor (CNA)
Linux Linux40fb64257dab507d86b5f1f2a62f3669ef0c91a8Vendor (CNA)
Linux Linux8132510c915815e6b537ab937d94ed66893bc7b8Vendor (CNA)
Linux Linux9c936844010466535bd46ea4ce4656ef17653644Vendor (CNA)
Linux Linuxfb2d057539eda67ec7cfc369bf587e6518a9b99dVendor (CNA)
azl3 kernel 6.6.51.1-5 on Azure Linux 3.06.6.56.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.56.1-5 on Azure Linux 3.06.6.56.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-23451529 days apartbonding: prevent potential infinite loop in bond_header_parse()
    30Monitor
  • CVE-2024-27032173 days apartf2fs: fix to avoid potential panic during recovery
    25Monitor
  • CVE-2022-48635176 days apartfsdax: Fix infinite loop in dax_iomap_rw()
    24Monitor
  • CVE-2024-500110 days apartASoC: Intel: soc-acpi-intel-rpl-match: add missing empty item
    22Monitor
  • CVE-2024-5027228 days apartfilemap: Fix bounds checking in filemap_read()
    22Monitor
  • CVE-2024-5305529 days apartwifi: iwlwifi: mvm: fix 6 GHz scan construction
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records