fkie_cve-2024-50214
Vulnerability from fkie_nvd
Published
2024-11-09 11:15
Modified
2024-11-13 17:25
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic() modprobe drm_connector_test and then rmmod drm_connector_test, the following memory leak occurs. The `mode` allocated in drm_mode_duplicate() called by drm_display_mode_from_cea_vic() is not freed, which cause the memory leak: unreferenced object 0xffffff80cb0ee400 (size 128): comm "kunit_try_catch", pid 1948, jiffies 4294950339 hex dump (first 32 bytes): 14 44 02 00 80 07 d8 07 04 08 98 08 00 00 38 04 .D............8. 3c 04 41 04 65 04 00 00 05 00 00 00 00 00 00 00 <.A.e........... backtrace (crc 90e9585c): [<00000000ec42e3d7>] kmemleak_alloc+0x34/0x40 [<00000000d0ef055a>] __kmalloc_cache_noprof+0x26c/0x2f4 [<00000000c2062161>] drm_mode_duplicate+0x44/0x19c [<00000000f96c74aa>] drm_display_mode_from_cea_vic+0x88/0x98 [<00000000d8f2c8b4>] 0xffffffdc982a4868 [<000000005d164dbc>] kunit_try_run_case+0x13c/0x3ac [<000000006fb23398>] kunit_generic_run_threadfn_adapter+0x80/0xec [<000000006ea56ca0>] kthread+0x2e8/0x374 [<000000000676063f>] ret_from_fork+0x10/0x20 ...... Free `mode` by using drm_kunit_display_mode_from_cea_vic() to fix it.
Impacted products



{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "386941FE-51A4-4893-9EC3-054AD3863E8D",
                     versionEndExcluding: "6.11.7",
                     versionStartIncluding: "6.11",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*",
                     matchCriteriaId: "7F361E1D-580F-4A2D-A509-7615F73167A1",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*",
                     matchCriteriaId: "925478D0-3E3D-4E6F-ACD5-09F28D5DF82C",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*",
                     matchCriteriaId: "3C95E234-D335-4B6C-96BF-E2CEBD8654ED",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*",
                     matchCriteriaId: "E0F717D8-3014-4F84-8086-0124B2111379",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*",
                     matchCriteriaId: "24DBE6C7-2AAE-4818-AED2-E131F153D2FA",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/connector: hdmi: Fix memory leak in drm_display_mode_from_cea_vic()\n\nmodprobe drm_connector_test and then rmmod drm_connector_test,\nthe following memory leak occurs.\n\nThe `mode` allocated in drm_mode_duplicate() called by\ndrm_display_mode_from_cea_vic() is not freed, which cause the memory leak:\n\n\tunreferenced object 0xffffff80cb0ee400 (size 128):\n\t  comm \"kunit_try_catch\", pid 1948, jiffies 4294950339\n\t  hex dump (first 32 bytes):\n\t    14 44 02 00 80 07 d8 07 04 08 98 08 00 00 38 04  .D............8.\n\t    3c 04 41 04 65 04 00 00 05 00 00 00 00 00 00 00  <.A.e...........\n\t  backtrace (crc 90e9585c):\n\t    [<00000000ec42e3d7>] kmemleak_alloc+0x34/0x40\n\t    [<00000000d0ef055a>] __kmalloc_cache_noprof+0x26c/0x2f4\n\t    [<00000000c2062161>] drm_mode_duplicate+0x44/0x19c\n\t    [<00000000f96c74aa>] drm_display_mode_from_cea_vic+0x88/0x98\n\t    [<00000000d8f2c8b4>] 0xffffffdc982a4868\n\t    [<000000005d164dbc>] kunit_try_run_case+0x13c/0x3ac\n\t    [<000000006fb23398>] kunit_generic_run_threadfn_adapter+0x80/0xec\n\t    [<000000006ea56ca0>] kthread+0x2e8/0x374\n\t    [<000000000676063f>] ret_from_fork+0x10/0x20\n\t......\n\nFree `mode` by using drm_kunit_display_mode_from_cea_vic()\nto fix it.",
      },
      {
         lang: "es",
         value: "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: drm/connector: hdmi: Se corrige la pérdida de memoria en drm_display_mode_from_cea_vic() modprobe drm_connector_test y luego rmmod drm_connector_test, se produce la siguiente pérdida de memoria. El `modo` asignado en drm_mode_duplicate() llamado por drm_display_mode_from_cea_vic() no se libera, lo que causa la pérdida de memoria: objeto sin referencia 0xffffff80cb0ee400 (tamaño 128): comm \"kunit_try_catch\", pid 1948, jiffies 4294950339 volcado hexadecimal (primeros 32 bytes): 14 44 02 00 80 07 d8 07 04 08 98 08 00 00 38 04 .D............8. 3c 04 41 04 65 04 00 00 05 00 00 00 00 00 00 00 &lt;.Ae.......... seguimiento inverso (crc 90e9585c): [&lt;00000000ec42e3d7&gt;] kmemleak_alloc+0x34/0x40 [&lt;00000000d0ef055a&gt;] __kmalloc_cache_noprof+0x26c/0x2f4 [&lt;00000000c2062161&gt;] drm_mode_duplicate+0x44/0x19c [&lt;00000000f96c74aa&gt;] drm_display_mode_from_cea_vic+0x88/0x98 [&lt;00000000d8f2c8b4&gt;] 0xffffffdc982a4868 [&lt;000000005d164dbc&gt;] kunit_try_run_case+0x13c/0x3ac [&lt;000000006fb23398&gt;] kunit_generic_run_threadfn_adapter+0x80/0xec [&lt;000000006ea56ca0&gt;] kthread+0x2e8/0x374 [&lt;000000000676063f&gt;] ret_from_fork+0x10/0x20 ...... Libere el `modo` usando drm_kunit_display_mode_from_cea_vic() para solucionarlo.",
      },
   ],
   id: "CVE-2024-50214",
   lastModified: "2024-11-13T17:25:55.197",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "LOCAL",
               availabilityImpact: "HIGH",
               baseScore: 5.5,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
               version: "3.1",
            },
            exploitabilityScore: 1.8,
            impactScore: 3.6,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-11-09T11:15:06.777",
   references: [
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/926163342a2e7595d950e84c17c693b1272bd491",
      },
      {
         source: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
         tags: [
            "Patch",
         ],
         url: "https://git.kernel.org/stable/c/df2b00685cd33cd85be8910c7d6d22c4ebbf18bb",
      },
   ],
   sourceIdentifier: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-401",
            },
         ],
         source: "nvd@nist.gov",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.