LiveActive security incident?Get immediate response
CVE Record

CVE-2024-58092: nfsd: fix legacy client tracking initialization

In the Linux kernel, the following vulnerability has been resolved: nfsd: fix legacy client tracking initialization Get rid of the nfsd4_legacy_tracking_ops->init() call in check_for_legacy_methods(). That will be handled in the caller (nfsd4_client_tracking_init()). Otherwise, we'll wind up calling nfsd4_legacy_tracking_ops->init() twice, and the second time we'll trigger the BUG_ON() in nfsd4_init_recdir().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects NFS server code. A legacy client-tracking initialization path can run twice and hit a kernel BUG condition. The available sources do not provide CVSS, exploit prerequisites, or proof of exploitation, so treat it as a potentially disruptive availability risk on systems running affected kernels with NFS server functionality.

Executive priority

Prioritize as an operational stability issue for Linux NFS servers. Escalate patching for critical file-sharing infrastructure, but do not treat it as confirmed active exploitation based on the supplied evidence.

Technical view

The nfsd legacy tracking initialization flow incorrectly calls nfsd4_legacy_tracking_ops->init() in check_for_legacy_methods(), while nfsd4_client_tracking_init() also handles initialization. The duplicate call can trigger BUG_ON() in nfsd4_init_recdir(). Kernel stable commits remove the redundant initialization call.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel versions where the NFS server component, nfsd, is enabled or configured. The source bundle lists affected Linux kernel lines but does not provide distribution-specific package status or configuration prerequisites.

Exploitation context

No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The bundle does not describe a public exploit, remote trigger conditions, authentication requirements, or attacker workflow. Evidence supports a kernel availability concern, not confirmed weaponized exploitation.

Researcher notes

Key evidence is narrow: duplicate nfsd legacy tracking initialization can hit BUG_ON(). Missing data includes CVSS, CWE, exploitability analysis, and distro advisories. Researchers should focus validation on NFS server enablement, kernel lineage, and whether vendor kernels contain the stable commits.

Mitigation direction

  • Apply kernel updates that include the referenced stable fixes.
  • Check Linux distribution advisories for backported patches and package names.
  • Disable NFS server functionality where it is not required.
  • Prioritize internet-exposed or business-critical NFS servers for remediation.
  • Avoid assuming fixed status from upstream versions alone; verify vendor backports.

Validation and detection

  • Inventory Linux hosts running NFS server services.
  • Map running kernel packages to vendor advisories for CVE-2024-58092.
  • Verify patched kernels include the referenced nfsd initialization fix.
  • Review kernel logs for nfsd BUG or initialization failures.
  • Test NFS server startup and client recovery behavior after patching.
Prepared
Confidence
medium
Sources
5

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-58092 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
0ADP providers
4Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux74fd48739d0488e39ae18b0168720f449a06690c, 74fd48739d0488e39ae18b0168720f449a06690c, 74fd48739d0488e39ae18b0168720f449a06690cunaffected
LinuxLinux6.8, 0, 6.12.22, 6.13.10, 6.14affected
Weakness

CWE details

No CWE listed

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