LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50057: fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix NULL deref in ntfs_update_mftmirr If ntfs_fill_super() wasn't called then sbi->sb will be equal to NULL. Code should check this ptr before dereferencing. Syzbot hit this issue via passing wrong mount param as can be seen from log below Fail log: ntfs3: Unknown parameter 'iochvrset' general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f] CPU: 1 PID: 3589 Comm: syz-executor210 Not tainted 5.18.0-rc3-syzkaller-00016-gb253435746d9 #0 ... Call Trace: <TASK> put_ntfs+0x1ed/0x2a0 fs/ntfs3/super.c:463 ntfs_fs_free+0x6a/0xe0 fs/ntfs3/super.c:1363 put_fs_context+0x119/0x7a0 fs/fs_context.c:469 do_new_mount+0x2b4/0xad0 fs/namespace.c:3044 do_mount fs/namespace.c:3383 [inline] __do_sys_mount fs/namespace.c:3591 [inline]

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel crash bug in the ntfs3 filesystem driver. A malformed or invalid NTFS mount setup could reach cleanup code that dereferences a NULL pointer. The disclosed impact is denial of service through a kernel fault, not data theft or remote compromise.

Executive priority

Treat this as a kernel reliability and availability issue. Prioritize routine kernel patching, especially on multi-user Linux systems or hosts processing removable or user-supplied NTFS media. No source evidence supports emergency remote-exploitation response.

Technical view

The issue is in fs/ntfs3 ntfs_update_mftmirr cleanup behavior. If ntfs_fill_super() was not called, sbi->sb can remain NULL, but later code dereferenced it. The source describes syzbot triggering the fault with an invalid mount parameter. Stable kernel commits add the missing NULL check.

Likely exposure

Exposure is limited to Linux systems with affected kernels and ntfs3 filesystem support where an actor can trigger NTFS mount handling. Source data lists Linux kernel versions including 5.15, 5.15.63, 5.19.4, and 6.0 as affected, but distro backports must be checked.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, public exploit use, or remote attack evidence. The only described trigger is syzbot passing a wrong mount parameter during mount processing.

Researcher notes

The evidence points to a NULL pointer dereference in ntfs3 error cleanup after failed superblock initialization. Impact assessment is constrained by missing CVSS, CWE, and exploitability details. Validate against downstream kernel patches because enterprise distributions may backport fixes without changing upstream version numbers.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for backported CVE-2022-50057 fixes.
  • If patching is delayed, follow vendor guidance for ntfs3 risk reduction.
  • Review whether untrusted users can initiate filesystem mounts.

Validation and detection

  • Inventory Linux kernel versions across affected servers and endpoints.
  • Check whether ntfs3 support is present, loaded, or required.
  • Compare installed kernel packages with distribution CVE fix status.
  • Confirm fixed stable commits or equivalent backports are included.
  • Prioritize systems allowing user-controlled mount workflows.
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-2022-50057 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
LinuxLinux82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17unaffected
LinuxLinux5.15, 0, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

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