ghsa-9vc2-g7hx-x44h
Vulnerability from github
Published
2025-10-22 15:31
Modified
2025-10-22 15:31
Details

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

media: max9286: Fix memleak in max9286_v4l2_register()

There is a kmemleak when testing the media/i2c/max9286.c with bpf mock device:

kmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

unreferenced object 0xffff88810defc400 (size 256): comm "python3", pid 278, jiffies 4294737563 (age 31.978s) hex dump (first 32 bytes): 28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff (........."..... 10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff ................ backtrace: [<00000000191de6a7>] __kmalloc_node+0x44/0x1b0 [<000000002f4912b7>] kvmalloc_node+0x34/0x180 [<0000000057dc4cae>] v4l2_ctrl_new+0x325/0x10f0 [videodev] [<0000000026030272>] v4l2_ctrl_new_std+0x16f/0x210 [videodev] [<00000000f0d9ea2f>] max9286_probe+0x76e/0xbff [max9286] [<00000000ea8f6455>] i2c_device_probe+0x28d/0x680 [<0000000087529af3>] really_probe+0x17c/0x3f0 [<00000000b08be526>] __driver_probe_device+0xe3/0x170 [<000000004382edea>] driver_probe_device+0x49/0x120 [<000000007bde528a>] __device_attach_driver+0xf7/0x150 [<000000009f9c6ab4>] bus_for_each_drv+0x114/0x180 [<00000000c8aaf588>] __device_attach+0x1e5/0x2d0 [<0000000041cc06b9>] bus_probe_device+0x126/0x140 [<000000002309860d>] device_add+0x810/0x1130 [<000000002827bf98>] i2c_new_client_device+0x359/0x4f0 [<00000000593bdc85>] of_i2c_register_device+0xf1/0x110

max9286_v4l2_register() calls v4l2_ctrl_new_std(), but won't free the created v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which causes the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2023-53700"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-22T14:15:44Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: max9286: Fix memleak in max9286_v4l2_register()\n\nThere is a kmemleak when testing the media/i2c/max9286.c with bpf mock\ndevice:\n\nkmemleak: 5 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\nunreferenced object 0xffff88810defc400 (size 256):\n  comm \"python3\", pid 278, jiffies 4294737563 (age 31.978s)\n  hex dump (first 32 bytes):\n    28 06 a7 0a 81 88 ff ff 00 fe 22 12 81 88 ff ff  (.........\".....\n    10 c4 ef 0d 81 88 ff ff 10 c4 ef 0d 81 88 ff ff  ................\n  backtrace:\n    [\u003c00000000191de6a7\u003e] __kmalloc_node+0x44/0x1b0\n    [\u003c000000002f4912b7\u003e] kvmalloc_node+0x34/0x180\n    [\u003c0000000057dc4cae\u003e] v4l2_ctrl_new+0x325/0x10f0 [videodev]\n    [\u003c0000000026030272\u003e] v4l2_ctrl_new_std+0x16f/0x210 [videodev]\n    [\u003c00000000f0d9ea2f\u003e] max9286_probe+0x76e/0xbff [max9286]\n    [\u003c00000000ea8f6455\u003e] i2c_device_probe+0x28d/0x680\n    [\u003c0000000087529af3\u003e] really_probe+0x17c/0x3f0\n    [\u003c00000000b08be526\u003e] __driver_probe_device+0xe3/0x170\n    [\u003c000000004382edea\u003e] driver_probe_device+0x49/0x120\n    [\u003c000000007bde528a\u003e] __device_attach_driver+0xf7/0x150\n    [\u003c000000009f9c6ab4\u003e] bus_for_each_drv+0x114/0x180\n    [\u003c00000000c8aaf588\u003e] __device_attach+0x1e5/0x2d0\n    [\u003c0000000041cc06b9\u003e] bus_probe_device+0x126/0x140\n    [\u003c000000002309860d\u003e] device_add+0x810/0x1130\n    [\u003c000000002827bf98\u003e] i2c_new_client_device+0x359/0x4f0\n    [\u003c00000000593bdc85\u003e] of_i2c_register_device+0xf1/0x110\n\nmax9286_v4l2_register() calls v4l2_ctrl_new_std(), but won\u0027t free the\ncreated v412_ctrl when fwnode_graph_get_endpoint_by_id() failed, which\ncauses the memleak. Call v4l2_ctrl_handler_free() to free the v412_ctrl.",
  "id": "GHSA-9vc2-g7hx-x44h",
  "modified": "2025-10-22T15:31:10Z",
  "published": "2025-10-22T15:31:10Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53700"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/505ff3a0c5951684c3a43094ca4c1a74683d5681"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5897fe3ebe8252993579e1bee715ebfe5504e052"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/5e31213fa017c20ccc989033a5f4a626473aa2ca"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/724039e013b34f46344abdbf8c74e6a65a828327"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8636c5fc7658c7c6299fb8b352d24ea4b9ba99e2"
    }
  ],
  "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 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.


Loading…

Loading…