LiveActive security incident?Get immediate response
CVE Record

CVE-2024-51729: mm: use aligned address in copy_user_gigantic_page()

In the Linux kernel, the following vulnerability has been resolved: mm: use aligned address in copy_user_gigantic_page() In current kernel, hugetlb_wp() calls copy_user_large_folio() with the fault address. Where the fault address may be not aligned with the huge page size. Then, copy_user_large_folio() may call copy_user_gigantic_page() with the address, while copy_user_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 copy_user_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 local, low-privileged user may trigger incorrect memory handling when Linux copies an unusually large huge page. The resulting memory corruption or information disclosure could affect confidentiality, integrity, and availability. Exploitation requires local access and the relevant gigantic-page memory path, limiting exposure compared with a remotely reachable flaw.

Executive priority

Treat as a high-priority local privilege-boundary risk, especially on shared or multi-tenant Linux hosts using gigantic pages. Patch through supported vendor channels after compatibility testing. Internet-facing status alone does not drive exposure because the documented attack vector is local.

Technical view

An unaligned fault address can pass from hugetlb_wp() through copy_user_large_folio() to copy_user_gigantic_page(), which expects huge-page-size alignment. The kernel fix uses an aligned address. The supplied CVSS 3.1 score is 7.8: local access, low complexity, low privileges, no user interaction, and potentially high impact across all three security properties.

Likely exposure

Exposure is most plausible on Linux systems using hugetlb gigantic pages where untrusted or compromised local users can exercise the affected copy-on-write path. The supplied version data references Linux 6.11, 6.12.7, 6.13, and specific commits, but does not clearly express complete affected and fixed ranges. Confirm status with the distribution vendor.

Exploitation context

The supplied record is not in CISA KEV, and no cited source reports active exploitation. That does not prove exploitation is impossible. The CVSS vector indicates a local attacker with low privileges and no required user interaction; successful triggering could cause memory disclosure, corruption, or system instability.

Researcher notes

The vulnerable condition is an address-alignment contract violation in the gigantic-page copy path. The sources describe possible corruption or disclosure but do not establish a demonstrated exploit, reliable trigger, or precise distribution package matrix. Version assessment should use commit ancestry and vendor backport information rather than kernel version strings alone.

Mitigation direction

  • Install a vendor-supported kernel containing the cited upstream or stable fix.
  • Consult distribution advisories to map package versions to the cited commits.
  • Prioritize multi-user, shared-hosting, and other systems allowing untrusted local execution.
  • If patching is delayed, assess whether gigantic-page usage can be safely reduced under vendor guidance.

Validation and detection

  • Inventory running kernel and distribution package versions on potentially exposed systems.
  • Check vendor advisories for backports of the cited alignment fix.
  • Determine whether hugetlb gigantic pages are configured or used by workloads.
  • Identify systems permitting local access by untrusted users or tenants.
  • After updating, verify the running kernel—not merely the installed package—contains the fix.
Prepared
Confidence
high
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-51729 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-51729Attack 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
LinuxLinux530dd9926dc16220d2fae0997f45cda94f5f0864, 530dd9926dc16220d2fae0997f45cda94f5f0864unaffected
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.