Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2025
Updated
Aug 5, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2025-38396

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel
debiandebian 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.37.1.el10_06.12.0-55.37.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.37.1.el10_06.12.0-55.37.1.el10_0
Debian:12linuxbefore 6.1.147-16.1.147-1
Debian:13linuxbefore 6.12.37-16.12.37-1
Red Hat:enterprise_linux:10.0kernelbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64kbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-corebefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debugbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-corebefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-debuginfobefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-develbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-devel-matchedbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modulesbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-corebefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debug-modules-extrabefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-debuginfobefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-develbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-devel-matchedbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modulesbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-corebefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-64k-modules-extrabefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-abi-stablelistsbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-corebefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0
Red Hat:enterprise_linux:10.0kernel-debugbefore 0:6.12.0-55.37.1.el10_00:6.12.0-55.37.1.el10_0

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38394Jul 25, 2025 · HID: appletb-kbd: fix memory corruption of input_handler_list
    31Monitor
  • ← EarlierCVE-2025-38395Jul 25, 2025 · regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods
    28Monitor
  • Later →CVE-2025-38397Jul 25, 2025 · nvme-multipath: fix suspicious RCU usage warning
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux66d29d757c968d2bee9124816da5d718eb352959Vendor (CNA)
Linux Linux6ca45ea48530332a4ba09595767bd26d3232743bVendor (CNA)
Linux Linuxcbe4134ea4bc493239786220bd69cb8a13493190Vendor (CNA)
Linux Linuxe3eed01347721cd7a8819568161c91d538fbf229Vendor (CNA)
Linux Linuxf94c422157f3e43dd31990567b3e5d54b3e5b32bVendor (CNA)
azl3 kernel 6.6.96.2-2 on Azure Linux 3.06.6.104.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel-abi-stablelists6.12.0-55.37.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.37.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.147-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-aarch640:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:6.12.0-55.37.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
rocky linux:kernel0:6.12.0-55.37.1.el10_0 · Rocky Linux:10Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_411-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_510-1.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_68-3.1 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_78-1.3 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_87-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-MICRO-6-0-RT_Update_96-1.2 · SUSE:Linux Micro 6.0Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_108-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package registry (OSV)
suse:kernel-livepatch-SLE15-SP6-RT_Update_136-150600.2.1 · SUSE:Linux Enterprise Live Patching 15 SP6Package 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.

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records