LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54264: fs/sysv: Null check to prevent null-ptr-deref bug

In the Linux kernel, the following vulnerability has been resolved: fs/sysv: Null check to prevent null-ptr-deref bug sb_getblk(inode->i_sb, parent) return a null ptr and taking lock on that leads to the null-ptr-deref bug.

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-54264 is a Linux kernel bug in the SysV filesystem code. A failed block lookup can return NULL, and the kernel then tries to lock it, causing a NULL pointer dereference. The public record does not provide CVSS, exploitability, or business impact detail.

Executive priority

Treat as a patch-management item with uncertain severity. Prioritize exposed Linux systems and platforms handling untrusted filesystem images, but do not escalate as exploited based on the provided evidence.

Technical view

The issue is in fs/sysv: sb_getblk(inode->i_sb, parent) may return NULL, followed by locking that pointer. The linked Linux stable commits add a NULL check. The bundle supports a kernel availability/stability concern but does not establish remote code execution, privilege escalation, or data exposure.

Likely exposure

Exposure is likely limited to systems running affected Linux kernel versions where SysV filesystem code is present and reachable. Distribution backports may change actual status, so kernel package advisories must be checked.

Exploitation context

The bundle does not report active exploitation, and KEV is false. It also does not describe attack prerequisites, whether mounting a crafted filesystem is required, or whether an unprivileged user can trigger the fault.

Researcher notes

Evidence is thin: no CVSS, CWE, exploit narrative, or prerequisite detail is provided. Analysis should focus on the stable commits and downstream vendor advisories to determine reachable code paths and fixed package versions.

Mitigation direction

  • Check Linux distribution advisories for CVE-2023-54264 coverage.
  • Apply kernel updates containing the linked fs/sysv NULL-check fixes.
  • Prioritize systems that allow SysV filesystem mounting or process untrusted disk images.
  • Restrict unnecessary filesystem mounting paths until vendor guidance is applied.

Validation and detection

  • Inventory kernel versions against the affected Linux versions in the CVE record.
  • Confirm whether vendor kernels include one of the linked stable commits or equivalent backport.
  • Review systems for SysV filesystem usage or mounted SysV filesystems.
  • Track patch status through normal vulnerability management reporting.
Prepared
Confidence
medium
Sources
10

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-54264 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
9Source 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
LinuxLinuxe5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58, e5657933863f43cc6bb76a54d659303dafaa9e58unaffected
LinuxLinux2.6.19, 0, 4.14.322, 4.19.291, 5.4.253, 5.10.190, 5.15.126, 6.1.45, 6.4.10, 6.5affected
Weakness

CWE details

No CWE listed

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