CVE-2024-46852

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

HIGH
7.8
CVSS Score
Published: September 27, 2024 at 12:42 PM UTC
Updated: August 5, 2026 at 12:04 PM UTC
2 products affected across 2 vendorsLinux KernelDebian Linux

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.1685.11 ≤ v < 6.1.1115.11 ≤ v < 6.10.115.11 ≤ v < 6.115.11 ≤ v < 6.6.525.16 ≤ v < 6.1.1116.2 ≤ v < 6.6.526.7 ≤ v < 6.10.116.11 rc16.11 rc26.11 rc36.11 rc46.11 rc56.11 rc66.11 rc7a5d2d29e24be8967ef78a1b1fb2292413e3b3df9
Vendor states this is fixed in 79cce5e81d20fa9ad553be439d665ac3302d3c95 (fixed)
Vendor states this is fixed in 84175dc5b2c932266a50c04e5ce342c30f817a2f (fixed)
Vendor states this is fixed in e79050882b857c37634baedbdcf7c2047c24cbff (fixed)
Vendor states this is fixed in ea5ff5d351b520524019f7ff7f9ce418de2dad87 (fixed)
Vendor states this is fixed in eb7fc8b65cea22f9038c52398c8b22849e9620ea (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.168 (unaffected)
Vendor states this is fixed in 6.1.111 (unaffected)
Vendor states this is fixed in 6.10.11 (unaffected)
Vendor states this is fixed in 6.11 (unaffected)
Vendor states this is fixed in 6.6.52 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/79cce5e81d20fa9ad553be439d665ac3302d3c95
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/84175dc5b2c932266a50c04e5ce342c30f817a2f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e79050882b857c37634baedbdcf7c2047c24cbff
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ea5ff5d351b520524019f7ff7f9ce418de2dad87
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/eb7fc8b65cea22f9038c52398c8b22849e9620ea
Mailing ListThird Party Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-193

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card