GHSA-8G4H-M7M7-62X8

Vulnerability from github – Published: 2025-09-17 15:30 – Updated: 2025-12-11 15:30
VLAI
Details

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

media: ov2740: Fix memleak in ov2740_init_controls()

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

unreferenced object 0xffff8881090e19e0 (size 16): comm "51-i2c-ov2740", pid 278, jiffies 4294781584 (age 23.613s) hex dump (first 16 bytes): 00 f3 7c 0b 81 88 ff ff 80 75 6a 09 81 88 ff ff ..|......uj..... backtrace: [<000000004e9fad8f>] __kmalloc_node+0x44/0x1b0 [<0000000039c802f4>] kvmalloc_node+0x34/0x180 [<000000009b8b5c63>] v4l2_ctrl_handler_init_class+0x11d/0x180 [videodev] [<0000000038644056>] ov2740_probe+0x37d/0x84f [ov2740] [<0000000092489f59>] i2c_device_probe+0x28d/0x680 [<000000001038babe>] really_probe+0x17c/0x3f0 [<0000000098c7af1c>] __driver_probe_device+0xe3/0x170 [<00000000e1b3dc24>] device_driver_attach+0x34/0x80 [<000000005a04a34d>] bind_store+0x10b/0x1a0 [<00000000ce25d4f2>] drv_attr_store+0x49/0x70 [<000000007d9f4e9a>] sysfs_kf_write+0x8c/0xb0 [<00000000be6cff0f>] kernfs_fop_write_iter+0x216/0x2e0 [<0000000031ddb40a>] vfs_write+0x658/0x810 [<0000000041beecdd>] ksys_write+0xd6/0x1b0 [<0000000023755840>] do_syscall_64+0x38/0x90 [<00000000b2cc2da2>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

ov2740_init_controls() won't clean all the allocated resources in fail path, which may causes the memleaks. Add v4l2_ctrl_handler_free() to prevent memleak.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-53349"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-401"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-09-17T15:15:38Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: ov2740: Fix memleak in ov2740_init_controls()\n\nThere is a kmemleak when testing the media/i2c/ov2740.c with bpf mock\ndevice:\n\nunreferenced object 0xffff8881090e19e0 (size 16):\n  comm \"51-i2c-ov2740\", pid 278, jiffies 4294781584 (age 23.613s)\n  hex dump (first 16 bytes):\n    00 f3 7c 0b 81 88 ff ff 80 75 6a 09 81 88 ff ff  ..|......uj.....\n  backtrace:\n    [\u003c000000004e9fad8f\u003e] __kmalloc_node+0x44/0x1b0\n    [\u003c0000000039c802f4\u003e] kvmalloc_node+0x34/0x180\n    [\u003c000000009b8b5c63\u003e] v4l2_ctrl_handler_init_class+0x11d/0x180\n[videodev]\n    [\u003c0000000038644056\u003e] ov2740_probe+0x37d/0x84f [ov2740]\n    [\u003c0000000092489f59\u003e] i2c_device_probe+0x28d/0x680\n    [\u003c000000001038babe\u003e] really_probe+0x17c/0x3f0\n    [\u003c0000000098c7af1c\u003e] __driver_probe_device+0xe3/0x170\n    [\u003c00000000e1b3dc24\u003e] device_driver_attach+0x34/0x80\n    [\u003c000000005a04a34d\u003e] bind_store+0x10b/0x1a0\n    [\u003c00000000ce25d4f2\u003e] drv_attr_store+0x49/0x70\n    [\u003c000000007d9f4e9a\u003e] sysfs_kf_write+0x8c/0xb0\n    [\u003c00000000be6cff0f\u003e] kernfs_fop_write_iter+0x216/0x2e0\n    [\u003c0000000031ddb40a\u003e] vfs_write+0x658/0x810\n    [\u003c0000000041beecdd\u003e] ksys_write+0xd6/0x1b0\n    [\u003c0000000023755840\u003e] do_syscall_64+0x38/0x90\n    [\u003c00000000b2cc2da2\u003e] entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nov2740_init_controls() won\u0027t clean all the allocated resources in fail\npath, which may causes the memleaks. Add v4l2_ctrl_handler_free() to\nprevent memleak.",
  "id": "GHSA-8g4h-m7m7-62x8",
  "modified": "2025-12-11T15:30:29Z",
  "published": "2025-09-17T15:30:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53349"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2d899592ed7829d0d5140853bac4d58742a6b8af"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3969b2ebc66039306f505c7c630c5530800f83c0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7c405ee63447f14eefcfe12a18aa749abbd596ea"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a163ee11345d8322321c28bd61631de32455b987"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/fc33380ae06f438b652f66b9370b543976ac8a03"
    }
  ],
  "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.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.