CVE-2024-50182

In the Linux kernel, the following vulnerability has been resolved: secretmem: disable memfd_secret() if arch cannot set direct map Return -ENOSYS from memfd_secret() syscall if !can_set_direct_map(). This is the case for example on some arm64 configurations, where marking 4k PTEs in the direct map not present can only be done if the direct map is set up at 4k granularity in the first place (as ARM's break-before-make semantics do not easily allow breaking apart large/gigantic pages). More precisely, on arm64 systems with !can_set_direct_map(), set_direct_map_invalid_noflush() is a no-op, however it returns success (0) instead of an error. This means that memfd_secret will seemingly "work" (e.g. syscall succeeds, you can mmap the fd and fault in pages), but it does not actually achieve its goal of removing its memory from the direct map. Note that with this patch, memfd_secret() will start erroring on systems where can_set_direct_map() returns false (arm64 with CONFIG_RODATA_FULL_DEFAULT_ENABLED=n, CONFIG_DEBUG_PAGEALLOC=n and CONFIG_KFENCE=n), but that still seems better than the current silent failure. Since CONFIG_RODATA_FULL_DEFAULT_ENABLED defaults to 'y', most arm64 systems actually have a working memfd_secret() and aren't be affected. From going through the iterations of the original memfd_secret patch series, it seems that disabling the syscall in these scenarios was the intended behavior [1] (preferred over having set_direct_map_invalid_noflush return an error as that would result in SIGBUSes at page-fault time), however the check for it got dropped between v16 [2] and v17 [3], when secretmem moved away from CMA allocations. [1]: https://lore.kernel.org/lkml/20201124164930.GK8537@kernel.org/ [2]: https://lore.kernel.org/lkml/20210121122723.3446-11-rppt@kernel.org/#t [3]: https://lore.kernel.org/lkml/20201125092208.12544-10-rppt@kernel.org/

• https://git.kernel.org/stable/c/532b53cebe58f34ce1c0f34d866f5c0e335c53c6Patch
• https://git.kernel.org/stable/c/5ea0b7af38754d2b45ead9257bca47e84662e926Patch
• https://git.kernel.org/stable/c/757786abe4547eb3d9d0e8350a63bdb0f9824af2Patch
• https://git.kernel.org/stable/c/7caf966390e6e4ebf42775df54e7ee1f280ce677Patch
• https://git.kernel.org/stable/c/d0ae6ffa1aeb297aef89f49cfb894a83c329ebadPatch
• https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Published

Nov 8, 2024

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-50177In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-50178In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-50179In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-5018In WhatsUp Gold versions released before 2023.1.3, an unauth…7.5
• CVE-2024-50180In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-50181Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2024-50183In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2024-50184In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-50185In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-50186In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2024-50187In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-50188In the Linux kernel, the following vulnerability has been re…5.5