CVE-2022-50436
published 2025-10-01CVE-2022-50436: In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.10%
0.8th percentile
In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set up encryption key during jbd2 transaction
Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature")
extended the scope of the transaction in ext4_unlink() too far, making
it include the call to ext4_find_entry(). However, ext4_find_entry()
can deadlock when called from within a transaction because it may need
to set up the directory's encryption key.
Fix this by restoring the transaction to its original scope.
Affected
16 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 | >= a80f7fcf18672ae4971a6b713b58c0d389aa99fe < 23ad034760dd38e12b0e0e1b28b9629f330810a1 | 23ad034760dd38e12b0e0e1b28b9629f330810a1 |
| linux | linux | >= a80f7fcf18672ae4971a6b713b58c0d389aa99fe < 6220ec405571ded17efedc56587190b542adf246 | 6220ec405571ded17efedc56587190b542adf246 |
| linux | linux | >= a80f7fcf18672ae4971a6b713b58c0d389aa99fe < 206dd3acfb9bca54a25b228c7c7c2257eedde09b | 206dd3acfb9bca54a25b228c7c7c2257eedde09b |
| linux | linux | >= a80f7fcf18672ae4971a6b713b58c0d389aa99fe < 1ba993208bcfd691e241483420a2a761d3f15750 | 1ba993208bcfd691e241483420a2a761d3f15750 |
| linux | linux | >= a80f7fcf18672ae4971a6b713b58c0d389aa99fe < 4c0d5778385cb3618ff26a561ce41de2b7d9de70 | 4c0d5778385cb3618ff26a561ce41de2b7d9de70 |
| linux | linux_kernel | — | — |
| 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 | >= 5.10.1 < 5.10.163 | 5.10.163 |
| 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 | >= 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: don't set up encryption key during jbd2 transaction
vendor_redhat·2025-10-01·CVSS 5.5
CVE-2022-50436 [MEDIUM] CWE-833 kernel: ext4: don't set up encryption key during jbd2 transaction
kernel: ext4: don't set up encryption key during jbd2 transaction
In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set up encryption key during jbd2 transaction
Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature")
extended the scope of the transaction in ext4_unlink() too far, making
it include the call to ext4_find_entry(). However, ext4_find_entry()
can deadlock when called from within a transaction because it may need
to set up the directory's encryption key.
Fix this by restoring the transaction to its original scope.
A flaw exists in the ext4 filesystem implementation in the Linux kernel such that the function ext4_unlink() extended a journaling transaction too far so that it included a call to ext4_find_entry(). However, ext4_find_
Debian
CVE-2022-50436: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: don't...
vendor_debian·2022·CVSS 5.5
CVE-2022-50436 [MEDIUM] CVE-2022-50436: linux - In the Linux kernel, the following vulnerability has been resolved: ext4: don't...
In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature") extended the scope of the transaction in ext4_unlink() too far, making it include the call to ext4_find_entry(). However, ext4_find_entry() can deadlock when called from within a transaction because it may need to set up the directory's encryption key. Fix this by restoring the transaction to its original scope.
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: resolved (fixed in 6.1.4-1)
OSV
CVE-2022-50436: In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ex
osv·2025-10-01·CVSS 5.5
CVE-2022-50436 [MEDIUM] CVE-2022-50436: In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ex
In the Linux kernel, the following vulnerability has been resolved: ext4: don't set up encryption key during jbd2 transaction Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature") extended the scope of the transaction in ext4_unlink() too far, making it include the call to ext4_find_entry(). However, ext4_find_entry() can deadlock when called from within a transaction because it may need to set up the directory's encryption key. Fix this by restoring the transaction to its original scope.
GHSA
GHSA-h235-mqh4-6cp2: In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set up encryption key during jbd2 transaction
Commit a80f7fcf1867 ("
ghsa_unreviewed·2025-10-01
CVE-2022-50436 [MEDIUM] GHSA-h235-mqh4-6cp2: In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set up encryption key during jbd2 transaction
Commit a80f7fcf1867 ("
In the Linux kernel, the following vulnerability has been resolved:
ext4: don't set up encryption key during jbd2 transaction
Commit a80f7fcf1867 ("ext4: fixup ext4_fc_track_* functions' signature")
extended the scope of the transaction in ext4_unlink() too far, making
it include the call to ext4_find_entry(). However, ext4_find_entry()
can deadlock when called from within a transaction because it may need
to set up the directory's encryption key.
Fix this by restoring the transaction to its original scope.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/1ba993208bcfd691e241483420a2a761d3f15750https://git.kernel.org/stable/c/206dd3acfb9bca54a25b228c7c7c2257eedde09bhttps://git.kernel.org/stable/c/23ad034760dd38e12b0e0e1b28b9629f330810a1https://git.kernel.org/stable/c/4c0d5778385cb3618ff26a561ce41de2b7d9de70https://git.kernel.org/stable/c/6220ec405571ded17efedc56587190b542adf246
2025-10-01
Published