CVE-2026-23390

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow

Published Mar 25, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow

The dma_map_sg tracepoint can trigger a perf buffer overflow when
tracing large scatter-gather lists. With devices like virtio-gpu
creating large DRM buffers, nents can exceed 1000 entries, resulting
in:

phys_addrs: 1000 * 8 bytes = 8,000 bytes
dma_addrs: 1000 * 8 bytes = 8,000 bytes
lengths: 1000 * 4 bytes = 4,000 bytes
Total: ~20,000 bytes

This exceeds PERF_MAX_TRACE_SIZE (8192 bytes), causing:

WARNING: CPU: 0 PID: 5497 at kernel/trace/trace_event_perf.c:405
perf buffer not large enough, wanted 24620, have 8192

Cap all three dynamic arrays at 128 entries using min() in the array
size calculation. This ensures arrays are only as large as needed
(up to the cap), avoiding unnecessary memory allocation for small
operations while preventing overflow for large ones.

The tracepoint now records the full nents/ents counts and a truncated
flag so users can see when data has been capped.

Changes in v2:
- Use min(nents, DMA_TRACE_MAX_ENTRIES) for dynamic array sizing
instead of fixed DMA_TRACE_MAX_ENTRIES allocation (feedback from
Steven Rostedt)
- This allocates only what's needed up to the cap, avoiding waste
for small operations

Reviwed-by: Sean Anderson <sean.anderson@linux.dev>

Analysis

AI-generated

Technical impact

The kernel’s dma_map_sg tracepoint can allocate dynamic arrays large enough to overflow the perf buffer. When devices such as virtio-gpu create scatter‑gather lists with more than a thousand entries, the tracepoint attempts to record over 20 KB of data, exceeding the 8 KB limit enforced by PERF_MAX_TRACE_SIZE. This results in a buffer overflow logged as a perf buffer warning and can corrupt kernel memory, potentially leading to a system crash or denial of service. This issue is classified as a buffer overflow (CWE-131).

Affected Systems

The vulnerability is present in the Linux kernel across all supported distributions that embed the affected code path. No specific kernel releases are listed in the advisory, so any kernel version that contains the unpatched dma_map_sg tracepoint is susceptible. The focus is on the generic implementation rather than a particular vendor.

Risk and Exploitability

Exploitability is considered low to moderate. The CVSS score of 7.8 indicates a high severity vulnerability. The EPSS score is below 1 % and the vulnerability is not listed in the CISA KEV catalog, indicating limited public exploitation. Attacks would require access to a user that can trigger large scatter‑gather operations or a privileged context that enables kernel tracing. Because the flaw only manifests when the dma_map_sg tracepoint is active, a local attacker would need to enable tracing and provoke a high‑entry list, making the risk lower than a remote RCE.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Linux kernel to a version that includes the dma_map_sg tracepoint patch which caps the array sizes at 128 entries.
  • Reboot the system to load the updated kernel and ensure tracing uses the patched implementation.
  • Disable the dma_map_sg tracepoint (e.g., by clearing the trace_events variable or using trace‑cmd to turn off the tracepoint) until the patch is fully rolled out.

Generated by OpenCVE AI on April 28, 2026 at 21:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-787
CPEs cpe:2.3:o:linux:linux_kernel:6.12:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-119
Type Values Removed Values Added
Weaknesses CWE-119
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow The dma_map_sg tracepoint can trigger a perf buffer overflow when tracing large scatter-gather lists. With devices like virtio-gpu creating large DRM buffers, nents can exceed 1000 entries, resulting in: phys_addrs: 1000 * 8 bytes = 8,000 bytes dma_addrs: 1000 * 8 bytes = 8,000 bytes lengths: 1000 * 4 bytes = 4,000 bytes Total: ~20,000 bytes This exceeds PERF_MAX_TRACE_SIZE (8192 bytes), causing: WARNING: CPU: 0 PID: 5497 at kernel/trace/trace_event_perf.c:405 perf buffer not large enough, wanted 24620, have 8192 Cap all three dynamic arrays at 128 entries using min() in the array size calculation. This ensures arrays are only as large as needed (up to the cap), avoiding unnecessary memory allocation for small operations while preventing overflow for large ones. The tracepoint now records the full nents/ents counts and a truncated flag so users can see when data has been capped. Changes in v2: - Use min(nents, DMA_TRACE_MAX_ENTRIES) for dynamic array sizing instead of fixed DMA_TRACE_MAX_ENTRIES allocation (feedback from Steven Rostedt) - This allocates only what's needed up to the cap, avoiding waste for small operations Reviwed-by: Sean Anderson <sean.anderson@linux.dev>
Title tracing/dma: Cap dma_map_sg tracepoint arrays to prevent buffer overflow
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-131

    Incorrect Calculation of Buffer Size

  • CWE-787

    Out-of-bounds Write

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
May 11, 2026, 10:05 PM
Reserved
Jan 13, 2026, 3:37 PM
Status
Analyzed
Published
Mar 25, 2026, 11:16 AM
Modified
Jun 17, 2026, 10:21 AM
Severity
Public date
Mar 25, 2026, 12:00 AM