CVE-2026-53127: Linux kernel · Memory Leak
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% 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 24 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
A fix for this memory leak vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this fix once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory or Linux kernel mailing lists for the current remediation guidance.
Description
A memory leak vulnerability was identified and resolved in the Linux kernel related to the block subsystem. Specifically, when blk_revalidate_disk_zones() fails after disk_revalidate_zone_resources() allocates memory for args.zones_cond, the allocated memory is not freed on error paths, causing a leak. This issue does not impact confidentiality or integrity but affects availability due to resource exhaustion. No known exploits are reported in the wild. The vulnerability is classified as CWE-401 (Improper Release of Memory).