GHSA-JX9Q-5J85-6QHG

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:

media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()

KASAN reports a use-after-free: BUG: KASAN: use-after-free in dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] Call Trace: ... dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core] vidtv_bridge_probe+0x7bf/0xa40 [dvb_vidtv_bridge] platform_probe+0xb6/0x170 ... Allocated by task 1238: ... dvb_register_device+0x1a7/0xa70 [dvb_core] dvb_dmxdev_init+0x2af/0x4a0 [dvb_core] vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge] ... Freed by task 1238: dvb_register_device+0x6d2/0xa70 [dvb_core] dvb_dmxdev_init+0x2af/0x4a0 [dvb_core] vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge] ...

It is because the error handling in vidtv_bridge_dvb_init() is wrong.

First, vidtv_bridge_dmx(dev)_init() will clean themselves when fail, but goto fail_dmx(_dev): calls release functions again, which causes use-after-free.

Also, in fail_fe, fail_tuner_probe and fail_demod_probe, j = i will cause out-of-bound when i finished its loop (i == NUM_FE). And the loop releasing is wrong, although now NUM_FE is 1 so it won't cause problem.

Fix this by correctly releasing everything.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-50725"
  ],
  "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\nmedia: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()\n\nKASAN reports a use-after-free:\nBUG: KASAN: use-after-free in dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core]\nCall Trace:\n ...\n dvb_dmxdev_release+0x4d5/0x5d0 [dvb_core]\n vidtv_bridge_probe+0x7bf/0xa40 [dvb_vidtv_bridge]\n platform_probe+0xb6/0x170\n ...\nAllocated by task 1238:\n ...\n dvb_register_device+0x1a7/0xa70 [dvb_core]\n dvb_dmxdev_init+0x2af/0x4a0 [dvb_core]\n vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge]\n ...\nFreed by task 1238:\n dvb_register_device+0x6d2/0xa70 [dvb_core]\n dvb_dmxdev_init+0x2af/0x4a0 [dvb_core]\n vidtv_bridge_probe+0x766/0xa40 [dvb_vidtv_bridge]\n ...\n\nIt is because the error handling in vidtv_bridge_dvb_init() is wrong.\n\nFirst, vidtv_bridge_dmx(dev)_init() will clean themselves when fail, but\ngoto fail_dmx(_dev): calls release functions again, which causes\nuse-after-free.\n\nAlso, in fail_fe, fail_tuner_probe and fail_demod_probe, j = i will cause\nout-of-bound when i finished its loop (i == NUM_FE). And the loop\nreleasing is wrong, although now NUM_FE is 1 so it won\u0027t cause problem.\n\nFix this by correctly releasing everything.",
  "id": "GHSA-jx9q-5j85-6qhg",
  "modified": "2025-12-24T15:30:32Z",
  "published": "2025-12-24T15:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-50725"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0369af6fe33d4053899b121b32e91f870b2cf0ae"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/06398ce69571a43a8a0dd0f1bfe35d221f726a6a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8a204a0b4a0d105229735222c515759ea2b126c1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/ba8d9405935097e296bcf7a942c3a01df0edb865"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c290aa527fd832d278c6388a3ba53a9890fbd74a"
    }
  ],
  "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…