{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50773 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50773 is a 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-50773 and fix it if it is affected.\n\nWhat it is: CVE-2022-50773 is a 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-50773 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-50773/ (Markdown: https://insights.sbomify.com/CVE-2022-50773/index.md)","id":"CVE-2022-50773","markdown":"https://insights.sbomify.com/CVE-2022-50773/index.md","name":"CVE-2022-50773","record":{"aliases":["DEBIAN-CVE-2022-50773","GHSA-cxg4-pr38-gg9p","UBUNTU-CVE-2022-50773"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A local attacker with high privileges can trigger a kernel null pointer dereference in the ALSA mts64 driver, causing a system crash.","user_interaction":"not_required","vuln_class":"null_dereference"},"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\nALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt\n\nI got a null-ptr-defer error report when I do the following tests\non the qemu platform:\n\nmake defconfig and CONFIG_PARPORT=m, CONFIG_PARPORT_PC=m,\nCONFIG_SND_MTS64=m\n\nThen making test scripts:\ncat\u003etest_mod1.sh\u003c\u003cEOF\nmodprobe snd-mts64\nmodprobe snd-mts64\nEOF\n\nExecuting the script, perhaps several times, we will get a null-ptr-defer\nreport, as follow:\n\nsyzkaller:~# ./test_mod.sh\nsnd_mts64: probe of snd_mts64.0 failed with error -5\nmodprobe: ERROR: could not insert 'snd_mts64': No such device\n BUG: kernel NULL pointer dereference, address: 0000000000000000\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 0 P4D 0\n Oops: 0002 [#1] PREEMPT SMP PTI\n CPU: 0 PID: 205 Comm: modprobe Not tainted 6.1.0-rc8-00588-g76dcd734eca2 #6\n Call Trace:\n  \u003cIRQ\u003e\n  snd_mts64_interrupt+0x24/0xa0 [snd_mts64]\n  parport_irq_handler+0x37/0x50 [parport]\n  __handle_irq_event_percpu+0x39/0x190\n  handle_irq_event_percpu+0xa/0x30\n  handle_irq_event+0x2f/0x50\n  handle_edge_irq+0x99/0x1b0\n  __common_interrupt+0x5d/0x100\n  common_interrupt+0xa0/0xc0\n  \u003c/IRQ\u003e\n  \u003cTASK\u003e\n  asm_common_interrupt+0x22/0x40\n RIP: 0010:_raw_write_unlock_irqrestore+0x11/0x30\n  parport_claim+0xbd/0x230 [parport]\n  snd_mts64_probe+0x14a/0x465 [snd_mts64]\n  platform_probe+0x3f/0xa0\n  really_probe+0x129/0x2c0\n  __driver_probe_device+0x6d/0xc0\n  driver_probe_device+0x1a/0xa0\n  __device_attach_driver+0x7a/0xb0\n  bus_for_each_drv+0x62/0xb0\n  __device_attach+0xe4/0x180\n  bus_probe_device+0x82/0xa0\n  device_add+0x550/0x920\n  platform_device_add+0x106/0x220\n  snd_mts64_attach+0x2e/0x80 [snd_mts64]\n  port_check+0x14/0x20 [parport]\n  bus_for_each_dev+0x6e/0xc0\n  __parport_register_driver+0x7c/0xb0 [parport]\n  snd_mts64_module_init+0x31/0x1000 [snd_mts64]\n  do_one_initcall+0x3c/0x1f0\n  do_init_module+0x46/0x1c6\n  load_module+0x1d8d/0x1e10\n  __do_sys_finit_module+0xa2/0xf0\n  do_syscall_64+0x37/0x90\n  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n  \u003c/TASK\u003e\n Kernel panic - not syncing: Fatal exception in interrupt\n Rebooting in 1 seconds..\n\nThe mts wa not initialized during interrupt,  we add check for\nmts to fix this bug.","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":"ALSA: mts64: fix possible null-ptr-defer in snd_mts64_interrupt","id":"CVE-2022-50773","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":9,"next":{"headline":"crypto: qat - fix DMA transfer direction","id":"CVE-2022-50774"},"packages":[],"prev":{"headline":"netdevsim: fix memory leak in nsim_bus_dev_new()","id":"CVE-2022-50772"},"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 local attacker with high privileges can trigger a kernel null pointer dereference in the ALSA mts64 driver, causing a system crash.","url":"https://insights.sbomify.com/CVE-2022-50773/"}