CVE-2025-38396: fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 66d29d757c968d2bee9124816da5d718eb352959, 6ca45ea48530332a4ba09595767bd26d3232743b, cbe4134ea4bc493239786220bd69cb8a13493190; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1.
Low priority for now. Upgrade to Linux Linux 66d29d757c968d2bee9124816da5d718eb352959, 6ca45ea48530332a4ba09595767bd26d3232743b, cbe4134ea4bc493239786220bd69cb8a13493190; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2025-10787
- ALSA-2025:16904
- RHSA-2025:16904
- RLSA-2025:16904
- SUSE-SU-2025:03636-1
- SUSE-SU-2025:03638-1
- SUSE-SU-2025:03646-1
- SUSE-SU-2025:03650-1
- SUSE-SU-2025:20873-1
- SUSE-SU-2025:20874-1
- SUSE-SU-2025:20875-1
- SUSE-SU-2025:20876-1
- SUSE-SU-2025:20877-1
- SUSE-SU-2025:20878-1
- SUSE-SU-2025:20879-1
- SUSE-SU-2025:20881-1
- SUSE-SU-2025:20882-1
- SUSE-SU-2025:20883-1
- SUSE-SU-2025:20884-1
- SUSE-SU-2025:20885-1
- Published
- Jul 25, 2025
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- 7.8
- CNA · Linux
- 7.8
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel6.0 and later · before 6.1.146
- linux linux kernel6.2 and later · before 6.6.97
- linux linux kernel6.7 and later · before 6.12.37
- linux linux kernel6.13 and later · before 6.15.6
- linux linux kernel6.16
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- 2bfe15c5261212130f1a71f32a300bcf426443d4 and later · before 66d29d757c968d2bee9124816da5d718eb352959affected · git
- 2bfe15c5261212130f1a71f32a300bcf426443d4 and later · before e3eed01347721cd7a8819568161c91d538fbf229affected · git
- 2bfe15c5261212130f1a71f32a300bcf426443d4 and later · before f94c422157f3e43dd31990567b3e5d54b3e5b32baffected · git
- 2bfe15c5261212130f1a71f32a300bcf426443d4 and later · before 6ca45ea48530332a4ba09595767bd26d3232743baffected · git
- 2bfe15c5261212130f1a71f32a300bcf426443d4 and later · before cbe4134ea4bc493239786220bd69cb8a13493190affected · git
- before 6.0not affected · semver
- 6.1.146 and later · up to and including 6.1.*not affected · semver
- 6.6.97 and later · up to and including 6.6.*not affected · semver
- 6.12.37 and later · up to and including 6.12.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.37.1.el10_0 | 6.12.0-55.37.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.37.1.el10_0 | 6.12.0-55.37.1.el10_0 |
| Debian:12 | linux | before 6.1.147-1 | 6.1.147-1 |
| Debian:13 | linux | before 6.12.37-1 | 6.12.37-1 |
| Red Hat:enterprise_linux:10.0 | kernel | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-core | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-core | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-debuginfo | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-devel | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-devel-matched | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-modules | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-modules-core | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debug-modules-extra | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-debuginfo | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-devel | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-devel-matched | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-modules | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-modules-core | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-64k-modules-extra | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-abi-stablelists | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-core | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
| Red Hat:enterprise_linux:10.0 | kernel-debug | before 0:6.12.0-55.37.1.el10_0 | 0:6.12.0-55.37.1.el10_0 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38394Jul 25, 2025 · HID: appletb-kbd: fix memory corruption of input_handler_list31Monitor
- ← EarlierCVE-2025-38395Jul 25, 2025 · regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods28Monitor
- Later →CVE-2025-38397Jul 25, 2025 · nvme-multipath: fix suspicious RCU usage warning22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 66d29d757c968d2bee9124816da5d718eb352959 | Vendor (CNA) |
| Linux Linux | 6ca45ea48530332a4ba09595767bd26d3232743b | Vendor (CNA) |
| Linux Linux | cbe4134ea4bc493239786220bd69cb8a13493190 | Vendor (CNA) |
| Linux Linux | e3eed01347721cd7a8819568161c91d538fbf229 | Vendor (CNA) |
| Linux Linux | f94c422157f3e43dd31990567b3e5d54b3e5b32b | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel-abi-stablelists | 6.12.0-55.37.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-55.37.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.147-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-devel-matched | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-aarch64 | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debuginfo-common-ppc64le | 0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| rocky linux:kernel | 0:6.12.0-55.37.1.el10_0 · Rocky Linux:10 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_4 | 11-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_5 | 10-1.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_6 | 8-3.1 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_7 | 8-1.3 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_8 | 7-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-MICRO-6-0-RT_Update_9 | 6-1.2 · SUSE:Linux Micro 6.0 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_10 | 8-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_13 | 6-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
+4
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6ca45ea48530332a4ba09595767bd26d3232743b
- git.kernel.org/stable/c/cbe4134ea4bc493239786220bd69cb8a13493190
- git.kernel.org/stable/c/e3eed01347721cd7a8819568161c91d538fbf229
- git.kernel.org/stable/c/f94c422157f3e43dd31990567b3e5d54b3e5b32b
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.