Linux KernelOperating system · Linux
CVE-2026-53063
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: dm cache: fix write hang in passthrough mode The invalidate_remove() function has incomplete logic for handling write hit bios after cache invalidation. It sets up the remapping for the overwrite_bio but then drops it immediately without submission, causing write operations to hang. Fix by adding a new invalidate_committed() continuation that submits the remapped writes to the cache origin after metadata commit completes, while using the overwrite_endio hook to ensure proper completion sequencing. This maintains existing coherency. Also improve error handling in invalidate_complete() to preserve the original error status instead of using bio_io_error() unconditionally.
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 confidenceIn the Linux kernel's dm cache (device mapper cache) subsystem, the invalidate_remove() function has incomplete logic that sets up remapping for write hit bios after cache invalidation but drops them without submission, causing write operations to hang in passthrough mode. The fix adds a new invalidate_committed() continuation to properly submit remapped writes after metadata commit and improves error handling to preserve original error status.
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
>= 4.12, < 6.1.175>= 6.2, < 6.6.141>= 6.7, < 6.12.91>= 6.13, < 6.18.33>= 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 if dm-cache module is loadedRun `lsmod | grep dm_cache` or check if /sys/module/dm_cache existsAffected if The dm_cache module is not loaded - the system is not using dm-cache and is not affected
-
Identify active dm-cache devicesRun `dmsetup status` and look for cache devices, or check /sys/block/*/dm/name for cache mappingsAffected if No cache devices exist - the system is not using dm-cache and is not affected
-
Check kernel version against affected rangesRun `uname -r` and compare to: >= 4.12 and < 6.1.175; >= 6.2 and < 6.6.141; >= 6.7 and < 6.12.91; >= 6.13 and < 6.18.33; >= 6.19 and < 7.0.10Affected if Kernel version is outside all affected ranges - the system is likely not affected (patches may have been backported)
-
Verify if cache invalidation is in useCheck dmsetup table for cache devices with invalidation settings: `dmsetup table | grep cache` and inspect cache policy/table entries for invalidation-related optionsAffected if No cache devices use invalidation features - the specific bug trigger condition is not present
A system is affected only if it runs a vulnerable kernel version, has active dm-cache devices, and those cache devices are using cache invalidation features with concurrent write operations.
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 · scoped6.1.1756.6.1416.12.91
Apply the kernel patch which adds invalidate_committed() continuation and fixes error handling in invalidate_complete(). This is a Linux kernel bug fix requiring kernel upgrade or patch application followed by system reboot.
Upgrade to kernel 6.1.175 (for 6.1.x branch), 6.6.141 (for 6.2-6.6.x branch), 6.12.91 (for 6.7-6.12.x branch), or 6.18.33 (for 6.13-6.18.x branch) - preferably the latest stable branch available
- Identify the currently running kernel version using `uname -r`
- Check which version range your current kernel falls into (>= 4.12, < 6.1.175), (>= 6.2, < 6.6.141), (>= 6.7, < 6.12.91), or (>= 6.13, < 6.18.33)
- Obtain a kernel upgrade to a version at or above the fixed release for your branch: 6.1.175, 6.6.141, 6.12.91, or 6.18.33
- Reboot the system to load the patched kernel
- Verify the fix is applied by checking the kernel version and confirming dm cache functionality works without write hangs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Linux Kernel
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,944.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-53063 — 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-53063 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