GHSA-QJW7-WGFM-9FRQ

Vulnerability from github – Published: 2026-05-06 12:30 – Updated: 2026-05-11 21:31
VLAI?
Details

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

media: v4l2-async: Fix error handling on steps after finding a match

Once an async connection is found to be matching with an fwnode, a sub-device may be registered (in case it wasn't already), its bound operation is called, ancillary links are created, the async connection is added to the sub-device's list of connections and removed from the global waiting connection list. Further on, the sub-device's possible own notifier is searched for possible additional matches.

Fix these specific issues:

  • If v4l2_async_match_notify() failed before the sub-notifier handling, the async connection was unbound and its entry removed from the sub-device's async connection list. The latter part was also done in v4l2_async_match_notify().

  • The async connection's sd field was only set after creating ancillary links in v4l2_async_match_notify(). It was however dereferenced in v4l2_async_unbind_subdev_one(), which was called on error path of v4l2_async_match_notify() failure.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-43189"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-06T12:16:37Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: v4l2-async: Fix error handling on steps after finding a match\n\nOnce an async connection is found to be matching with an fwnode, a\nsub-device may be registered (in case it wasn\u0027t already), its bound\noperation is called, ancillary links are created, the async connection\nis added to the sub-device\u0027s list of connections and removed from the\nglobal waiting connection list. Further on, the sub-device\u0027s possible own\nnotifier is searched for possible additional matches.\n\nFix these specific issues:\n\n- If v4l2_async_match_notify() failed before the sub-notifier handling,\n  the async connection was unbound and its entry removed from the\n  sub-device\u0027s async connection list. The latter part was also done in\n  v4l2_async_match_notify().\n\n- The async connection\u0027s sd field was only set after creating ancillary\n  links in v4l2_async_match_notify(). It was however dereferenced in\n  v4l2_async_unbind_subdev_one(), which was called on error path of\n  v4l2_async_match_notify() failure.",
  "id": "GHSA-qjw7-wgfm-9frq",
  "modified": "2026-05-11T21:31:30Z",
  "published": "2026-05-06T12:30:32Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-43189"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2de0a3c8148fc3dbea21981e6569f550b3626119"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/30aaed311f973f13ba13a0cd2dc0202f595fff48"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/461733d83e67ba7e3a5b750c0d203f738e01244f"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7345d6d356336c448d6b9230ed8704f39679fd12"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b02bcb378efa8af07827f49b3afcc5e825318c55"
    }
  ],
  "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…
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.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…