CVE-2022-50485
Last modified
CVE-2022-50485 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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)
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 3.10, < 5.4.229 |
| Linux | Linux Kernel | >= 5.5, < 5.10.163 |
| Linux | Linux Kernel | >= 5.11, < 5.15.87 |
| Linux | Linux Kernel | >= 5.16, < 6.0.18 |
| Linux | Linux Kernel | >= 6.1, < 6.1.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2022-50485?
How severe is CVE-2022-50485?
How do I fix CVE-2022-50485?
Are you affected by CVE-2022-50485?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
