{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-49784 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-49784 is a medium-severity memory corruption vulnerability in Linux kernel, published on 1 May 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-49784 and fix it if it is affected.\n\nWhat it is: CVE-2022-49784 is a medium-severity memory corruption vulnerability in Linux kernel, published on 1 May 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-49784 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-2022-49784/ (Markdown: https://insights.sbomify.com/CVE-2022-49784/index.md)","id":"CVE-2022-49784","markdown":"https://insights.sbomify.com/CVE-2022-49784/index.md","name":"CVE-2022-49784","record":{"aliases":["DEBIAN-CVE-2022-49784","GHSA-m6c5-jhrw-6658","UBUNTU-CVE-2022-49784"],"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 AMD uncore performance monitoring driver 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":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/amd/uncore: Fix memory leak for events array\n\nWhen a CPU comes online, the per-CPU NB and LLC uncore contexts are\nfreed but not the events array within the context structure. This\ncauses a memory leak as identified by the kmemleak detector.\n\n  [...]\n  unreferenced object 0xffff8c5944b8e320 (size 32):\n    comm \"swapper/0\", pid 1, jiffies 4294670387 (age 151.072s)\n    hex dump (first 32 bytes):\n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    backtrace:\n      [\u003c000000000759fb79\u003e] amd_uncore_cpu_up_prepare+0xaf/0x230\n      [\u003c00000000ddc9e126\u003e] cpuhp_invoke_callback+0x2cf/0x470\n      [\u003c0000000093e727d4\u003e] cpuhp_issue_call+0x14d/0x170\n      [\u003c0000000045464d54\u003e] __cpuhp_setup_state_cpuslocked+0x11e/0x330\n      [\u003c0000000069f67cbd\u003e] __cpuhp_setup_state+0x6b/0x110\n      [\u003c0000000015365e0f\u003e] amd_uncore_init+0x260/0x321\n      [\u003c00000000089152d2\u003e] do_one_initcall+0x3f/0x1f0\n      [\u003c000000002d0bd18d\u003e] kernel_init_freeable+0x1ca/0x212\n      [\u003c0000000030be8dde\u003e] kernel_init+0x11/0x120\n      [\u003c0000000059709e59\u003e] ret_from_fork+0x22/0x30\n  unreferenced object 0xffff8c5944b8dd40 (size 64):\n    comm \"swapper/0\", pid 1, jiffies 4294670387 (age 151.072s)\n    hex dump (first 32 bytes):\n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n      00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    backtrace:\n      [\u003c00000000306efe8b\u003e] amd_uncore_cpu_up_prepare+0x183/0x230\n      [\u003c00000000ddc9e126\u003e] cpuhp_invoke_callback+0x2cf/0x470\n      [\u003c0000000093e727d4\u003e] cpuhp_issue_call+0x14d/0x170\n      [\u003c0000000045464d54\u003e] __cpuhp_setup_state_cpuslocked+0x11e/0x330\n      [\u003c0000000069f67cbd\u003e] __cpuhp_setup_state+0x6b/0x110\n      [\u003c0000000015365e0f\u003e] amd_uncore_init+0x260/0x321\n      [\u003c00000000089152d2\u003e] do_one_initcall+0x3f/0x1f0\n      [\u003c000000002d0bd18d\u003e] kernel_init_freeable+0x1ca/0x212\n      [\u003c0000000030be8dde\u003e] kernel_init+0x11/0x120\n      [\u003c0000000059709e59\u003e] ret_from_fork+0x22/0x30\n  [...]\n\nFix the problem by freeing the events array before freeing the uncore\ncontext.","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":"perf/x86/amd/uncore: Fix memory leak for events array","id":"CVE-2022-49784","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"x86/sgx: Add overflow check in sgx_validate_offset_length()","id":"CVE-2022-49785"},"packages":[],"prev":{"headline":"x86/fpu: Drop fpregs lock before inheriting FPU permissions","id":"CVE-2022-49783"},"products":["Linux"],"published":"2025-05-01","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's AMD uncore performance monitoring driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-49784/"}