Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-38396fs: export anon_inode_make_secure_inode() and fix secretmem LSM bypass

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38396, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 2bfe15c5261212130f1a71f32a300bcf426443d4 – < 66d29d757c968d2bee9124816da5d718eb352959
    • affected 2bfe15c5261212130f1a71f32a300bcf426443d4 – < e3eed01347721cd7a8819568161c91d538fbf229
    • affected 2bfe15c5261212130f1a71f32a300bcf426443d4 – < f94c422157f3e43dd31990567b3e5d54b3e5b32b
    • affected 2bfe15c5261212130f1a71f32a300bcf426443d4 – < 6ca45ea48530332a4ba09595767bd26d3232743b
    • affected 2bfe15c5261212130f1a71f32a300bcf426443d4 – < cbe4134ea4bc493239786220bd69cb8a13493190
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.146 – ≤ 6.1.*
    • unaffected 6.6.97 – ≤ 6.6.*
    • unaffected 6.12.37 – ≤ 6.12.*
    • unaffected 6.15.6 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38396 badge
[![CVE-2025-38396](https://cveledger.app/badge/CVE-2025-38396.svg)](https://cveledger.app/cve/CVE-2025-38396)

Record last updated .