CVE-2026-53140: Linux kernel · Memory Leak
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jun 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.
What to do
AI-suggested
Until then, limiting local access to trusted users may reduce risk.
Description
In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Fix vaddr leak when indirect CSD has zeroed workgroups v3d_rewrite_csd_job_wg_counts_from_indirect() maps both the indirect buffer and the workgroup buffer and is expected to release them before returning. When any of the workgroup counts read from the buffer is zero, the function bailed out early and skipped the cleanup, leaking the vaddr mappings of both BOs. Jump to the cleanup path instead of returning directly, so the mappings are always dropped.
References
- nvd.nist.gov/vuln/detail/CVE-2026-53140 (opens in a new tab)
- git.kernel.org/stable/c/0b59d0946913a0df7d1a033013e259e9b6a76546 (opens in a new tab)
- git.kernel.org/stable/c/60ebeb23eaf3d7fd2e0551fe304309305e31d424 (opens in a new tab)
- git.kernel.org/stable/c/90b629269088a9fe24a02c032be9f08357f47873 (opens in a new tab)
- git.kernel.org/stable/c/ae7676952790f421c40918e2586a2c9f12a682b6 (opens in a new tab)