GHSA-976X-8GHM-5PQ3

Vulnerability from github – Published: 2025-12-24 15:30 – Updated: 2025-12-24 15:30
VLAI?
Details

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

scsi: efct: Fix possible memleak in efct_device_init()

In efct_device_init(), when efct_scsi_reg_fc_transport() fails, efct_scsi_tgt_driver_exit() is not called to release memory for efct_scsi_tgt_driver_init() and causes memleak:

unreferenced object 0xffff8881020ce000 (size 2048): comm "modprobe", pid 465, jiffies 4294928222 (age 55.872s) backtrace: [<0000000021a1ef1b>] kmalloc_trace+0x27/0x110 [<000000004c3ed51c>] target_register_template+0x4fd/0x7b0 [target_core_mod] [<00000000f3393296>] efct_scsi_tgt_driver_init+0x18/0x50 [efct] [<00000000115de533>] 0xffffffffc0d90011 [<00000000d608f646>] do_one_initcall+0xd0/0x4e0 [<0000000067828cf1>] do_init_module+0x1cc/0x6a0 ...

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-50727"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-24T13:15:59Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: efct: Fix possible memleak in efct_device_init()\n\nIn efct_device_init(), when efct_scsi_reg_fc_transport() fails,\nefct_scsi_tgt_driver_exit() is not called to release memory for\nefct_scsi_tgt_driver_init() and causes memleak:\n\nunreferenced object 0xffff8881020ce000 (size 2048):\n  comm \"modprobe\", pid 465, jiffies 4294928222 (age 55.872s)\n  backtrace:\n    [\u003c0000000021a1ef1b\u003e] kmalloc_trace+0x27/0x110\n    [\u003c000000004c3ed51c\u003e] target_register_template+0x4fd/0x7b0 [target_core_mod]\n    [\u003c00000000f3393296\u003e] efct_scsi_tgt_driver_init+0x18/0x50 [efct]\n    [\u003c00000000115de533\u003e] 0xffffffffc0d90011\n    [\u003c00000000d608f646\u003e] do_one_initcall+0xd0/0x4e0\n    [\u003c0000000067828cf1\u003e] do_init_module+0x1cc/0x6a0\n    ...",
  "id": "GHSA-976x-8ghm-5pq3",
  "modified": "2025-12-24T15:30:32Z",
  "published": "2025-12-24T15:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50727"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/038359eeccffaf0de4c1c9c51ee19cc5649619a1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0c6e6bb30229b1297ac0fd7ede2941d2322fc736"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bb0cd225dd37df1f4a22e36dad59ff33178ecdfc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c7e96168a8ca3be96c4959475164bef31115f07e"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…