{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50084 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-50084 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 Oct 2024. 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-2024-50084 and fix it if it is affected.\n\nWhat it is: CVE-2024-50084 is a high-severity memory corruption vulnerability in Linux kernel, published on 29 Oct 2024. 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-2024-50084 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-2024-50084/ (Markdown: https://insights.sbomify.com/CVE-2024-50084/index.md)","id":"CVE-2024-50084","markdown":"https://insights.sbomify.com/CVE-2024-50084/index.md","name":"CVE-2024-50084","record":{"aliases":["AZL-51945","BELL-CVE-2024-50084","DEBIAN-CVE-2024-50084","GHSA-p346-px87-vf2h","UBUNTU-CVE-2024-50084"],"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's Microchip VCAP API test function 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":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"},{"id":"CWE-416","name":"Use After Free"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()\n\nCommit a3c1e45156ad (\"net: microchip: vcap: Fix use-after-free error in\nkunit test\") fixed the use-after-free error, but introduced below\nmemory leaks by removing necessary vcap_free_rule(), add it to fix it.\n\n\tunreferenced object 0xffffff80ca58b700 (size 192):\n\t  comm \"kunit_try_catch\", pid 1215, jiffies 4294898264\n\t  hex dump (first 32 bytes):\n\t    00 12 7a 00 05 00 00 00 0a 00 00 00 64 00 00 00  ..z.........d...\n\t    00 00 00 00 00 00 00 00 00 04 0b cc 80 ff ff ff  ................\n\t  backtrace (crc 9c09c3fe):\n\t    [\u003c0000000052a0be73\u003e] kmemleak_alloc+0x34/0x40\n\t    [\u003c0000000043605459\u003e] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [\u003c0000000040a01b8d\u003e] vcap_alloc_rule+0x3cc/0x9c4\n\t    [\u003c000000003fe86110\u003e] vcap_api_encode_rule_test+0x1ac/0x16b0\n\t    [\u003c00000000b3595fc4\u003e] kunit_try_run_case+0x13c/0x3ac\n\t    [\u003c0000000010f5d2bf\u003e] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u003c00000000c5d82c9a\u003e] kthread+0x2e8/0x374\n\t    [\u003c00000000f4287308\u003e] ret_from_fork+0x10/0x20\n\tunreferenced object 0xffffff80cc0b0400 (size 64):\n\t  comm \"kunit_try_catch\", pid 1215, jiffies 4294898265\n\t  hex dump (first 32 bytes):\n\t    80 04 0b cc 80 ff ff ff 18 b7 58 ca 80 ff ff ff  ..........X.....\n\t    39 00 00 00 02 00 00 00 06 05 04 03 02 01 ff ff  9...............\n\t  backtrace (crc daf014e9):\n\t    [\u003c0000000052a0be73\u003e] kmemleak_alloc+0x34/0x40\n\t    [\u003c0000000043605459\u003e] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [\u003c000000000ff63fd4\u003e] vcap_rule_add_key+0x2cc/0x528\n\t    [\u003c00000000dfdb1e81\u003e] vcap_api_encode_rule_test+0x224/0x16b0\n\t    [\u003c00000000b3595fc4\u003e] kunit_try_run_case+0x13c/0x3ac\n\t    [\u003c0000000010f5d2bf\u003e] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u003c00000000c5d82c9a\u003e] kthread+0x2e8/0x374\n\t    [\u003c00000000f4287308\u003e] ret_from_fork+0x10/0x20\n\tunreferenced object 0xffffff80cc0b0700 (size 64):\n\t  comm \"kunit_try_catch\", pid 1215, jiffies 4294898265\n\t  hex dump (first 32 bytes):\n\t    80 07 0b cc 80 ff ff ff 28 b7 58 ca 80 ff ff ff  ........(.X.....\n\t    3c 00 00 00 00 00 00 00 01 2f 03 b3 ec ff ff ff  \u003c......../......\n\t  backtrace (crc 8d877792):\n\t    [\u003c0000000052a0be73\u003e] kmemleak_alloc+0x34/0x40\n\t    [\u003c0000000043605459\u003e] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [\u003c000000006eadfab7\u003e] vcap_rule_add_action+0x2d0/0x52c\n\t    [\u003c00000000323475d1\u003e] vcap_api_encode_rule_test+0x4d4/0x16b0\n\t    [\u003c00000000b3595fc4\u003e] kunit_try_run_case+0x13c/0x3ac\n\t    [\u003c0000000010f5d2bf\u003e] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u003c00000000c5d82c9a\u003e] kthread+0x2e8/0x374\n\t    [\u003c00000000f4287308\u003e] ret_from_fork+0x10/0x20\n\tunreferenced object 0xffffff80cc0b0900 (size 64):\n\t  comm \"kunit_try_catch\", pid 1215, jiffies 4294898266\n\t  hex dump (first 32 bytes):\n\t    80 09 0b cc 80 ff ff ff 80 06 0b cc 80 ff ff ff  ................\n\t    7d 00 00 00 01 00 00 00 00 00 00 00 ff 00 00 00  }...............\n\t  backtrace (crc 34181e56):\n\t    [\u003c0000000052a0be73\u003e] kmemleak_alloc+0x34/0x40\n\t    [\u003c0000000043605459\u003e] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [\u003c000000000ff63fd4\u003e] vcap_rule_add_key+0x2cc/0x528\n\t    [\u003c00000000991e3564\u003e] vcap_val_rule+0xcf0/0x13e8\n\t    [\u003c00000000fc9868e5\u003e] vcap_api_encode_rule_test+0x678/0x16b0\n\t    [\u003c00000000b3595fc4\u003e] kunit_try_run_case+0x13c/0x3ac\n\t    [\u003c0000000010f5d2bf\u003e] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [\u003c00000000c5d82c9a\u003e] kthread+0x2e8/0x374\n\t    [\u003c00000000f4287308\u003e] ret_from_fork+0x10/0x20\n\tunreferenced object 0xffffff80cc0b0980 (size 64):\n\t  comm \"kunit_try_catch\", pid 1215, jiffies 4294898266\n\t  hex dump (first 32 bytes):\n\t    18 b7 58 ca 80 ff ff ff 00 09 0b cc 80 ff ff ff  ..X.............\n\t    67 00 00 00 00 00 00 00 01 01 74 88 c0 ff ff ff  g.........t.....\n\t  backtrace (crc 275fd9be):\n\t    [\u003c0000000052a0be73\u003e] kmemleak_alloc+0x34/0x40\n\t    [\u003c0000000043605459\u003e] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [\u003c000000000ff63fd4\u003e] vcap_rule_add_key+0x2cc/0x528\n\t    [\u003c000000001396a1a2\u003e] test_add_de\n---truncated---","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":"net: microchip: vcap api: Fix memory leaks in vcap_api_encode_rule_test()","id":"CVE-2024-50084","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"mptcp: pm: fix UaF read in mptcp_pm_nl_rm_addr_or_subflow","id":"CVE-2024-50085"},"packages":[],"prev":{"headline":"tcp: fix mptcp DSS corruption due to large pmtu xmit","id":"CVE-2024-50083"},"products":["Linux"],"published":"2024-10-29","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's Microchip VCAP API test function can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2024-50084/"}