LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46690: nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfsd4_deleg_getattr_conflict in presence of third party lease It is not safe to dereference fl->c.flc_owner without first confirming fl->fl_lmops is the expected manager. nfsd4_deleg_getattr_conflict() tests fl_lmops but largely ignores the result and assumes that flc_owner is an nfs4_delegation anyway. This is wrong. With this patch we restore the "!= &nfsd_lease_mng_ops" case to behave as it did before the change mentioned below. This is the same as the current code, but without any reference to a possible delegation.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux NFS server flaw can make the kernel treat a third-party lease owner as an NFSv4 delegation. This unsafe assumption may cause serious security impact when affected NFS functionality is reachable. The supplied record rates it critical, but does not describe a demonstrated attack or confirmed real-world exploitation.

Executive priority

Treat as urgent for organizations operating exposed or broadly reachable Linux NFS servers. Rapidly identify affected assets and schedule vendor-supported kernel updates. Systems not providing NFS services are lower priority for this specific flaw. Escalate exceptions because the supplied severity is critical, while recognizing exploitation evidence is absent.

Technical view

In nfsd4_deleg_getattr_conflict(), the kernel could dereference fl->c.flc_owner as an nfs4_delegation even when fl->fl_lmops identified a different lease manager. The fix restores safe handling for non-nfsd lease-manager operations and avoids referencing a possible delegation in that case.

Likely exposure

Exposure is limited to Linux systems running the affected kernel code and using the NFS server functionality implicated by the flaw. The bundle identifies Linux 6.9, 6.10.8, and 6.11 as affected, but its version data is ambiguous; confirm exact vulnerable ranges with the distribution or kernel maintainer.

Exploitation context

The supplied CVE is not in KEV, and no cited source reports active exploitation or provides evidence of a public exploit. The network-based 9.8 CVSS rating indicates potentially severe remote impact, but the bundle does not establish practical attack prerequisites beyond the affected NFS server path.

Researcher notes

The core defect is an unsafe owner dereference across lease-manager types. The record supplies no CWE, crash trace, reproducer, or proof of confidentiality, integrity, and availability impact. Review the two stable commits and surrounding regression history to determine branch-specific exposure; do not infer vulnerable distribution kernels solely from upstream version labels.

Mitigation direction

  • Apply a vendor-supported kernel update incorporating one of the cited upstream stable fixes.
  • Prioritize internet-facing or untrusted-network NFS servers for assessment and maintenance.
  • Restrict NFS access to trusted networks while awaiting an applicable update.
  • Check distribution guidance before relying on version numbers alone.

Validation and detection

  • Inventory systems running the Linux NFS server and record their exact kernel builds.
  • Compare distribution kernel builds against vendor advisories and the cited fix commits.
  • Confirm the running kernel changed after updating and rebooting.
  • Verify NFS exposure using approved configuration and network-access reviews.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2024-46690 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-46690Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc5967721e1063648b0506481585ba7e2e49a075e, c5967721e1063648b0506481585ba7e2e49a075eunaffected
LinuxLinux6.9, 0, 6.10.8, 6.11affected
Weakness

CWE details

No CWE listed

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