FlawAtlas
Search the atlas
CVE-2025-38396 Not scored

fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass

In the Linux kernel, the following vulnerability has been resolved: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass Export anon_inode_make_secure_inode() to allow KVM guest_memfd to create anonymous inodes with proper security context. This replaces the current pattern of calling alloc_anon_inode() followed by inode_init_security_anon() for creating security context manually. This change also fixes a security regression in secretmem where the S_PRIVATE flag was not cleared after alloc_anon_inode(), causing LSM/SELinux checks to be bypassed for secretmem file descriptors. As guest_memfd currently resides in the KVM module, we need to export this symbol for use outside the core kernel. In the future, guest_memfd might be moved to core-mm, at which point the symbols no longer would have to be exported. When/if that happens is still unclear.

Exploit probability 0.2%
Published July 25, 2025
Required by Not available
Last source change July 15, 2026

02 / AFFECTED SOFTWARE

Affected packages

Linux Kernel
Unknown Unknown

03 / CONNECTIONS

Connected vulnerabilities

related ALSA-2025:16904
related ALSA-2025:20518
related OPENSUSE-SU-2025:20081-1
related SUSE-SU-2025:02853-1
related SUSE-SU-2025:02923-1
related SUSE-SU-2025:02969-1
related SUSE-SU-2025:02996-1
related SUSE-SU-2025:02997-1
related SUSE-SU-2025:03011-1
related SUSE-SU-2025:03023-1
related SUSE-SU-2025:03636-1
related SUSE-SU-2025:03638-1
related SUSE-SU-2025:03646-1
related SUSE-SU-2025:03650-1
related SUSE-SU-2025:20577-1
related SUSE-SU-2025:20586-1
related SUSE-SU-2025:20601-1
related SUSE-SU-2025:20602-1
related SUSE-SU-2025:20873-1
related SUSE-SU-2025:20874-1
related SUSE-SU-2025:20875-1
related SUSE-SU-2025:20876-1
related SUSE-SU-2025:20877-1
related SUSE-SU-2025:20878-1
related SUSE-SU-2025:20879-1
related SUSE-SU-2025:20881-1
related SUSE-SU-2025:20882-1
related SUSE-SU-2025:20883-1
related SUSE-SU-2025:20884-1
related SUSE-SU-2025:20885-1
related SUSE-SU-2025:20886-1
related SUSE-SU-2025:20887-1
related SUSE-SU-2025:20888-1
related SUSE-SU-2025:20890-1
related SUSE-SU-2025:20891-1
related SUSE-SU-2025:20902-1
related SUSE-SU-2025:20903-1
related SUSE-SU-2025:20904-1
related SUSE-SU-2025:20905-1
related SUSE-SU-2025:20906-1
related SUSE-SU-2025:20907-1
related SUSE-SU-2025:20909-1
related SUSE-SU-2025:20912-1
related SUSE-SU-2025:20913-1
related SUSE-SU-2025:20914-1
related SUSE-SU-2025:20915-1
related SUSE-SU-2025:20916-1
related SUSE-SU-2025:20917-1
related SUSE-SU-2025:20918-1
related SUSE-SU-2025:20920-1
related SUSE-SU-2025:21074-1
related SUSE-SU-2025:21139-1
related SUSE-SU-2025:21179-1
related SUSE-SU-2025:3742-1
related SUSE-SU-2025:3748-1
related SUSE-SU-2025:3755-1
related SUSE-SU-2025:3762-1
related SUSE-SU-2025:3764-1
related SUSE-SU-2025:3765-1
related SUSE-SU-2025:3768-1
related SUSE-SU-2025:3771-1
related SUSE-SU-2025:3772-1

04 / EVIDENCE

Source records

Open Source Vulnerabilities CVE-2025-38396

In the Linux kernel, the following vulnerability has been resolved: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass Export anon_inode_make_secure_inode() to allow KVM guest_memfd to create anonymous inodes with proper security context. This replaces the current pattern of calling alloc_anon_inode() followed by inode_init_security_anon() for creating security context manually. This change also fixes a security regression in secretmem where the S_PRIVATE flag was not cleared after alloc_anon_inode(), causing LSM/SELinux checks to be bypassed for secretmem file descriptors. As guest_memfd currently resides in the KVM module, we need to export this symbol for use outside the core kernel. In the future, guest_memfd might be moved to core-mm, at which point the symbols no longer would have to be exported. When/if that happens is still unclear.

View original source

05 / REFERENCES

Further evidence