LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46852: dma-buf: heaps: Fix off-by-one in CMA heap fault handler

In the Linux kernel, the following vulnerability has been resolved: dma-buf: heaps: Fix off-by-one in CMA heap fault handler Until VM_DONTEXPAND was added in commit 1c1914d6e8c6 ("dma-buf: heaps: Don't track CMA dma-buf pages under RssFile") it was possible to obtain a mapping larger than the buffer size via mremap and bypass the overflow check in dma_buf_mmap_internal. When using such a mapping to attempt to fault past the end of the buffer, the CMA heap fault handler also checks the fault offset against the buffer size, but gets the boundary wrong by 1. Fix the boundary check so that we don't read off the end of the pages array and insert an arbitrary page in the mapping.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-46852 is a Linux kernel memory-handling flaw in the CMA dma-buf heap path. A boundary check was one entry too permissive, allowing the kernel to use the wrong page when a mapping exceeds the buffer. The supplied sources do not provide a severity score or confirmed business impact.

Executive priority

Treat this as a kernel patch-management item with incomplete public severity data. Prioritize systems with untrusted local users, container workloads, Android-like device stacks, or graphics/media memory-sharing paths. Do not treat it as confirmed exploited based on this bundle.

Technical view

The flaw is an off-by-one error in the CMA heap fault handler. Earlier mapping behavior could allow a mapping larger than the dma-buf size; a later fault past the buffer end could read beyond the pages array and map an arbitrary page. Kernel stable commits fix the boundary check.

Likely exposure

Exposure is limited to Linux kernels containing the affected CMA dma-buf heap code before the referenced stable fixes. Systems using vendor kernels should be assessed by kernel package version and vendor advisory, not by upstream version alone.

Exploitation context

The bundle does not show CISA KEV listing or any cited report of active exploitation. The vulnerability appears local and kernel-adjacent, but the supplied sources do not confirm exploitability, required privileges, or final impact.

Researcher notes

The key issue is the incorrect fault offset boundary check after oversized mappings became possible. The public record identifies the fix but does not provide CVSS, CWE, exploit status, or proof-of-concept detail. Validation should focus on fix presence, not exploit reproduction.

Mitigation direction

  • Update Linux kernels to vendor releases containing the referenced upstream stable fixes.
  • Check Debian LTS guidance if running affected Debian kernel packages.
  • Prioritize internet-facing fleets only if they also expose relevant local workload risk.
  • Monitor distribution advisories for backported fixes and corrected package versions.
  • Avoid assuming fixed status from upstream version numbers on vendor kernels.

Validation and detection

  • Inventory Linux kernel versions and distribution package revisions across affected hosts.
  • Confirm whether deployed kernels include the cited stable fix commits or vendor backports.
  • Review whether systems use CMA dma-buf heap functionality or related device workloads.
  • Check vulnerability scanner results against vendor advisories for package-level accuracy.
  • Document exceptions where appliance or embedded kernels cannot be upgraded promptly.
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-46852 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
7Source links

SSVC decision data

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

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
LinuxLinuxa5d2d29e24be8967ef78a1b1fb2292413e3b3df9, a5d2d29e24be8967ef78a1b1fb2292413e3b3df9, a5d2d29e24be8967ef78a1b1fb2292413e3b3df9, a5d2d29e24be8967ef78a1b1fb2292413e3b3df9, a5d2d29e24be8967ef78a1b1fb2292413e3b3df9unaffected
LinuxLinux5.11, 0, 5.15.168, 6.1.111, 6.6.52, 6.10.11, 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.