CVE-2023-54317
CVE-2023-54317 is a security vulnerability that is still awaiting full analysis and scoring. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- EPSS exploit prediction: 0% (9th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2023-60487
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2023-54317?
- 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.
- Is CVE-2023-54317 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (9th percentile), an estimate of the probability of exploitation in the next 30 days.
- How do I fix CVE-2023-54317?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2023-54317 have an EU (EUVD) identifier?
- Yes. CVE-2023-54317 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-60487.
- When was CVE-2023-54317 published?
- CVE-2023-54317 was published on 2025-12-30 and last updated on 2026-06-17.
References
- https://git.kernel.org/stable/c/3c4a56ef7c538d16c1738ba0ccea9e7146105b5a
- https://git.kernel.org/stable/c/63d31617883d64b43b0e2d529f0751f40713ecae
- https://git.kernel.org/stable/c/98e311be44dbe31ad9c42aa067b2359bac451fda
- https://git.kernel.org/stable/c/b7f8892f672222dbfcc721f51edc03963212b249
- https://git.kernel.org/stable/c/be360c83f2d810493c04f999d69ec9152981e0c0
- https://git.kernel.org/stable/c/f2b478228bfdd11e358c5bc197561331f5d5c394
- https://git.kernel.org/stable/c/f50714b57aecb6b3dc81d578e295f86d9c73f078
- https://git.kernel.org/stable/c/ff60b2bb680ebcaf8890814dd51084a022891469