{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50578 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50578 is a memory corruption vulnerability in Linux, published on 22 Oct 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-50578 and fix it if it is affected.\n\nWhat it is: CVE-2022-50578 is a memory corruption vulnerability in Linux, published on 22 Oct 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-50578 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-50578/ (Markdown: https://insights.sbomify.com/CVE-2022-50578/index.md)","id":"CVE-2022-50578","markdown":"https://insights.sbomify.com/CVE-2022-50578/index.md","name":"CVE-2022-50578","record":{"aliases":["DEBIAN-CVE-2022-50578","GHSA-x9pw-p3r7-mr43","UBUNTU-CVE-2022-50578"],"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 class registration allows local attackers to cause 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\nclass: fix possible memory leak in __class_register()\n\nIf class_add_groups() returns error, the 'cp-\u003esubsys' need be\nunregister, and the 'cp' need be freed.\n\nWe can not call kset_unregister() here, because the 'cls' will\nbe freed in callback function class_release() and it's also\nfreed in caller's error path, it will cause double free.\n\nSo fix this by calling kobject_del() and kfree_const(name) to\ncleanup kobject. Besides, call kfree() to free the 'cp'.\n\nFault injection test can trigger this:\n\nunreferenced object 0xffff888102fa8190 (size 8):\n  comm \"modprobe\", pid 502, jiffies 4294906074 (age 49.296s)\n  hex dump (first 8 bytes):\n    70 6b 74 63 64 76 64 00                          pktcdvd.\n  backtrace:\n    [\u003c00000000e7c7703d\u003e] __kmalloc_track_caller+0x1ae/0x320\n    [\u003c000000005e4d70bc\u003e] kstrdup+0x3a/0x70\n    [\u003c00000000c2e5e85a\u003e] kstrdup_const+0x68/0x80\n    [\u003c000000000049a8c7\u003e] kvasprintf_const+0x10b/0x190\n    [\u003c0000000029123163\u003e] kobject_set_name_vargs+0x56/0x150\n    [\u003c00000000747219c9\u003e] kobject_set_name+0xab/0xe0\n    [\u003c0000000005f1ea4e\u003e] __class_register+0x15c/0x49a\n\nunreferenced object 0xffff888037274000 (size 1024):\n  comm \"modprobe\", pid 502, jiffies 4294906074 (age 49.296s)\n  hex dump (first 32 bytes):\n    00 40 27 37 80 88 ff ff 00 40 27 37 80 88 ff ff  .@'7.....@'7....\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n  backtrace:\n    [\u003c00000000151f9600\u003e] kmem_cache_alloc_trace+0x17c/0x2f0\n    [\u003c00000000ecf3dd95\u003e] __class_register+0x86/0x49a","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":"class: fix possible memory leak in __class_register()","id":"CVE-2022-50578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":8,"next":{"headline":"arm64: ftrace: fix module PLTs with mcount","id":"CVE-2022-50579"},"packages":[],"prev":{"headline":"ima: Fix memory leak in __ima_inode_hash()","id":"CVE-2022-50577"},"products":["Linux"],"published":"2025-10-22","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 class registration allows local attackers to cause resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50578/"}