LiveActive security incident?Get immediate response
CVE Record

CVE-2024-35993: mm: turn folio_test_hugetlb into a PageType

In the Linux kernel, the following vulnerability has been resolved: mm: turn folio_test_hugetlb into a PageType The current folio_test_hugetlb() can be fooled by a concurrent folio split into returning true for a folio which has never belonged to hugetlbfs. This can't happen if the caller holds a refcount on it, but we have a few places (memory-failure, compaction, procfs) which do not and should not take a speculative reference. Since hugetlb pages do not use individual page mapcounts (they are always fully mapped and use the entire_mapcount field to record the number of mappings), the PageType field is available now that page_mapcount() ignores the value in this field. In compaction and with CONFIG_DEBUG_VM enabled, the current implementation can result in an oops, as reported by Luis. This happens since 9c5ccf2db04b ("mm: remove HUGETLB_PAGE_DTOR") effectively added some VM_BUG_ON() checks in the PageHuge() testing path. [willy@infradead.org: update vmcoreinfo]

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel race can misidentify an ordinary memory page as a huge-page object while it is being split. This can trigger a kernel oops and disrupt the system. The 7.8 CVSS score models severe potential impact, but the supplied evidence does not demonstrate practical privilege escalation or data compromise.

Executive priority

Treat this as a high-priority kernel maintenance issue, especially on multi-user systems and debug-enabled infrastructure. Use normal expedited patching rather than emergency incident measures unless crashes or related indicators appear. Current sources do not support claims of active exploitation.

Technical view

A concurrent folio split can cause folio_test_hugetlb() to return true for a folio that never belonged to hugetlbfs. Refcount-less callers in memory-failure, compaction, and procfs are exposed. Compaction with CONFIG_DEBUG_VM can reach VM_BUG_ON checks and produce an oops. The stable changes represent hugetlb status using PageType.

Likely exposure

Exposure applies to affected Linux kernel builds identified in the CVE data, including listed 6.6, 6.6.30, 6.8.9, and 6.9 releases. Hosts exercising memory compaction, memory-failure, or procfs paths merit attention. CONFIG_DEBUG_VM increases the documented crash exposure, but disabling it is not established as a complete mitigation.

Exploitation context

The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation, public weaponization, or a reliable privilege-escalation path. The documented reproduced effect is a kernel oops.

Researcher notes

The key race concerns classification during folio splitting when callers intentionally lack speculative references. The supplied version list is not a complete distribution-package matrix, and defaultStatus is represented inconsistently alongside affected entries. Validate exposure through distribution advisories and commit backports. Avoid inferring confidentiality or integrity exploitation solely from the CVSS impact ratings.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable Linux stable fix, then reboot.
  • Use distribution advisories to map the fix to backported package versions.
  • Prioritize systems permitting untrusted local access or running CONFIG_DEBUG_VM.
  • If upgrading is delayed, consult the distribution vendor; no complete workaround is documented here.

Validation and detection

  • Record each host's running kernel release and distribution package version.
  • Confirm the vendor changelog explicitly references CVE-2024-35993 or an associated stable commit.
  • After rebooting, verify the fixed kernel is actually running.
  • Review kernel logs for compaction-related oopses or PageHuge and VM_BUG_ON failures.
  • Check CONFIG_DEBUG_VM status for prioritization, but do not treat its absence as proof of safety.
Prepared
Confidence
medium
Sources
5

Public sources used

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-35993 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-35993Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9c5ccf2db04b8d7c3df363fdd4856c2b79ab2c6a, 9c5ccf2db04b8d7c3df363fdd4856c2b79ab2c6a, 9c5ccf2db04b8d7c3df363fdd4856c2b79ab2c6aunaffected
LinuxLinux6.6, 0, 6.6.30, 6.8.9, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.