ghsa-94m8-5mhq-ph6m
Vulnerability from github
Published
2024-10-21 15:32
Modified
2024-10-22 18:32
Details

In the Linux kernel, the following vulnerability has been resolved:

nvdimm: Fix devs leaks in scan_labels()

scan_labels() leaks memory when label scanning fails and it falls back to just creating a default "seed" namespace for userspace to configure. Root can force the kernel to leak memory.

Allocate the minimum resources unconditionally and release them when unneeded to avoid the memory leak.

A kmemleak reports: unreferenced object 0xffff88800dda1980 (size 16): comm "kworker/u10:5", pid 69, jiffies 4294671781 hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 0): [<00000000c5dea560>] __kmalloc+0x32c/0x470 [<000000009ed43c83>] nd_region_register_namespaces+0x6fb/0x1120 [libnvdimm] [<000000000e07a65c>] nd_region_probe+0xfe/0x210 [libnvdimm] [<000000007b79ce5f>] nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm] [<00000000a5f3da2e>] really_probe+0xc6/0x390 [<00000000129e2a69>] __driver_probe_device+0x78/0x150 [<000000002dfed28b>] driver_probe_device+0x1e/0x90 [<00000000e7048de2>] __device_attach_driver+0x85/0x110 [<0000000032dca295>] bus_for_each_drv+0x85/0xe0 [<00000000391c5a7d>] __device_attach+0xbe/0x1e0 [<0000000026dabec0>] bus_probe_device+0x94/0xb0 [<00000000c590d936>] device_add+0x656/0x870 [<000000003d69bfaa>] nd_async_device_register+0xe/0x50 [libnvdimm] [<000000003f4c52a4>] async_run_entry_fn+0x2e/0x110 [<00000000e201f4b0>] process_one_work+0x1ee/0x600 [<000000006d90d5a9>] worker_thread+0x183/0x350

Show details on source website


{
   affected: [],
   aliases: [
      "CVE-2024-47755",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-401",
      ],
      github_reviewed: false,
      github_reviewed_at: null,
      nvd_published_at: "2024-10-21T13:15:05Z",
      severity: "MODERATE",
   },
   details: "In the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm: Fix devs leaks in scan_labels()\n\nscan_labels() leaks memory when label scanning fails and it falls back\nto just creating a default \"seed\" namespace for userspace to configure.\nRoot can force the kernel to leak memory.\n\nAllocate the minimum resources unconditionally and release them when\nunneeded to avoid the memory leak.\n\nA kmemleak reports:\nunreferenced object 0xffff88800dda1980 (size 16):\n  comm \"kworker/u10:5\", pid 69, jiffies 4294671781\n  hex dump (first 16 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace (crc 0):\n    [<00000000c5dea560>] __kmalloc+0x32c/0x470\n    [<000000009ed43c83>] nd_region_register_namespaces+0x6fb/0x1120 [libnvdimm]\n    [<000000000e07a65c>] nd_region_probe+0xfe/0x210 [libnvdimm]\n    [<000000007b79ce5f>] nvdimm_bus_probe+0x7a/0x1e0 [libnvdimm]\n    [<00000000a5f3da2e>] really_probe+0xc6/0x390\n    [<00000000129e2a69>] __driver_probe_device+0x78/0x150\n    [<000000002dfed28b>] driver_probe_device+0x1e/0x90\n    [<00000000e7048de2>] __device_attach_driver+0x85/0x110\n    [<0000000032dca295>] bus_for_each_drv+0x85/0xe0\n    [<00000000391c5a7d>] __device_attach+0xbe/0x1e0\n    [<0000000026dabec0>] bus_probe_device+0x94/0xb0\n    [<00000000c590d936>] device_add+0x656/0x870\n    [<000000003d69bfaa>] nd_async_device_register+0xe/0x50 [libnvdimm]\n    [<000000003f4c52a4>] async_run_entry_fn+0x2e/0x110\n    [<00000000e201f4b0>] process_one_work+0x1ee/0x600\n    [<000000006d90d5a9>] worker_thread+0x183/0x350",
   id: "GHSA-94m8-5mhq-ph6m",
   modified: "2024-10-22T18:32:10Z",
   published: "2024-10-21T15:32:27Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2024-47755",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/18a672c62d735744c6340eb3f5e58934a5d34cf2",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/45db20bdb5695d06478d35e05fb2550441bed890",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/62c2aa6b1f565d2fc1ec11a6e9e8336ce37a6426",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/939053737edb49ba5bdc5846acb45f11d15b7ab4",
      },
      {
         type: "WEB",
         url: "https://git.kernel.org/stable/c/cdf0dfb3d183bbe0d0b6a6622c53d105074ad384",
      },
   ],
   schema_version: "1.4.0",
   severity: [
      {
         score: "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
         type: "CVSS_V3",
      },
   ],
}


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.