{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50770 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50770 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50770 and fix it if it is affected.\n\nWhat it is: CVE-2022-50770 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50770 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50770/ (Markdown: https://insights.sbomify.com/CVE-2022-50770/index.md)","id":"CVE-2022-50770","markdown":"https://insights.sbomify.com/CVE-2022-50770/index.md","name":"CVE-2022-50770","record":{"aliases":["DEBIAN-CVE-2022-50770","GHSA-5phr-qvw5-5rg9","UBUNTU-CVE-2022-50770"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel OCFS2 filesystem allows local attackers to cause denial of service by exhausting kernel memory during mount operations.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: fix memory leak in ocfs2_mount_volume()\n\nThere is a memory leak reported by kmemleak:\n\n  unreferenced object 0xffff88810cc65e60 (size 32):\n    comm \"mount.ocfs2\", pid 23753, jiffies 4302528942 (age 34735.105s)\n    hex dump (first 32 bytes):\n      10 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01  ................\n      01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 00  ................\n    backtrace:\n      [\u003cffffffff8170f73d\u003e] __kmalloc+0x4d/0x150\n      [\u003cffffffffa0ac3f51\u003e] ocfs2_compute_replay_slots+0x121/0x330 [ocfs2]\n      [\u003cffffffffa0b65165\u003e] ocfs2_check_volume+0x485/0x900 [ocfs2]\n      [\u003cffffffffa0b68129\u003e] ocfs2_mount_volume.isra.0+0x1e9/0x650 [ocfs2]\n      [\u003cffffffffa0b7160b\u003e] ocfs2_fill_super+0xe0b/0x1740 [ocfs2]\n      [\u003cffffffff818e1fe2\u003e] mount_bdev+0x312/0x400\n      [\u003cffffffff819a086d\u003e] legacy_get_tree+0xed/0x1d0\n      [\u003cffffffff818de82d\u003e] vfs_get_tree+0x7d/0x230\n      [\u003cffffffff81957f92\u003e] path_mount+0xd62/0x1760\n      [\u003cffffffff81958a5a\u003e] do_mount+0xca/0xe0\n      [\u003cffffffff81958d3c\u003e] __x64_sys_mount+0x12c/0x1a0\n      [\u003cffffffff82f26f15\u003e] do_syscall_64+0x35/0x80\n      [\u003cffffffff8300006a\u003e] entry_SYSCALL_64_after_hwframe+0x46/0xb0\n\nThis call stack is related to two problems.  Firstly, the ocfs2 super uses\n\"replay_map\" to trace online/offline slots, in order to recover offline\nslots during recovery and mount.  But when ocfs2_truncate_log_init()\nreturns an error in ocfs2_mount_volume(), the memory of \"replay_map\" will\nnot be freed in error handling path.  Secondly, the memory of \"replay_map\"\nwill not be freed if d_make_root() returns an error in ocfs2_fill_super().\nBut the memory of \"replay_map\" will be freed normally when completing\nrecovery and mount in ocfs2_complete_mount_recovery().\n\nFix the first problem by adding error handling path to free \"replay_map\"\nwhen ocfs2_truncate_log_init() fails.  And fix the second problem by\ncalling ocfs2_free_replay_slots(osb) in the error handling path\n\"out_dismount\".  In addition, since ocfs2_free_replay_slots() is static,\nit is necessary to remove its static attribute and declare it in header\nfile.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"ocfs2: fix memory leak in ocfs2_mount_volume()","id":"CVE-2022-50770","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"rcu: Fix __this_cpu_read() lockdep warning in rcu_force_quiescent_state()","id":"CVE-2022-50771"},"packages":[],"prev":{"headline":"mmc: mxcmmc: fix return value check of mmc_add_host()","id":"CVE-2022-50769"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel OCFS2 filesystem allows local attackers to cause denial of service by exhausting kernel memory during mount operations.","url":"https://insights.sbomify.com/CVE-2022-50770/"}