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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 7.8NVD modified 2026-10-15 22:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 8
- 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