Skip to content
TrackCVE
  • 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-50485

ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode

Medium5.5EPSS 0.17%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode There are many places that will get unhappy (and crash) when ext4_iget() returns a bad inode. However, if iget the boot loader inode, allows a bad inode to be returned, because the inode may not be initialized. This mechanism can be used to bypass some checks and cause panic. To solve this problem, we add a special iget flag EXT4_IGET_BAD. Only with this flag we'd be returning bad inode from ext4_iget(), otherwise we always return the error code if the inode is bad inode.(suggested by Jan Kara)

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-50485, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (7 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < 2142dfa1de61e25b83198af0308ec7689cca25d3
    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5
    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < f7e6b5548f915d7aa435d0764d41eacfb49c6e09
    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < f725b290ed79ad61e4f721fee95a287892d8b1ad
    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < 488a5c2bf7543c3cd3f07a025f2e62be91599430
    • affected 393d1d1d76933886d5e1ce603214c9987589c6d5 – < 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.4.229 – ≤ 5.4.*
    • unaffected 5.10.163 – ≤ 5.10.*
    • unaffected 5.15.87 – ≤ 5.15.*
    • unaffected 6.0.18 – ≤ 6.0.*
    • unaffected 6.1.4 – ≤ 6.1.*
    • unaffected 6.2 – ≤ *

References (6)

Sources

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

Badge for a README or a ticket

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

Record last updated .