VulnerabilityPublished 19 Jul 2026

CVE-2026-63929: Linux kernel · iio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf()

Source GCVE Database

Not known to be exploited.

Data as of 26 Oct 2026, 13:47 UTC

Severity

Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-7xv7-rch9-q9hw

What to do

AI-suggested

A fix has been implemented in the Linux kernel to call dma_fence_put() after dma_resv_add_fence(), ensuring proper release of the DMA fence reference and preventing the memory leak. Users should apply the official kernel update containing this fix. Patch status is not explicitly stated in the provided data; check the vendor or kernel mailing list advisories for the exact fixed versions and update accordingly.

Description

A vulnerability in the Linux kernel's Industrial I/O (iio) buffer subsystem caused a memory leak due to a missing release of a DMA fence reference in the iio_buffer_enqueue_dmabuf() function. This leak results from the function not calling dma_fence_put() after dma_resv_add_fence(), causing permanent allocation growth. The issue was fixed by ensuring the DMA fence reference is properly released, preventing the leak.

References

Community reviews

Loading reviews…