{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50743 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50743 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-50743 and fix it if it is affected.\n\nWhat it is: CVE-2022-50743 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-50743 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-50743/ (Markdown: https://insights.sbomify.com/CVE-2022-50743/index.md)","id":"CVE-2022-50743","markdown":"https://insights.sbomify.com/CVE-2022-50743/index.md","name":"CVE-2022-50743","record":{"aliases":["DEBIAN-CVE-2022-50743","GHSA-x7fv-mvjx-m6c8","UBUNTU-CVE-2022-50743"],"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":"none","summary":"A memory leak in the Linux kernel EROFS filesystem allows local attackers to cause a denial of service by triggering a specific block address condition.","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\nerofs: Fix pcluster memleak when its block address is zero\n\nsyzkaller reported a memleak:\nhttps://syzkaller.appspot.com/bug?id=62f37ff612f0021641eda5b17f056f1668aa9aed\n\nunreferenced object 0xffff88811009c7f8 (size 136):\n  ...\n  backtrace:\n    [\u003cffffffff821db19b\u003e] z_erofs_do_read_page+0x99b/0x1740\n    [\u003cffffffff821dee9e\u003e] z_erofs_readahead+0x24e/0x580\n    [\u003cffffffff814bc0d6\u003e] read_pages+0x86/0x3d0\n    ...\n\nsyzkaller constructed a case: in z_erofs_register_pcluster(),\nztailpacking = false and map-\u003em_pa = zero. This makes pcl-\u003eobj.index be\nzero although pcl is not a inline pcluster.\n\nThen following path adds refcount for grp, but the refcount won't be put\nbecause pcl is inline.\n\nz_erofs_readahead()\n  z_erofs_do_read_page() # for another page\n    z_erofs_collector_begin()\n      erofs_find_workgroup()\n        erofs_workgroup_get()\n\nSince it's illegal for the block address of a non-inlined pcluster to\nbe zero, add check here to avoid registering the pcluster which would\nbe leaked.","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":"erofs: Fix pcluster memleak when its block address is zero","id":"CVE-2022-50743","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs","id":"CVE-2022-50744"},"packages":[],"prev":{"headline":"misc: ocxl: fix possible refcount leak in afu_ioctl()","id":"CVE-2022-50742"},"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 EROFS filesystem allows local attackers to cause a denial of service by triggering a specific block address condition.","url":"https://insights.sbomify.com/CVE-2022-50743/"}