fkie_cve-2022-49784
Vulnerability from fkie_nvd
Published
2025-05-01 15:16
Modified
2025-05-02 13:53
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: perf/x86/amd/uncore: Fix memory leak for events array When a CPU comes online, the per-CPU NB and LLC uncore contexts are freed but not the events array within the context structure. This causes a memory leak as identified by the kmemleak detector. [...] unreferenced object 0xffff8c5944b8e320 (size 32): comm "swapper/0", pid 1, jiffies 4294670387 (age 151.072s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<000000000759fb79>] amd_uncore_cpu_up_prepare+0xaf/0x230 [<00000000ddc9e126>] cpuhp_invoke_callback+0x2cf/0x470 [<0000000093e727d4>] cpuhp_issue_call+0x14d/0x170 [<0000000045464d54>] __cpuhp_setup_state_cpuslocked+0x11e/0x330 [<0000000069f67cbd>] __cpuhp_setup_state+0x6b/0x110 [<0000000015365e0f>] amd_uncore_init+0x260/0x321 [<00000000089152d2>] do_one_initcall+0x3f/0x1f0 [<000000002d0bd18d>] kernel_init_freeable+0x1ca/0x212 [<0000000030be8dde>] kernel_init+0x11/0x120 [<0000000059709e59>] ret_from_fork+0x22/0x30 unreferenced object 0xffff8c5944b8dd40 (size 64): comm "swapper/0", pid 1, jiffies 4294670387 (age 151.072s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<00000000306efe8b>] amd_uncore_cpu_up_prepare+0x183/0x230 [<00000000ddc9e126>] cpuhp_invoke_callback+0x2cf/0x470 [<0000000093e727d4>] cpuhp_issue_call+0x14d/0x170 [<0000000045464d54>] __cpuhp_setup_state_cpuslocked+0x11e/0x330 [<0000000069f67cbd>] __cpuhp_setup_state+0x6b/0x110 [<0000000015365e0f>] amd_uncore_init+0x260/0x321 [<00000000089152d2>] do_one_initcall+0x3f/0x1f0 [<000000002d0bd18d>] kernel_init_freeable+0x1ca/0x212 [<0000000030be8dde>] kernel_init+0x11/0x120 [<0000000059709e59>] ret_from_fork+0x22/0x30 [...] Fix the problem by freeing the events array before freeing the uncore context.
Impacted products
Vendor Product Version



{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: perf/x86/amd/uncore: Se corrige una fuga de memoria en la matriz de eventos. Cuando una CPU se conecta, se liberan los contextos de n\u00facleo \u00fanico (NB) y LLC por CPU, pero no la matriz de eventos dentro de la estructura del contexto. Esto provoca una fuga de memoria, identificada por el detector kmemleak. [...] objeto sin referencia 0xffff8c5944b8e320 (tama\u00f1o 32): comm \"swapper/0\", pid 1, jiffies 4294670387 (edad 151.072s) volcado hexadecimal (primeros 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [\u0026lt;000000000759fb79\u0026gt;] amd_uncore_cpu_up_prepare+0xaf/0x230 [\u0026lt;00000000ddc9e126\u0026gt;] cpuhp_invoke_callback+0x2cf/0x470 [\u0026lt;0000000093e727d4\u0026gt;] cpuhp_issue_call+0x14d/0x170 [\u0026lt;0000000045464d54\u0026gt;] __cpuhp_setup_state_cpuslocked+0x11e/0x330 [\u0026lt;0000000069f67cbd\u0026gt;] __cpuhp_setup_state+0x6b/0x110 [\u0026lt;0000000015365e0f\u0026gt;] amd_uncore_init+0x260/0x321 [\u0026lt;00000000089152d2\u0026gt;] do_one_initcall+0x3f/0x1f0 [\u0026lt;000000002d0bd18d\u0026gt;] kernel_init_freeable+0x1ca/0x212 [\u0026lt;0000000030be8dde\u0026gt;] kernel_init+0x11/0x120 [\u0026lt;0000000059709e59\u0026gt;] ret_from_fork+0x22/0x30 objeto sin referencia 0xffff8c5944b8dd40 (tama\u00f1o 64): comm \"swapper/0\", pid 1, jiffies 4294670387 (edad 151.072s) volcado hexadecimal (primeros 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ seguimiento inverso: [\u0026lt;00000000306efe8b\u0026gt;] preparaci\u00f3n de CPU activada de AMD sin n\u00facleo + 0x183/0x230 [\u0026lt;00000000ddc9e126\u0026gt;] devoluci\u00f3n de llamada de invocaci\u00f3n de CPUHp + 0x2cf/0x470 [\u0026lt;0000000093e727d4\u0026gt;] llamada de emisi\u00f3n de CPUHp + 0x14d/0x170 [\u0026lt;0000000045464d54\u0026gt;] estado de configuraci\u00f3n de CPUHp bloqueado + 0x11e/0x330 [\u0026lt;0000000069f67cbd\u0026gt;] __cpuhp_setup_state+0x6b/0x110 [\u0026lt;0000000015365e0f\u0026gt;] amd_uncore_init+0x260/0x321 [\u0026lt;00000000089152d2\u0026gt;] do_one_initcall+0x3f/0x1f0 [\u0026lt;000000002d0bd18d\u0026gt;] kernel_init_freeable+0x1ca/0x212 [\u0026lt;0000000030be8dde\u0026gt;] kernel_init+0x11/0x120 [\u0026lt;0000000059709e59\u0026gt;] ret_from_fork+0x22/0x30 [...] Solucione el problema liberando la matriz de eventos antes de liberar el contexto uncore."
    }
  ],
  "id": "CVE-2022-49784",
  "lastModified": "2025-05-02T13:53:20.943",
  "metrics": {},
  "published": "2025-05-01T15:16:01.610",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/bdfe34597139cfcecd47a2eb97fea44d77157491"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/f75be9885d49e3717de962345c4572ddab52b178"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…