LiveActive security incident?Get immediate response
CVE Record

CVE-2024-54456: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client()

In the Linux kernel, the following vulnerability has been resolved: NFS: Fix potential buffer overflowin nfs_sysfs_link_rpc_client() name is char[64] where the size of clnt->cl_program->name remains unknown. Invoking strcat() directly will also lead to potential buffer overflow. Change them to strscpy() and strncat() to fix potential issues.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-54456 is a Linux kernel NFS flaw involving a possible buffer overflow when linking an RPC client into sysfs. The public record does not provide CVSS, exploitability, or impact details. Treat it as a kernel maintenance priority for systems using NFS, especially servers or appliances where kernel updates are controlled separately.

Executive priority

Schedule remediation through normal kernel patching, with priority for NFS-dependent production systems. There is no sourced evidence of active exploitation, but kernel memory-safety issues can become more serious as analysis matures.

Technical view

The issue is in nfs_sysfs_link_rpc_client(). A fixed-size char[64] name buffer was built using strcat() while clnt->cl_program->name length was not known, creating potential overflow risk. Kernel fixes replace unsafe string handling with bounded strscpy() and strncat(). Public sources identify Linux kernel NFS and stable kernel commits, but not a detailed attack path.

Likely exposure

Exposure is most relevant to Linux systems with the NFS client/kernel NFS code present or used. The source bundle lists Linux kernel versions and stable commits, but the affected-version data is not sufficiently clear to map every distribution kernel without vendor backport information.

Exploitation context

No active exploitation is indicated: this CVE is not listed as KEV in the provided data, and no cited source claims exploitation. Public information describes a potential buffer overflow, not a proven remote exploit or privilege-escalation chain.

Researcher notes

The CVE record lacks CVSS, CWE, and concrete impact details. The fix is a defensive bounds-checking change in NFS sysfs RPC client name handling. Distribution advisories are needed to determine exact affected builds because kernel vendors may backport fixes without changing upstream version numbers.

Mitigation direction

  • Apply Linux kernel updates from your distribution or vendor when available.
  • Prioritize systems using NFS or hosting critical workloads.
  • Confirm updates include the referenced stable kernel fixes or vendor backports.
  • If updates are unavailable, monitor vendor guidance for supported workarounds.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Identify systems using or loading NFS functionality.
  • Compare installed kernels against vendor advisories and fixed stable commits.
  • Verify patched kernels are deployed after maintenance windows.
Prepared
Confidence
medium
Sources
6

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-54456 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
5Source 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
LinuxLinuxe13b549319a684dd80c4cc25e9567a5c84007e32, e13b549319a684dd80c4cc25e9567a5c84007e32, e13b549319a684dd80c4cc25e9567a5c84007e32, e13b549319a684dd80c4cc25e9567a5c84007e32unaffected
LinuxLinux6.5, 0, 6.6.79, 6.12.16, 6.13.4, 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.