GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

GHSA-J9HG-PRQV-M4RX

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32
VLAI
Details

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

drm/rockchip: inno-hdmi: Switch to drmm_kzalloc()

Driver makes use of drmm_encoder_init() to initialize the encoder and automatically handle the cleanup by registering drm_encoder_cleanup() with drmm_add_action().

However, the internal structure containing the encoder part gets allocated with devm_kzalloc(), which happens while component_bind_all() is being called from Rockchip DRM driver. The component framework further ensures it is deallocated as part of releasing all the resources claimed during bind, which is triggered from component_unbind_all().

When the reference to the DRM device gets eventually dropped via drm_dev_put() in rockchip_drm_unbind(), drmm_encoder_alloc_release() attempts to access the now released encoder structure, leading to use-after-free.

Ensure driver's internal structure is still reachable on encoder cleanup by switching from a device-managed allocation to a drm-managed one.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-74422"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:44Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/rockchip: inno-hdmi: Switch to drmm_kzalloc()\n\nDriver makes use of drmm_encoder_init() to initialize the encoder and\nautomatically handle the cleanup by registering drm_encoder_cleanup()\nwith drmm_add_action().\n\nHowever, the internal structure containing the encoder part gets\nallocated with devm_kzalloc(), which happens while component_bind_all()\nis being called from Rockchip DRM driver.  The component framework\nfurther ensures it is deallocated as part of releasing all the resources\nclaimed during bind, which is triggered from component_unbind_all().\n\nWhen the reference to the DRM device gets eventually dropped via\ndrm_dev_put() in rockchip_drm_unbind(), drmm_encoder_alloc_release()\nattempts to access the now released encoder structure, leading to\nuse-after-free.\n\nEnsure driver\u0027s internal structure is still reachable on encoder cleanup\nby switching from a device-managed allocation to a drm-managed one.",
  "id": "GHSA-j9hg-prqv-m4rx",
  "modified": "2026-08-15T06:32:33Z",
  "published": "2026-08-15T06:32:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74422"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/195ab348af4b2bdf5988f9397059317bb68fd797"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3cc50e7f73fcf79f28660b9d91566b13cb62e520"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



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…

Loading…