CVE-2023-54317

dm flakey: don't corrupt the zero page

HIGH
7.8
CVSS Score
Published: December 30, 2025 at 12:23 PM UTC
Updated: October 15, 2026 at 10:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: dm flakey: don't corrupt the zero page When we need to zero some range on a block device, the function __blkdev_issue_zero_pages submits a write bio with the bio vector pointing to the zero page. If we use dm-flakey with corrupt bio writes option, it will corrupt the content of the zero page which results in crashes of various userspace programs. Glibc assumes that memory returned by mmap is zeroed and it uses it for calloc implementation; if the newly mapped memory is not zeroed, calloc will return non-zeroed memory. Fix this bug by testing if the page is equal to ZERO_PAGE(0) and avoiding the corruption in this case.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1ed7c9f45fb893877ffa7cedd7aa61beaadbb3284.14.1584.19.884.9.2065.0a00f5276e26636cbf72f24f79831026d2e2868e7c6cd92fcabd6cc78bb1808c6a18245c842722fc1d4c637af2e56ee1ec66ee34d0ac5a13c75911aec
Vendor states this is fixed in 3c4a56ef7c538d16c1738ba0ccea9e7146105b5a (fixed)
Vendor states this is fixed in 63d31617883d64b43b0e2d529f0751f40713ecae (fixed)
Vendor states this is fixed in 98e311be44dbe31ad9c42aa067b2359bac451fda (fixed)
Vendor states this is fixed in b7f8892f672222dbfcc721f51edc03963212b249 (fixed)
Vendor states this is fixed in be360c83f2d810493c04f999d69ec9152981e0c0 (fixed)
Vendor states this is fixed in f2b478228bfdd11e358c5bc197561331f5d5c394 (fixed)
Vendor states this is fixed in f50714b57aecb6b3dc81d578e295f86d9c73f078 (fixed)
Vendor states this is fixed in ff60b2bb680ebcaf8890814dd51084a022891469 (fixed)
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.14.308 (unaffected)
Vendor states this is fixed in 4.19.276 (unaffected)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.99 (unaffected)
Vendor states this is fixed in 5.4.235 (unaffected)
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card