{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50748 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50748 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-50748 and fix it if it is affected.\n\nWhat it is: CVE-2022-50748 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-50748 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-50748/ (Markdown: https://insights.sbomify.com/CVE-2022-50748/index.md)","id":"CVE-2022-50748","markdown":"https://insights.sbomify.com/CVE-2022-50748/index.md","name":"CVE-2022-50748","record":{"aliases":["DEBIAN-CVE-2022-50748","GHSA-28q7-rjgm-6w8f","ROOT-OS-UBUNTU-2204-CVE-2022-50748","UBUNTU-CVE-2022-50748"],"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's mqueue initialization can lead to resource exhaustion and denial of service.","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\nipc: mqueue: fix possible memory leak in init_mqueue_fs()\n\ncommit db7cfc380900 (\"ipc: Free mq_sysctls if ipc namespace creation\nfailed\")\n\nHere's a similar memory leak to the one fixed by the patch above.\nretire_mq_sysctls need to be called when init_mqueue_fs fails after\nsetup_mq_sysctls.","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":"ipc: mqueue: fix possible memory leak in init_mqueue_fs()","id":"CVE-2022-50748","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":"acct: fix potential integer overflow in encode_comp_t()","id":"CVE-2022-50749"},"packages":[],"prev":{"headline":"hfs: Fix OOB Write in hfs_asc2mac","id":"CVE-2022-50747"},"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's mqueue initialization can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50748/"}