LiveActive security incident?Get immediate response
CVE Record

CVE-2025-39798: NFS: Fix the setting of capabilities when automounting a new filesystem

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix the setting of capabilities when automounting a new filesystem Capabilities cannot be inherited when we cross into a new filesystem. They need to be reset to the minimal defaults, and then probed for again.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux NFS automount can carry capability settings into a newly crossed filesystem instead of safely resetting and rediscovering them. This may cause the kernel to make incorrect assumptions about the new filesystem, potentially affecting confidentiality, integrity, or availability. Systems not using NFS automounting are less likely to be exposed.

Executive priority

Treat this as an expedited patching priority for NFS automount environments, especially externally connected or business-critical systems. First confirm actual NFS automount use and vendor package status. Systems without this functionality can receive lower priority after documented verification.

Technical view

During NFS automounting, the kernel may inherit capability state across a new filesystem boundary. The fix resets that state to minimal defaults and probes again. The supplied CVSS 3.1 vector indicates network access, low complexity, no privileges or user interaction, and low confidentiality, integrity, and availability impacts. Concrete failure modes are not documented.

Likely exposure

Exposure is concentrated on Linux systems using NFS automounting, particularly workflows crossing into newly mounted filesystems. The bundle lists affected branch versions from 2.6.19 through 6.17 and provides multiple stable-branch fixes. Distribution backports make assessment by version string alone unreliable; confirm status with the relevant vendor.

Exploitation context

The source bundle provides no evidence of active exploitation, public weaponization, or observed attacks, and marks the CVE as absent from KEV. The CVSS vector suggests a network-reachable, unauthenticated condition, but the sources do not document practical prerequisites or a demonstrated attack path.

Researcher notes

In context, “capabilities” likely refers to NFS filesystem or server feature state, not Linux process privileges; the supplied description does not explicitly define it. Evidence establishes improper state inheritance and the reset-and-reprobe correction, but does not describe a reproducer, concrete corruption scenario, affected NFS versions, or confirmed exploitability.

Mitigation direction

  • Apply the vendor kernel update incorporating the fix for the system's applicable stable branch.
  • Prioritize systems using NFS automounts or crossing into separately mounted NFS filesystems.
  • If updates are unavailable, consult vendor guidance; the supplied sources identify no validated workaround.
  • Activate the updated kernel according to the vendor's maintenance procedure.

Validation and detection

  • Inventory Linux hosts using NFS automounting and record their running kernels and distribution packages.
  • Map each kernel package to vendor advisories and the applicable upstream stable fix commit.
  • Confirm the active kernel contains the correction after maintenance.
  • Retest NFS automount workflows that cross filesystem boundaries for normal operation.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-39798 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
14Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2025-39798Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25b, 54ceac4515986030c2502960be620198dd8fe25bunaffected
LinuxLinux2.6.19, 0, 5.4.297, 5.10.241, 5.15.190, 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.