LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50451: fs/ntfs3: Fix memory leak on ntfs_fill_super() error path

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak on ntfs_fill_super() error path syzbot reported kmemleak as below: BUG: memory leak unreferenced object 0xffff8880122f1540 (size 32): comm "a.out", pid 6664, jiffies 4294939771 (age 25.500s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 ed ff ed ff 00 00 00 00 ................ backtrace: [<ffffffff81b16052>] ntfs_init_fs_context+0x22/0x1c0 [<ffffffff8164aaa7>] alloc_fs_context+0x217/0x430 [<ffffffff81626dd4>] path_mount+0x704/0x1080 [<ffffffff81627e7c>] __x64_sys_mount+0x18c/0x1d0 [<ffffffff84593e14>] do_syscall_64+0x34/0xb0 [<ffffffff84600087>] entry_SYSCALL_64_after_hwframe+0x63/0xcd This patch fixes this issue by freeing mount options on error path of ntfs_fill_super().

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in the NTFS3 filesystem mount error path. It was found by syzbot, not reported as actively exploited. Business urgency is mainly for systems that mount NTFS volumes or images, where repeated failures could waste kernel memory.

Executive priority

Handle through normal kernel patch management unless NTFS mounting is common or exposed to untrusted inputs. There is no source-backed active exploitation signal, but kernel memory leaks can affect availability if repeatedly triggered.

Technical view

During NTFS3 mounting, memory allocated for mount options could remain unfreed when ntfs_fill_super() failed. The cited kernel fix frees those mount options on the error path. The source bundle provides no CVSS, CWE, or exploitability detail.

Likely exposure

Exposure appears limited to Linux systems with the ntfs3 filesystem path available and workflows that mount NTFS media or images. Risk is higher where users, services, or automation can trigger NTFS mounts. The sources do not establish remote exposure.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The available evidence is a syzbot kmemleak report showing leakage during a mount syscall, not a public exploit report.

Researcher notes

Focus validation on the NTFS3 mount error path and downstream backports of the listed kernel commits. The source data is sparse: affected version ranges are listed, but no CVSS vector, CWE classification, exploit status, or distribution-specific package fixes are provided.

Mitigation direction

  • Apply Linux kernel vendor updates containing the referenced stable fixes.
  • Prioritize hosts that mount NTFS removable media, disk images, or shared storage.
  • If patching is delayed, reduce unnecessary NTFS3 mount capability where operationally feasible.
  • Track distribution advisories for the exact fixed kernel package version.

Validation and detection

  • Inventory Linux kernel versions and compare them with vendor fixed releases.
  • Identify systems where NTFS3 support is enabled or routinely used.
  • Confirm installed kernels include one of the referenced stable commits or downstream equivalents.
  • Review vulnerability scanners for CVE-2022-50451 package-level detections.
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-2022-50451 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
LinuxLinux4534a70b7056fd4b9a1c6db5a4ce3c98546b291e, 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e, 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e, 4534a70b7056fd4b9a1c6db5a4ce3c98546b291eunaffected
LinuxLinux5.15, 0, 5.15.87, 6.0.17, 6.1.3, 6.2affected
Weakness

CWE details

No CWE listed

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