LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54248: fs/ntfs3: Add check for kmemdup

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Add check for kmemdup Since the kmemdup may return NULL pointer, it should be better to add check for the return value in order to avoid NULL pointer dereference.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-54248 is a Linux kernel ntfs3 filesystem bug where memory allocation could fail and the code could still use a NULL pointer. The provided sources do not give CVSS, full impact, or exploitation details. Business urgency is highest where Linux systems process NTFS filesystems or removable media.

Executive priority

Prioritize as kernel hygiene, not an emergency, unless NTFS handling is business-critical or exposed to untrusted media. The absence of CVSS and exploitation evidence limits urgency, but kernel crashes can still affect availability.

Technical view

The resolved Linux kernel issue adds a missing check after kmemdup in fs/ntfs3 to avoid a NULL pointer dereference. The bundle identifies affected Linux kernel version ranges and stable commit references. It does not specify prerequisites, privilege requirements, or whether the dereference is reliably triggerable.

Likely exposure

Exposure likely applies to Linux systems running affected kernels with the ntfs3 filesystem code available, especially systems that mount or inspect NTFS volumes. The bundle does not confirm exposure for systems without ntfs3 enabled or used.

Exploitation context

No active exploitation is supported by the supplied sources; KEV is false. The source bundle does not cite exploit availability, trigger mechanics, or real-world attacks. Treat offensive feasibility as unconfirmed.

Researcher notes

Evidence supports a NULL pointer dereference fix in fs/ntfs3 after kmemdup failure. The bundle lacks CWE, CVSS, trigger path, exploitability, and impact detail. Avoid overstating beyond potential availability impact from a kernel NULL dereference.

Mitigation direction

  • Apply a vendor kernel update that includes the referenced stable fixes.
  • Check distribution advisories for backported fixes before relying on version strings.
  • Reduce or avoid ntfs3 filesystem use until patched where operationally feasible.
  • Prioritize systems that process removable media or untrusted NTFS volumes.

Validation and detection

  • Inventory Linux kernel versions across affected assets.
  • Verify patched kernels include the referenced stable commit or vendor backport.
  • Check whether ntfs3 is enabled, loaded, or used operationally.
  • Review vendor advisories for exact package-level fixed versions.
Prepared
Confidence
medium
Sources
7

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-2023-54248 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
6Source 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
LinuxLinuxb46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445, b46acd6a6a627d876898e1c84d3f84902264b445unaffected
LinuxLinux5.15, 0, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4affected
Weakness

CWE details

No CWE listed

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