CVE-2026-99579 in Linuxinfo

Summary

by MITRE • 11/20/2026

In the Linux kernel, the following vulnerability has been resolved:

mm/shmem: honour F_SEAL_EXEC when an ACL is set

The owner of a memfd sealed with F_SEAL_EXEC can still change its execute bits by setting a POSIX access ACL. With CONFIG_TMPFS_POSIX_ACL, this lets an unprivileged owner make a non-executable memfd executable, bypassing vm.memfd_noexec=2.

simple_set_acl() updates i_mode directly, bypassing the seal check in shmem_setattr(). Add shmem_set_acl() to check the resulting mode. Share the F_SEAL_EXEC check with shmem_setattr() using memfd_check_seals_mode() in include/linux/memfd.h.

Fix generated by an LLM and sent by Chris Mason in private.

[ david: use common helper; simplify description ]

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/20/2026

The Linux kernel contains a vulnerability within the shared memory implementation, specifically affecting files created via memfd with the F_SEAL_EXEC seal applied when POSIX Access Control Lists are enabled. This issue arises because the mechanism designed to prevent execution of sealed memory regions can be circumvented through the manipulation of file permissions using ACLs. The core technical flaw lies in how access control lists are processed during attribute updates. When a user sets an ACL on a memfd, the function simple_set_acl is invoked, which directly modifies the inode mode bits representing execute permissions without invoking the standard setattr path that performs seal validation checks. This direct modification bypasses the security controls enforced by shmem_setattr, allowing an unprivileged process to alter execution rights despite having explicitly sealed those attributes during file creation.

The operational impact of this vulnerability is significant for systems relying on strict memory execution policies, particularly in containerized or sandboxed environments where vm.memfd_noexec=2 is configured to enforce non-executable shared memory segments. An attacker with write access to a memfd object can exploit this flaw to transition the file from a non-executable state to an executable one. This effectively nullifies the protective intent of the F_SEAL_EXEC flag, enabling the execution of code in regions that were intended to be read-only or data-only. Such bypasses are particularly dangerous as they allow for potential privilege escalation or arbitrary code execution within contexts where memory protection is a primary defense mechanism against exploits like buffer overflows or return-oriented programming attacks.

From a standards perspective, this vulnerability aligns with CWE-284 Improper Access Control and CWE-732 Incorrect Permission Assignment for Critical Resource. The failure to validate permission changes against existing security seals represents a classic access control bypass where the enforcement logic is incomplete regarding specific attribute modification paths. In terms of MITRE ATT&CK mapping, this behavior facilitates techniques related to Defense Evasion by allowing an adversary to modify file attributes to execute malicious payloads in protected memory spaces, potentially leveraging T1059 Command and Scripting Interpreter or T1204 User Execution depending on the subsequent exploitation steps taken after gaining execution capability.

The resolution involves introducing a dedicated function shmem_set_acl that intercepts ACL modifications before they are applied to the inode mode. This new function utilizes a shared helper, memfd_check_seals_mode located in include/linux/memfd.h, which is also used by shmem_setattr to ensure consistent enforcement of seals across different attribute modification paths. By centralizing the seal validation logic, the kernel ensures that any attempt to change execute permissions on a sealed memfd will be rejected if it violates the F_SEAL_EXEC constraint. This fix restores the integrity of memory sealing mechanisms and prevents unprivileged users from bypassing execution restrictions through ACL manipulation. System administrators should ensure their kernels are updated with this patch applied, particularly in environments where strict separation between executable and non-executable shared memory is required for security compliance or exploit mitigation strategies.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00177

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!