LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54317: dm flakey: don't corrupt the zero page

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-54317 is a Linux kernel bug in dm-flakey, a device-mapper fault-injection target. Under a specific corrupt-write option, it can corrupt the kernel zero page during block zeroing. That can break the assumption that newly mapped memory is zeroed, causing user-space instability and incorrect calloc behavior.

Executive priority

Treat as a targeted kernel reliability and integrity issue, not a broad internet-facing emergency based on available evidence. Patch during the next kernel maintenance cycle, sooner for storage testing, virtualization, or environments using dm-flakey.

Technical view

When __blkdev_issue_zero_pages submits a write bio backed by ZERO_PAGE(0), dm-flakey with corrupt bio writes can modify that shared zero page. The upstream fix avoids corruption when the page equals ZERO_PAGE(0). The source names affected Linux kernel lines and stable commits, but provides no CVSS, CWE, or detailed attack vector.

Likely exposure

Exposure appears limited to affected Linux kernels where dm-flakey is used with the corrupt bio writes option. This is often associated with testing or fault-injection setups, but the provided sources do not define deployment prevalence or required privileges.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. It does not provide public exploit details, remote attack claims, or privilege requirements. The practical risk is kernel-level memory corruption causing user-space crashes or incorrect zero-initialization assumptions.

Researcher notes

Key evidence is the upstream kernel resolution text: corrupting ZERO_PAGE(0) can propagate non-zero memory assumptions into mmap and calloc behavior. Missing evidence includes CVSS, CWE, exploitability analysis, required privileges, and distro-specific fixed package versions.

Mitigation direction

  • Update to a vendor kernel containing the listed stable fixes.
  • If immediate patching is not possible, review vendor guidance for supported mitigations.
  • Avoid using dm-flakey corrupt bio writes on affected kernels where operationally feasible.
  • Prioritize hosts that use device-mapper fault-injection or storage test configurations.

Validation and detection

  • Inventory Linux kernel versions against the affected version list.
  • Check whether dm-flakey is configured with corrupt bio writes.
  • Confirm installed kernels include the relevant upstream stable fix commit.
  • Review crash reports for unexplained user-space failures after block zeroing activity.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54317 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc6cd92fcabd6cc78bb1808c6a18245c842722fc1, d4c637af2e56ee1ec66ee34d0ac5a13c75911aec, a00f5276e26636cbf72f24f79831026d2e2868e7, a00f5276e26636cbf72f24f79831026d2e2868e7, a00f5276e26636cbf72f24f79831026d2e2868e7, a00f5276e26636cbf72f24f79831026d2e2868e7, a00f5276e26636cbf72f24f79831026d2e2868e7, a00f5276e26636cbf72f24f79831026d2e2868e7, 1ed7c9f45fb893877ffa7cedd7aa61beaadbb328, 4.14.158, 4.19.88, 4.9.206unaffected
LinuxLinux5.0, 0, 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.