Bug 2401531 (CVE-2022-50485) - CVE-2022-50485 kernel: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
Summary: CVE-2022-50485 kernel: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad...
Keywords:
Status: NEW
Alias: CVE-2022-50485
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-04 16:05 UTC by OSIDB Bzimport
Modified: 2025-10-10 11:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-04 16:05:53 UTC
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)


Note You need to log in before you can comment on or make changes to this bug.