LiveActive security incident?Get immediate response
CVE Record

CVE-2024-52319: mm: use aligned address in clear_gigantic_page()

In the Linux kernel, the following vulnerability has been resolved: mm: use aligned address in clear_gigantic_page() In current kernel, hugetlb_no_page() calls folio_zero_user() with the fault address. Where the fault address may be not aligned with the huge page size. Then, folio_zero_user() may call clear_gigantic_page() with the address, while clear_gigantic_page() requires the address to be huge page size aligned. So, this may cause memory corruption or information leak, addtional, use more obvious naming 'addr_hint' instead of 'addr' for clear_gigantic_page().

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 flaw in huge-page memory clearing can use a misaligned address, potentially corrupting memory or exposing information. A low-privileged local user may be able to affect confidentiality, integrity, and availability. The supplied sources do not establish remote reachability or active exploitation.

Executive priority

Prioritize accelerated kernel maintenance, especially on shared, multi-user, or untrusted-workload hosts. The possible impact is severe, but current evidence supports planned urgent remediation rather than exploitation-driven incident response. Validate vendor-specific exposure before broad emergency action.

Technical view

The hugetlb_no_page() path can pass an unaligned fault address through folio_zero_user() to clear_gigantic_page(), which expects huge-page alignment. This mismatch may cause memory corruption or information disclosure. The CVSS 3.1 assessment is 7.8, requiring local access and low privileges, without user interaction.

Likely exposure

Potentially exposed systems run affected Linux kernels and can reach the gigantic hugetlb page fault and zeroing path. The bundle lists 6.11, 6.12.7, and 6.13, but its version data contains ambiguity, including an unexplained “0”; confirm precise applicability with the kernel or distribution vendor.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source reports active exploitation or a public exploit. The CVSS vector indicates a local, low-privilege attack surface. Treat exploitation status as unconfirmed rather than absent.

Researcher notes

The core defect and correction are documented by two upstream stable commits. Exact affected-version boundaries are not reliably expressed in the supplied structured data: one commit is duplicated and “0” appears among affected versions. No CWE, exploit evidence, or vendor-specific package mapping is provided.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable cited stable fix.
  • Confirm distribution-specific fixed versions before deployment; upstream version data is ambiguous.
  • Restrict untrusted local access while patching is pending.
  • Consult vendor guidance for supported workarounds; none is identified in the bundle.

Validation and detection

  • Inventory running kernels and identify systems using affected Linux releases.
  • Compare vendor changelogs against the two cited upstream stable commits.
  • Verify upgraded systems booted into the corrected kernel.
  • Prioritize hosts permitting untrusted or shared low-privilege local access.
Prepared
Confidence
medium
Sources
4

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-52319 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
0ADP providers
3Source links

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-52319Attack 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux78fefd04c123493bbf28434768fa577b2153c79b, 78fefd04c123493bbf28434768fa577b2153c79bunaffected
LinuxLinux6.11, 0, 6.12.7, 6.13affected
Weakness

CWE details

No CWE listed

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