CVE-2022-50770: ocfs2: fix memory leak in ocfs2_mount_volume()
Noroxi assessment
Priority: Monitor (action score 0/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.25% (FIRST EPSS).
- Fixed version: Linux Linux 2b7e59ed2e77136e9360274f8f0fc208a003e95c, 4efe1d2db731bad19891e2fb9b338724b1f598cc, 50ab0ca3aff4da26037113d69f5a756d8c1a92cd.
Low priority for now. Upgrade to Linux Linux 2b7e59ed2e77136e9360274f8f0fc208a003e95c, 4efe1d2db731bad19891e2fb9b338724b1f598cc, 50ab0ca3aff4da26037113d69f5a756d8c1a92cd 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: ocfs2: fix memory leak in ocfs2_mount_volume() There is a memory leak reported by kmemleak: unreferenced object 0xffff88810cc65e60 (size 32): comm "mount.ocfs2", pid 23753, jiffies 4302528942 (age 34735.105s) hex dump (first 32 bytes): 10 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01 ................ 01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff8170f73d>] __kmalloc+0x4d/0x150 [<ffffffffa0ac3f51>] ocfs2_compute_replay_slots+0x121/0x330 [ocfs2] [<ffffffffa0b65165>] ocfs2_check_volume+0x485/0x900 [ocfs2] [<ffffffffa0b68129>] ocfs2_mount_volume.isra.0+0x1e9/0x650 [ocfs2] [<ffffffffa0b7160b>] ocfs2_fill_super+0xe0b/0x1740 [ocfs2] [<ffffffff818e1fe2>] mount_bdev+0x312/0x400 [<ffffffff819a086d>] legacy_get_tree+0xed/0x1d0 [<ffffffff818de82d>] vfs_get_tree+0x7d/0x230 [<ffffffff81957f92>] path_mount+0xd62/0x1760 [<ffffffff81958a5a>] do_mount+0xca/0xe0 [<ffffffff81958d3c>] __x64_sys_mount+0x12c/0x1a0 [<ffffffff82f26f15>] do_syscall_64+0x35/0x80 [<ffffffff8300006a>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 This call stack is related to two problems. Firstly, the ocfs2 super uses "replay_map" to trace online/offline slots, in order to recover offline slots during recovery and mount. But when ocfs2_truncate_log_init() returns an error in ocfs2_mount_volume(), the memory of "replay_map" will not be freed in error handling path. Secondly, the memory of "replay_map" will not be freed if d_make_root() returns an error in ocfs2_fill_super(). But the memory of "replay_map" will be freed normally when completing recovery and mount in ocfs2_complete_mount_recovery(). Fix the first problem by adding error handling path to free "replay_map" when ocfs2_truncate_log_init() fails. And fix the second problem by calling ocfs2_free_replay_slots(osb) in the error handling path "out_dismount". In addition, since ocfs2_free_replay_slots() is static, it is necessary to remove its static attribute and declare it in header file.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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.
—
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
- 2.6.30affected
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before 7ef516888c4d30ae41bfcd79e7077d86d92794c5affected · git
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before 2b7e59ed2e77136e9360274f8f0fc208a003e95caffected · git
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before 8059e200259e9c483d715fc2df6340c227c3e196affected · git
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before 4efe1d2db731bad19891e2fb9b338724b1f598ccaffected · git
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before 50ab0ca3aff4da26037113d69f5a756d8c1a92cdaffected · git
- 9140db04ef185f934acf2b1b15b3dd5e6a6bfc22 and later · before ce2fcf1516d674a174d9b34d1e1024d64de9fba3affected · git
- before 2.6.30not affected · semver
- 5.4.229 and later · up to and including 5.4.*not affected · semver
- 5.10.163 and later · up to and including 5.10.*not affected · semver
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 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kernel-default | before 4.12.14-122.293.1 | 4.12.14-122.293.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_77 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-source | before 4.12.14-122.293.1 | 4.12.14-122.293.1 |
| SUSE:Linux Enterprise Server 12 SP5-LTSS | kernel-syms | before 4.12.14-122.293.1 | 4.12.14-122.293.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50768Dec 24, 2025 · scsi: smartpqi: Correct device removal for multi-actuator devices0Monitor
- ← EarlierCVE-2022-50769Dec 24, 2025 · mmc: mxcmmc: fix return value check of mmc_add_host()0Monitor
- Later →CVE-2022-50771Dec 24, 2025 · rcu: Fix __this_cpu_read() lockdep warning in rcu_force_quiescent_state()0Monitor
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 | 2b7e59ed2e77136e9360274f8f0fc208a003e95c | Vendor (CNA) |
| Linux Linux | 4efe1d2db731bad19891e2fb9b338724b1f598cc | Vendor (CNA) |
| Linux Linux | 50ab0ca3aff4da26037113d69f5a756d8c1a92cd | Vendor (CNA) |
| Linux Linux | 7ef516888c4d30ae41bfcd79e7077d86d92794c5 | Vendor (CNA) |
| Linux Linux | 8059e200259e9c483d715fc2df6340c227c3e196 | Vendor (CNA) |
| Linux Linux | ce2fcf1516d674a174d9b34d1e1024d64de9fba3 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.293.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.293.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.293.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_77 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | 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.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4efe1d2db731bad19891e2fb9b338724b1f598cc
- git.kernel.org/stable/c/50ab0ca3aff4da26037113d69f5a756d8c1a92cd
- git.kernel.org/stable/c/7ef516888c4d30ae41bfcd79e7077d86d92794c5
- git.kernel.org/stable/c/8059e200259e9c483d715fc2df6340c227c3e196
- git.kernel.org/stable/c/ce2fcf1516d674a174d9b34d1e1024d64de9fba3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.