LiveActive security incident?Get immediate response
CVE Record

CVE-2024-36891: maple_tree: fix mas_empty_area_rev() null pointer dereference

In the Linux kernel, the following vulnerability has been resolved: maple_tree: fix mas_empty_area_rev() null pointer dereference Currently the code calls mas_start() followed by mas_data_end() if the maple state is MA_START, but mas_start() may return with the maple state node == NULL. This will lead to a null pointer dereference when checking information in the NULL node, which is done in mas_data_end(). Avoid setting the offset if there is no node by waiting until after the maple state is checked for an empty or single entry state. A user could trigger the events to cause a kernel oops by unmapping all vmas to produce an empty maple tree, then mapping a vma that would cause the scenario described above.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can let a local user crash the system by triggering a null pointer dereference in maple tree memory-management code. The documented impact is a kernel oops, so the business concern is availability, especially on multi-user or shared compute systems.

Executive priority

Treat as a normal-priority kernel availability fix, elevated for shared or untrusted-user environments. Patch through standard kernel maintenance unless local denial-of-service risk affects critical operations.

Technical view

CVE-2024-36891 is a null pointer dereference in mas_empty_area_rev(). mas_start() can leave the maple state node as NULL, after which mas_data_end() dereferences it. The described trigger involves emptying the VMA maple tree and mapping a VMA that reaches this state.

Likely exposure

Exposure is Linux systems running affected kernel code, especially hosts where untrusted local users, containers, or workloads can perform memory mapping activity. The supplied version data is incomplete for precise range confirmation, so validate against distribution advisories and kernel stable fixes.

Exploitation context

The source says a user could trigger a kernel oops. KEV is false, and the provided sources do not claim active exploitation, remote exploitation, privilege escalation, or code execution.

Researcher notes

Evidence supports local kernel crash potential through VMA maple tree state handling. The bundle does not provide CVSS, CWE, exploit-in-the-wild evidence, or definitive per-distribution fixed package versions.

Mitigation direction

  • Apply vendor or distribution kernel updates containing the referenced maple_tree fix.
  • Reboot systems after kernel updates to ensure the fixed kernel is active.
  • Prioritize shared hosts, developer machines, container platforms, and multi-user Linux servers.
  • Check Linux distribution advisories before assuming exact affected or fixed versions.
  • Limit untrusted local shell access where immediate patching is delayed.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and container hosts.
  • Compare running kernels with vendor advisories and referenced stable kernel commits.
  • Confirm patched systems have rebooted into the updated kernel.
  • Review crash logs for kernel oops events involving maple_tree or mas_empty_area_rev().
  • Track KEV and vendor advisories for any change in exploitation status.
Prepared
Confidence
medium
Sources
6

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-36891 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
5Source 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux54a611b605901c7d5d05b6b8f5d04a6ceb0962aa, 54a611b605901c7d5d05b6b8f5d04a6ceb0962aa, 54a611b605901c7d5d05b6b8f5d04a6ceb0962aa, 54a611b605901c7d5d05b6b8f5d04a6ceb0962aaunaffected
LinuxLinux6.1, 0, 6.1.94, 6.6.31, 6.8.10, 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.