Linux KernelOperating system · Linux
CVE-2026-53127
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: block: fix zones_cond memory leak on zone revalidation error paths When blk_revalidate_disk_zones() fails after disk_revalidate_zone_resources() has allocated args.zones_cond, the memory is leaked because no error path frees it.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory leak exists in the Linux kernel's blk_revalidate_disk_zones() function. When disk_reallocate_zone_resources() allocates args.zones_cond memory and subsequent zone revalidation fails, the allocated memory is never freed because no error path handles its deallocation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Linux KernelOperating system
>= 6.19, < 7.0.10CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed kernel versionRun 'uname -r' or check /proc/version to get the running kernel versionAffected if The version is >= 6.19 and < 7.0.10
-
Verify zoned block device support is enabledCheck kernel config for CONFIG_BLK_DEV_ZONED or run 'grep -i zoned /proc/config.gz' if available, or check /sys/class/block/*/queue/zoned 2>/dev/null for any zoned devicesAffected if Zoned block device support is compiled in and the system uses zoned block devices
-
Check if blk_revalidate_disk_zones function exists in kernelCheck /proc/kallsyms for 'blk_revalidate_disk_zones' or examine kernel symbol exportsAffected if The function is present in the running kernel (vulnerable code path exists)
-
Verify if the fix is present in the kernel sourceIf kernel source is available, check blk_revalidate_disk_zones() for proper cleanup of args.zones_cond on error paths; look for kfree(args.zones_cond) before error returnsAffected if The fix is NOT present - args.zones_cond is not freed on error paths in blk_revalidate_disk_zones()
The system is affected if the running kernel version is between 6.19 and 7.0.10, zoned block device support is enabled, and the memory leak fix has not been applied to blk_revalidate_disk_zones().
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.0.10
Apply the kernel patch that adds proper error path cleanup to free args.zones_cond memory when blk_revalidate_disk_zones() fails after allocation.
Linux Kernel 7.0.10 or later
- Upgrade the Linux kernel to version 7.0.10 or later to obtain the fix for the memory leak in blk_revalidate_disk_zones()
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-53127 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data