CVE-2022-50485
MediumIn 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)
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
3.10
and later are affected. Fixed in
5.4.229,
5.10.163,
5.15.87,
6.0.18,
6.1.4,
6.2
and their respective stable series.
References
6 total-
Patch
-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2022-50485?
CVE-2022-50485 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 3.10 onward and has been patched in 5.4.229, 5.10.163, 5.15.87 and others. CVE-2022-50485 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2022-50485?
CVE-2022-50485 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2022-50485?
Yes. CVE-2022-50485 has been patched. Fixed versions include 5.4.229, 5.10.163, 5.15.87 and others. If you are running Linux kernel 3.10 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-50485 actively exploited?
No. CVE-2022-50485 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.