Bug 2400725 (CVE-2022-50436) - CVE-2022-50436 kernel: ext4: don't set up encryption key during jbd2 transaction
Summary: CVE-2022-50436 kernel: ext4: don't set up encryption key during jbd2 transaction
Keywords:
Status: NEW
Alias: CVE-2022-50436
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-01 12:03 UTC by OSIDB Bzimport
Modified: 2025-10-25 21:22 UTC (History)
0 users

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-10-01 12:03:43 UTC
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.


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