CVE-2022-50436: ext4: don't set up encryption key during jbd2 transaction
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.10% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1ba993208bcfd691e241483420a2a761d3f15750, 206dd3acfb9bca54a25b228c7c7c2257eedde09b, 23ad034760dd38e12b0e0e1b28b9629f330810a1.
Low priority for now. Upgrade to Linux Linux 1ba993208bcfd691e241483420a2a761d3f15750, 206dd3acfb9bca54a25b228c7c7c2257eedde09b, 23ad034760dd38e12b0e0e1b28b9629f330810a1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
22
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- a80f7fcf18672ae4971a6b713b58c0d389aa99fe and later · before 23ad034760dd38e12b0e0e1b28b9629f330810a1affected · git
- a80f7fcf18672ae4971a6b713b58c0d389aa99fe and later · before 6220ec405571ded17efedc56587190b542adf246affected · git
- a80f7fcf18672ae4971a6b713b58c0d389aa99fe and later · before 206dd3acfb9bca54a25b228c7c7c2257eedde09baffected · git
- a80f7fcf18672ae4971a6b713b58c0d389aa99fe and later · before 1ba993208bcfd691e241483420a2a761d3f15750affected · git
- a80f7fcf18672ae4971a6b713b58c0d389aa99fe and later · before 4c0d5778385cb3618ff26a561ce41de2b7d9de70affected · git
- before 5.10not affected · semver
- 5.10.163 and later · up to and including 5.10.*not affected · semver
- 5.15.87 and later · up to and including 5.15.*not affected · semver
- 6.0.18 and later · up to and including 6.0.*not affected · semver
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.10.1 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.87
- linux linux kernel5.16 and later · before 6.0.18
- linux linux kernel6.1 and later · before 6.1.4
- linux linux kernel5.10
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-39921Oct 1, 2025 · spi: microchip-core-qspi: stop checking viability of op->max_freq in supports_op callback22Monitor
- ← EarlierCVE-2025-39922Oct 1, 2025 · ixgbe: fix incorrect map used in eee linkmode28Monitor
- Later →CVE-2025-39923Oct 1, 2025 · dmaengine: qcom: bam_dma: Fix DT error handling for num-channels/ees22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1ba993208bcfd691e241483420a2a761d3f15750 | Vendor (CNA) |
| Linux Linux | 206dd3acfb9bca54a25b228c7c7c2257eedde09b | Vendor (CNA) |
| Linux Linux | 23ad034760dd38e12b0e0e1b28b9629f330810a1 | Vendor (CNA) |
| Linux Linux | 4c0d5778385cb3618ff26a561ce41de2b7d9de70 | Vendor (CNA) |
| Linux Linux | 6220ec405571ded17efedc56587190b542adf246 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.