Review reviewHigh

CVE-2023-54317

Linux

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 t...

CVSS
7.8
EPSS
0.13%
3.33% percentile
CISA KEV
Not listed
Published
2025.12.30
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.13%
Technical severityCVSS 7.8

Vulnerability overview

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 t...

Affected product and versions

Product
Linux
Affected versions
>= c6cd92fcabd6cc78bb1808c6a18245c842722fc1 < b7f8892f672222dbfcc721f51edc03963212b249, >= d4c637af2e56ee1ec66ee34d0ac5a13c75911aec < 98e311be44dbe31ad9c42aa067b2359bac451fda, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < 3c4a56ef7c538d16c1738ba0ccea9e7146105b5a, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < f2b478228bfdd11e358c5bc197561331f5d5c394, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < ff60b2bb680ebcaf8890814dd51084a022891469, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < be360c83f2d810493c04f999d69ec9152981e0c0, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < 63d31617883d64b43b0e2d529f0751f40713ecae, >= a00f5276e26636cbf72f24f79831026d2e2868e7 < f50714b57aecb6b3dc81d578e295f86d9c73f078, >= 1ed7c9f45fb893877ffa7cedd7aa61beaadbb328, >= 4.14.158 < 4.14.308, >= 4.19.88 < 4.19.276, >= 4.9.206 < 4.10, >= 5.0
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available
CVE-2023-54317 — Linux | SECUFOCUS NOW