Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50367

fs: fix UAF/GPF bug in nilfs_mdt_destroy

High7.8EPSS 0.22%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: fs: fix UAF/GPF bug in nilfs_mdt_destroy In alloc_inode, inode_init_always() could return -ENOMEM if security_inode_alloc() fails, which causes inode->i_private uninitialized. Then nilfs_is_metadata_file_inode() returns true and nilfs_free_inode() wrongly calls nilfs_mdt_destroy(), which frees the uninitialized inode->i_private and leads to crashes(e.g., UAF/GPF). Fix this by moving security_inode_alloc just prior to this_cpu_inc(nr_inodes)

Scores

CVSS scores of CVE-2022-50367, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA-ADPADP (enrichment)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (5 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Weakness

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d1ff475d7c83289d0a7faef346ea3bbf90818bad
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c0aa76b0f17f59dd9c9d3463550a2986a1d592e4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < ec2aab115eb38ac4992ea2fcc2a02fbe7af5cf48
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 70e4f70d54e0225f91814e8610477d65f33cefe4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 1e555c3ed1fce4b278aaebe18a64a934cece57d8
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 64b79e632869ad3ef6c098a4731d559381da1115
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 81de80330fa6907aec32eb54c5619059e6e36452
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2a96b532098284ecf8e4849b8b9e5fc7a28bdee9
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 2e488f13755ffbb60f307e991b27024716a33b29
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.9.331 – ≤ 4.9.*
    • unaffected 4.14.296 – ≤ 4.14.*
    • unaffected 4.19.262 – ≤ 4.19.*
    • unaffected 5.4.218 – ≤ 5.4.*
    • unaffected 5.10.148 – ≤ 5.10.*
    • unaffected 5.15.73 – ≤ 5.15.*
    • unaffected 5.19.15 – ≤ 5.19.*
    • unaffected 6.0.1 – ≤ 6.0.*
    • unaffected 6.1 – ≤ *

References (9)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50367 badge
[![CVE-2022-50367](https://trackcve.app/badge/CVE-2022-50367.svg)](https://trackcve.app/cve/CVE-2022-50367)

Record last updated .