CVE-2022-50485
published 2025-10-04CVE-2022-50485: 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…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.16%
5.4th percentile
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)
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 2142dfa1de61e25b83198af0308ec7689cca25d3 | 2142dfa1de61e25b83198af0308ec7689cca25d3 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5 | c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < f7e6b5548f915d7aa435d0764d41eacfb49c6e09 | f7e6b5548f915d7aa435d0764d41eacfb49c6e09 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < f725b290ed79ad61e4f721fee95a287892d8b1ad | f725b290ed79ad61e4f721fee95a287892d8b1ad |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 488a5c2bf7543c3cd3f07a025f2e62be91599430 | 488a5c2bf7543c3cd3f07a025f2e62be91599430 |
| linux | linux | >= 393d1d1d76933886d5e1ce603214c9987589c6d5 < 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023 | 63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023 |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 3.10 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 5.11 < 5.15.87 | 5.15.87 |
| linux | linux_kernel | >= 5.16 < 6.0.18 | 6.0.18 |
| linux | linux_kernel | >= 5.5 < 5.10.163 | 5.10.163 |
| linux | linux_kernel | >= 6.1 < 6.1.4 | 6.1.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
vendor_redhat·2025-10-04·CVSS 5.5
CVE-2022-50485 [MEDIUM] CWE-654 kernel: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
kernel: ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
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)
Package: kernel (Red Hat Enterprise Linux 10) - Not affected
Package: kernel (Red Hat Enterprise Li
Debian
CVE-2022-50485: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: add E...
vendor_debian·2022·CVSS 5.5
CVE-2022-50485 [MEDIUM] CVE-2022-50485: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: add E...
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)
Scope: local
bookworm: resolved (fixed in 6.1.4-1)
bullseye: resolved (fixed in 5.10.178-1)
forky: resolved (fixed in 6.1.4-1)
sid: resolved (fixed in 6.1.4-1)
trixie: res
GHSA
GHSA-7gg4-pr88-8256: In the Linux kernel, the following vulnerability has been resolved:
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
There are many plac
ghsa_unreviewed·2025-10-04
CVE-2022-50485 [MEDIUM] GHSA-7gg4-pr88-8256: In the Linux kernel, the following vulnerability has been resolved:
ext4: add EXT4_IGET_BAD flag to prevent unexpected bad inode
There are many plac
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)
OSV
CVE-2022-50485: 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
osv·2025-10-04·CVSS 5.5
CVE-2022-50485 [MEDIUM] CVE-2022-50485: 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
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)
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2142dfa1de61e25b83198af0308ec7689cca25d3https://git.kernel.org/stable/c/488a5c2bf7543c3cd3f07a025f2e62be91599430https://git.kernel.org/stable/c/63b1e9bccb71fe7d7e3ddc9877dbdc85e5d2d023https://git.kernel.org/stable/c/c0a738875c2e9c8c3366d792f8bf7fe508d5e5a5https://git.kernel.org/stable/c/f725b290ed79ad61e4f721fee95a287892d8b1adhttps://git.kernel.org/stable/c/f7e6b5548f915d7aa435d0764d41eacfb49c6e09
2025-10-04
Published