CVE-2025-38396
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Modified
Affected
- Linux Kernel < 6.1.146
- Linux Kernel < 6.6.97
- Linux Kernel < 6.12.37
- Linux Kernel < 6.15.6
- Linux Kernel 6.16
- Debian Linux 11.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38396.md and follow it. Check whether this project is affected by CVE-2025-38396. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/66d29d757c968d2bee9124816da5d718eb352959
- https://git.kernel.org/stable/c/6ca45ea48530332a4ba09595767bd26d3232743b
- https://git.kernel.org/stable/c/cbe4134ea4bc493239786220bd69cb8a13493190
- https://git.kernel.org/stable/c/e3eed01347721cd7a8819568161c91d538fbf229
- https://git.kernel.org/stable/c/f94c422157f3e43dd31990567b3e5d54b3e5b32b
References
- https://git.kernel.org/stable/c/66d29d757c968d2bee9124816da5d718eb352959
- https://git.kernel.org/stable/c/6ca45ea48530332a4ba09595767bd26d3232743b
- https://git.kernel.org/stable/c/cbe4134ea4bc493239786220bd69cb8a13493190
- https://git.kernel.org/stable/c/e3eed01347721cd7a8819568161c91d538fbf229
- https://git.kernel.org/stable/c/f94c422157f3e43dd31990567b3e5d54b3e5b32b
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html