fkie_cve-2022-50500
Vulnerability from fkie_nvd
Published
2025-10-04 16:15
Modified
2025-10-06 14:56
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: netdevsim: fix memory leak in nsim_drv_probe() when nsim_dev_resources_register() failed If some items in nsim_dev_resources_register() fail, memory leak will occur. The following is the memory leak information. unreferenced object 0xffff888074c02600 (size 128): comm "echo", pid 8159, jiffies 4294945184 (age 493.530s) hex dump (first 32 bytes): 40 47 ea 89 ff ff ff ff 01 00 00 00 00 00 00 00 @G.............. ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ backtrace: [<0000000011a31c98>] kmalloc_trace+0x22/0x60 [<0000000027384c69>] devl_resource_register+0x144/0x4e0 [<00000000a16db248>] nsim_drv_probe+0x37a/0x1260 [<000000007d1f448c>] really_probe+0x20b/0xb10 [<00000000c416848a>] __driver_probe_device+0x1b3/0x4a0 [<00000000077e0351>] driver_probe_device+0x49/0x140 [<0000000054f2465a>] __device_attach_driver+0x18c/0x2a0 [<000000008538f359>] bus_for_each_drv+0x151/0x1d0 [<0000000038e09747>] __device_attach+0x1c9/0x4e0 [<00000000dd86e533>] bus_probe_device+0x1d5/0x280 [<00000000839bea35>] device_add+0xae0/0x1cb0 [<000000009c2abf46>] new_device_store+0x3b6/0x5f0 [<00000000fb823d7f>] bus_attr_store+0x72/0xa0 [<000000007acc4295>] sysfs_kf_write+0x106/0x160 [<000000005f50cb4d>] kernfs_fop_write_iter+0x3a8/0x5a0 [<0000000075eb41bf>] vfs_write+0x8f0/0xc80
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6b1da9f7126f05e857da6db24c6a04aa7974d644
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/7c4957fe40e2a628b7cceaf4c9bfb5b701774d05
Impacted products
Vendor Product Version


To clipboard 

{
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnetdevsim: fix memory leak in nsim_drv_probe() when nsim_dev_resources_register() failed\n\nIf some items in nsim_dev_resources_register() fail, memory leak will\noccur. The following is the memory leak information.\n\nunreferenced object 0xffff888074c02600 (size 128):\n  comm \"echo\", pid 8159, jiffies 4294945184 (age 493.530s)\n  hex dump (first 32 bytes):\n    40 47 ea 89 ff ff ff ff 01 00 00 00 00 00 00 00  @G..............\n    ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff  ................\n  backtrace:\n    [\u003c0000000011a31c98\u003e] kmalloc_trace+0x22/0x60\n    [\u003c0000000027384c69\u003e] devl_resource_register+0x144/0x4e0\n    [\u003c00000000a16db248\u003e] nsim_drv_probe+0x37a/0x1260\n    [\u003c000000007d1f448c\u003e] really_probe+0x20b/0xb10\n    [\u003c00000000c416848a\u003e] __driver_probe_device+0x1b3/0x4a0\n    [\u003c00000000077e0351\u003e] driver_probe_device+0x49/0x140\n    [\u003c0000000054f2465a\u003e] __device_attach_driver+0x18c/0x2a0\n    [\u003c000000008538f359\u003e] bus_for_each_drv+0x151/0x1d0\n    [\u003c0000000038e09747\u003e] __device_attach+0x1c9/0x4e0\n    [\u003c00000000dd86e533\u003e] bus_probe_device+0x1d5/0x280\n    [\u003c00000000839bea35\u003e] device_add+0xae0/0x1cb0\n    [\u003c000000009c2abf46\u003e] new_device_store+0x3b6/0x5f0\n    [\u003c00000000fb823d7f\u003e] bus_attr_store+0x72/0xa0\n    [\u003c000000007acc4295\u003e] sysfs_kf_write+0x106/0x160\n    [\u003c000000005f50cb4d\u003e] kernfs_fop_write_iter+0x3a8/0x5a0\n    [\u003c0000000075eb41bf\u003e] vfs_write+0x8f0/0xc80"
    }
  ],
  "id": "CVE-2022-50500",
  "lastModified": "2025-10-06T14:56:21.733",
  "metrics": {},
  "published": "2025-10-04T16:15:47.153",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/6b1da9f7126f05e857da6db24c6a04aa7974d644"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7c4957fe40e2a628b7cceaf4c9bfb5b701774d05"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Awaiting Analysis"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.