# ext4: don't set up encryption key during jbd2 transaction

CVE record · `CVE-2022-50436`

- **Identifiers:** `CVE-2022-50436`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 Oct 2025
- **Updated:** 11 May 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 Oct 2025, 11:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `a80f7fcf18672ae4971a6b713b58c0d389aa99fe to before 23ad034760dd38e12b0e0e1b28b9629f330810a1` (git)
  - affected: `a80f7fcf18672ae4971a6b713b58c0d389aa99fe to before 6220ec405571ded17efedc56587190b542adf246` (git)
  - affected: `a80f7fcf18672ae4971a6b713b58c0d389aa99fe to before 206dd3acfb9bca54a25b228c7c7c2257eedde09b` (git)
  - affected: `a80f7fcf18672ae4971a6b713b58c0d389aa99fe to before 1ba993208bcfd691e241483420a2a761d3f15750` (git)
  - affected: `a80f7fcf18672ae4971a6b713b58c0d389aa99fe to before 4c0d5778385cb3618ff26a561ce41de2b7d9de70` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.10`
  - unaffected: `before 5.10` (semver)
  - unaffected: `5.10.163 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.87 to 5.15.*, inclusive` (semver)
  - unaffected: `6.0.18 to 6.0.*, inclusive` (semver)
  - unaffected: `6.1.4 to 6.1.*, inclusive` (semver)
  - unaffected: `6.2 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0010, the 1st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 1 Oct 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2022-50436](https://www.cve.org/CVERecord?id=CVE-2022-50436)
- [NVD: CVE-2022-50436](https://nvd.nist.gov/vuln/detail/CVE-2022-50436)

### References from the CNA

- <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>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2022-50436>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2022-50436/>. Everything for agents: <https://agentprime.io/llms.txt>.
