CVE-2023-52429: Linux kernel · Excessive Memory Allocation
Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.7.5 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Affects
- Linux kernel through 6.7.4
- Patch
- Available – fixed in 6.7.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Feb 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor Linux kernel updates and apply patches promptly once available for versions up to 6.7.4 to address this vulnerability.
- Restrict local access to trusted users only, minimizing the risk of exploitation by unauthorized personnel.
- Implement strict access controls and auditing on systems running vulnerable kernels to detect suspicious activities or attempts to trigger the vulnerability.
- Use kernel hardening techniques such as SELinux or AppArmor to limit the impact of potential exploits.
- For environments using device mapper extensively, conduct thorough testing of kernel updates in staging before production deployment to ensure stability.
- Employ system monitoring tools to detect abnormal kernel crashes or memory allocation failures that may indicate exploitation attempts.
- Consider isolating critical Linux hosts or using virtualization/containerization to contain potential impact.
- Educate system administrators about the vulnerability and safe handling of local privileges to reduce insider risk.
Description
dm_table_create in drivers/md/dm-table.c in the Linux kernel through 6.7.4 can attempt to (in alloc_targets) allocate more than INT_MAX bytes, and crash, because of a missing check for struct dm_ioctl.target_count.
References
- spinics.net/lists/dm-devel/msg56625.html (opens in a new tab)
- git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd504bcfec41a503b32054da5472904b404341a4 (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GS7S3XLTLOUKBXV67LLFZWB3YVFJZHRK/ (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3LZROQAX7Q7LEP4F7WQ3KUZKWCZGFFP2/ (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/06/msg00017.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/06/msg00020.html (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3LZROQAX7Q7LEP4F7WQ3KUZKWCZGFFP2/ (opens in a new tab)