{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50675 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50675 is a memory corruption vulnerability in Linux, published on 9 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50675 and fix it if it is affected.\n\nWhat it is: CVE-2022-50675 is a memory corruption vulnerability in Linux, published on 9 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50675 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-50675/ (Markdown: https://insights.sbomify.com/CVE-2022-50675/index.md)","id":"CVE-2022-50675","markdown":"https://insights.sbomify.com/CVE-2022-50675/index.md","name":"CVE-2022-50675","record":{"aliases":["DEBIAN-CVE-2022-50675","GHSA-cvq8-ghfq-j2cg","UBUNTU-CVE-2022-50675"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A Linux kernel bug in ARM64 MTE handling causes KASAN access faults and potential crashes when tags are incorrectly set on untagged pages.","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\narm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored\n\nPrior to commit 69e3b846d8a7 (\"arm64: mte: Sync tags for pages where PTE\nis untagged\"), mte_sync_tags() was only called for pte_tagged() entries\n(those mapped with PROT_MTE). Therefore mte_sync_tags() could safely use\ntest_and_set_bit(PG_mte_tagged, \u0026page-\u003eflags) without inadvertently\nsetting PG_mte_tagged on an untagged page.\n\nThe above commit was required as guests may enable MTE without any\ncontrol at the stage 2 mapping, nor a PROT_MTE mapping in the VMM.\nHowever, the side-effect was that any page with a PTE that looked like\nswap (or migration) was getting PG_mte_tagged set automatically. A\nsubsequent page copy (e.g. migration) copied the tags to the destination\npage even if the tags were owned by KASAN.\n\nThis issue was masked by the page_kasan_tag_reset() call introduced in\ncommit e5b8d9218951 (\"arm64: mte: reset the page tag in page-\u003eflags\").\nWhen this commit was reverted (20794545c146), KASAN started reporting\naccess faults because the overriding tags in a page did not match the\noriginal page-\u003eflags (with CONFIG_KASAN_HW_TAGS=y):\n\n  BUG: KASAN: invalid-access in copy_page+0x10/0xd0 arch/arm64/lib/copy_page.S:26\n  Read at addr f5ff000017f2e000 by task syz-executor.1/2218\n  Pointer tag: [f5], memory tag: [f2]\n\nMove the PG_mte_tagged bit setting from mte_sync_tags() to the actual\nplace where tags are cleared (mte_sync_page_tags()) or restored\n(mte_restore_tags()).","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":"arm64: mte: Avoid setting PG_mte_tagged if no tags cleared or restored","id":"CVE-2022-50675","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":"net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks()","id":"CVE-2022-50676"},"packages":[],"prev":{"headline":"riscv: vdso: fix NULL deference in vdso_join_timens() when vfork","id":"CVE-2022-50674"},"products":["Linux"],"published":"2025-12-09","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 Linux kernel bug in ARM64 MTE handling causes KASAN access faults and potential crashes when tags are incorrectly set on untagged pages.","url":"https://insights.sbomify.com/CVE-2022-50675/"}