CVE-2026-23390

Perf tracing disruption via oversized DMA arrays

Published Mar 25, 2026 · Updated Mar 25, 2026

Buffer overflow in Linux Kernel 6.12 through 6.18.12 allows local users to disrupt perf tracing via large scatter-gather lists. The dma_map_sg tracepoint sizes its phys_addrs, dma_addrs, and lengths arrays from nents, so lists above 1,000 entries produce an event around 20 KB that exceeds the 8,192-byte perf trace limit. Low-privileged local access and active perf tracing are required; the observed consequence is a kernel warning that the perf buffer is too small, not a demonstrated kernel crash.

CVSS severity7.8
High
EPSS probability0.13%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Buffer overflow in Linux Kernel 6.12 through 6.18.12 allows local users to disrupt perf tracing via large scatter-gather lists. The dma_map_sg tracepoint sizes its phys_addrs, dma_addrs, and lengths arrays from nents, so lists above 1,000 entries produce an event around 20 KB that exceeds the 8,192-byte perf trace limit. Low-privileged local access and active perf tracing are required; the observed consequence is a kernel warning that the perf buffer is too small, not a demonstrated kernel crash.

The record

CVE
CVE-2026-23390
Published
Mar 25, 2026
Updated
Mar 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-787, T1499
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=038eb433dc1474c4bc7d33188294e3d4778efdfd <02d209bb018a40dee9eac89e91860253dee9605b
  2. Affected versionversion=038eb433dc1474c4bc7d33188294e3d4778efdfd <daafcc0ef0b358d9d622b6e3b7c43767aa3814ee
  3. Affected versionversion=038eb433dc1474c4bc7d33188294e3d4778efdfd <f2584f791a10343bdc995ff6ff402db45b95de69
  4. Affected versionversion=6.12

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=038eb433dc1474c4bc7d33188294e3d4778efdfd <02d209bb018a40dee9eac89e91860253dee9605b; version=038eb433dc1474c4bc7d33188294e3d4778efdfd <daafcc0ef0b358d9d622b6e3b7c43767aa3814ee; version=038eb433dc1474c4bc7d33188294e3d4778efdfd <f2584f791a10343bdc995ff6ff402db45b95de69; version=6.12

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-787Out-of-bounds Write
T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo