LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42258: mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines

In the Linux kernel, the following vulnerability has been resolved: mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines Yves-Alexis Perez reported commit 4ef9ad19e176 ("mm: huge_memory: don't force huge page alignment on 32 bit") didn't work for x86_32 [1]. It is because x86_32 uses CONFIG_X86_32 instead of CONFIG_32BIT. !CONFIG_64BIT should cover all 32 bit machines. [1] https://lore.kernel.org/linux-mm/CAHbLzkr1LwH3pcTgM+aGQ31ip2bKqiqEQ8=FQB+t2c3dhNKNHA@mail.gmail.com/

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory-management issue around huge page alignment on 32-bit systems. The source says a prior change intended to relax alignment did not work for x86_32. Business urgency is hard to rank because no CVSS, CWE, impact description, or exploitation evidence is provided.

Executive priority

Handle through normal kernel patch governance unless your environment still runs 32-bit Linux, embedded Linux, or unsupported kernels. There is insufficient evidence here to justify emergency response, but kernel issues can be operationally sensitive and should not be ignored.

Technical view

The kernel fix changes the huge_memory alignment logic to use !CONFIG_64BIT so all 32-bit architectures are covered, including x86_32 using CONFIG_X86_32. The bundle lists Linux kernel versions and stable commits, but does not describe attack prerequisites, privilege impact, confidentiality, integrity, or availability consequences.

Likely exposure

Exposure is most plausible on Linux systems running affected kernel builds, especially 32-bit or x86_32 environments using transparent huge page behavior. Modern 64-bit fleets may be less relevant, but confirm against distribution advisories and exact kernel package versions.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, exploit maturity, or weaponized activity. Treat active exploitation as unconfirmed. The available evidence is a kernel bug fix and downstream advisory reference, not an exploitation report.

Researcher notes

The record is sparse: severity is unknown, no CVSS or CWE is supplied, and the impact is not described. Analysis should focus on affected kernel lineage and whether !CONFIG_64BIT behavior is present in the target build, without assuming exploitability from the fix alone.

Mitigation direction

  • Inventory Linux kernel versions across servers, appliances, containers hosts, and embedded systems.
  • Prioritize distribution-supported kernel updates that include the referenced stable fixes.
  • Check Debian LTS guidance if operating affected Debian LTS kernels.
  • For unsupported 32-bit systems, consult vendor guidance or plan retirement.
  • Do not rely on source commit hashes alone; map them to packaged kernel builds.

Validation and detection

  • Compare running kernel package versions with vendor advisories for CVE-2024-42258.
  • Identify any 32-bit or x86_32 Linux systems in production and lab environments.
  • Confirm whether distribution kernel changelogs include the referenced stable commits.
  • Review vulnerability scanner findings for this CVE against actual kernel build metadata.
  • Document systems where vendor status is unavailable or the source evidence is incomplete.
Prepared
Confidence
medium
Sources
7

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-42258 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

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

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
LinuxLinux87632bc9ecff5ded93433bc0fca428019bdd1cfe, 6ea9aa8d97e6563676094cb35755884173269555, 4ef9ad19e17676b9ef071309bc62020e2373705d, 4ef9ad19e17676b9ef071309bc62020e2373705d, 7432376c913381c5f24d373a87ff629bbde94b47, 6.1.81, 6.7.6unaffected
LinuxLinux6.8, 0, 6.1.105, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

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