LiveActive security incident?Get immediate response
CVE Record

CVE-2024-26621: mm: huge_memory: don't force huge page alignment on 32 bit

In the Linux kernel, the following vulnerability has been resolved: mm: huge_memory: don't force huge page alignment on 32 bit commit efa7df3e3bb5 ("mm: align larger anonymous mappings on THP boundaries") caused two issues [1] [2] reported on 32 bit system or compat userspace. It doesn't make too much sense to force huge page alignment on 32 bit system due to the constrained virtual address space. [1] https://lore.kernel.org/linux-mm/d0a136a0-4a31-46bc-adf4-2db109a61672@kernel.org/ [2] https://lore.kernel.org/linux-mm/CAJuCfpHXLdQy1a2B6xN2d7quTYwg2OoZseYPZTRpU0eHHKD-sQ@mail.gmail.com/

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

Security readout for executives and security teams

Plain-English summary

A Linux memory-management change forced large anonymous mappings onto huge-page boundaries. On 32-bit systems, and for 32-bit compatibility applications, limited address space made that behavior unsafe. The supplied record rates the issue high severity, but does not document a complete attack chain.

Executive priority

Treat this as a targeted high-priority kernel update, especially where 32-bit or compatibility workloads process untrusted input. There is no source-backed evidence of active exploitation, so prioritize rapid exposure confirmation and normal high-severity patching rather than declaring an emergency solely from the score.

Technical view

Commit efa7df3e3bb5 introduced forced Transparent Huge Page alignment for larger anonymous mappings. The fix avoids that alignment on 32-bit systems. The supplied CVSS 8.2 vector asserts high confidentiality and low availability impact, although the narrative primarily documents mapping problems and does not explain the confidentiality mechanism.

Likely exposure

Exposure is concentrated in affected Linux kernels running natively on 32-bit architectures or executing 32-bit compatibility workloads. The normalized version list is ambiguous and includes isolated version identifiers without range relationships, so organizations should confirm affected and fixed builds through their Linux distributor.

Exploitation context

CISA KEV status is false, and the bundle provides no evidence of active exploitation or public weaponization. Although the CVSS vector specifies network access without privileges or user interaction, the supplied technical description does not establish a remote interface or end-to-end attack path.

Researcher notes

The fix removes forced huge-page alignment on 32-bit paths. Researchers should map each stable commit to the relevant maintained branch because the supplied affected-version normalization lacks clear range semantics. The CVSS network and confidentiality characteristics should be reconciled with distributor analysis before asserting remote exploitability or data disclosure.

Mitigation direction

  • Inventory 32-bit Linux systems and hosts permitting 32-bit compatibility applications.
  • Match each installed kernel against distributor advisories and the referenced stable fix commits.
  • Upgrade to a vendor-supported kernel containing the applicable fix.
  • If updating is delayed, consult vendor guidance; the sources provide no verified workaround.

Validation and detection

  • Confirm each system's running kernel version, architecture, and 32-bit compatibility status.
  • Verify the applicable stable fix appears in the vendor kernel changelog or source package.
  • Test representative 32-bit workloads after updating for memory-mapping regressions.
  • Re-scan assets and document systems whose affected status remains unresolved.
Prepared
Confidence
medium
Sources
8

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-26621 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
8.2 (3.1)
Known Exploited
No
Published

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

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
6Source 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
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L3.94.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1854bc6e2420472676c5c90d3d6b15f6cd640e40, 1854bc6e2420472676c5c90d3d6b15f6cd640e40, 1854bc6e2420472676c5c90d3d6b15f6cd640e40, 1854bc6e2420472676c5c90d3d6b15f6cd640e40unaffected
LinuxLinux5.18, 0, 6.1.81, 6.6.46, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

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