CVE-2026-43236

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release

The atmel_hlcdc_plane_atomic_duplicate_state() callback was copying the atmel_hlcdc_plane state structure without properly duplicating the drm_plane_state. In particular, state->commit remained set to the old state commit, which can lead to a use-after-free in the next drm_atomic_commit() call.

Fix this by calling __drm_atomic_helper_duplicate_plane_state(), which correctly clones the base drm_plane_state (including the ->commit pointer).

It has been seen when closing and re-opening the device node while another DRM client (e.g. fbdev) is still attached:

============================================================================= BUG kmalloc-64 (Not tainted): Poison overwritten -----------------------------------------------------------------------------

0xc611b344-0xc611b344 @offset=836. First byte 0x6a instead of 0x6b FIX kmalloc-64: Restoring Poison 0xc611b344-0xc611b344=0x6b Allocated in drm_atomic_helper_setup_commit+0x1e8/0x7bc age=178 cpu=0 pid=29 drm_atomic_helper_setup_commit+0x1e8/0x7bc drm_atomic_helper_commit+0x3c/0x15c drm_atomic_commit+0xc0/0xf4 drm_framebuffer_remove+0x4cc/0x5a8 drm_mode_rmfb_work_fn+0x6c/0x80 process_one_work+0x12c/0x2cc worker_thread+0x2a8/0x400 kthread+0xc0/0xdc ret_from_fork+0x14/0x28 Freed in drm_atomic_helper_commit_hw_done+0x100/0x150 age=8 cpu=0 pid=169 drm_atomic_helper_commit_hw_done+0x100/0x150 drm_atomic_helper_commit_tail+0x64/0x8c commit_tail+0x168/0x18c drm_atomic_helper_commit+0x138/0x15c drm_atomic_commit+0xc0/0xf4 drm_atomic_helper_set_config+0x84/0xb8 drm_mode_setcrtc+0x32c/0x810 drm_ioctl+0x20c/0x488 sys_ioctl+0x14c/0xc20 ret_fast_syscall+0x0/0x54 Slab 0xef8bc360 objects=21 used=16 fp=0xc611b7c0 flags=0x200(workingset|zone=0) Object 0xc611b340 @offset=832 fp=0xc611b7c0

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd4a4d0711f48a99b25bcd45e00eef8339eff82d
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bc847787233277a337788568e90a6ee1557595eb
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ac2d898da5095d46bd1ff8585fdd753d58ad91e7
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a205740a7231e967ac77cb731171642901c327af
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7b4d0fab3ff2c00c6d34e1952c9df5129a826aee
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/796e77c14c4c1e2cd36473760fb6cc66c695eb47
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6404898af86d986db1dbbe06177c143e40652e49
generic

drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/549c6db503dbb85dbff4840830971853feac6625

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-23ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-23ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.186.196~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1112.119~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
linuxKernel @ 5.10.252—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (116 versions)6.19.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(24)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 216 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 16:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-23 19:55 UTCEG score recompute
  18. 2026-08-23 19:55 UTCVendor advisory
  19. 2026-08-23 19:54 UTCGHSA enrichment
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-17 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 12:54 UTCEG score recompute
  2. 2026-08-17 12:54 UTCVendor advisory
  3. 2026-08-17 12:54 UTCGHSA enrichment
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 04:52 UTCEG score recompute
  6. 2026-08-16 04:52 UTCVendor advisory
  7. 2026-08-16 04:52 UTCGHSA enrichment
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-15 01:27 UTCVendor advisory
  11. 2026-08-15 01:27 UTCGHSA enrichment
  12. 2026-08-14 14:26 UTCVendor advisory
  13. 2026-08-14 14:26 UTCGHSA enrichment
  14. 2026-08-14 03:26 UTCEG score recompute
  15. 2026-08-14 03:26 UTCVendor advisory
  16. 2026-08-14 03:26 UTCGHSA enrichment
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 04:00 UTCVendor advisory
  19. 2026-08-13 04:00 UTCGHSA enrichment
  20. 2026-08-12 17:00 UTCEG score recompute
  21. 2026-08-12 17:00 UTCVendor advisory
  22. 2026-08-12 17:00 UTCGHSA enrichment
  23. 2026-08-12 13:51 UTCEPSS rescore
  24. 2026-08-11 16:00 UTCVendor advisory
  25. 2026-08-11 16:00 UTCGHSA enrichment
  26. 2026-08-11 01:31 UTCEG score recompute
  27. 2026-08-11 01:31 UTCVendor advisory
  28. 2026-08-11 01:31 UTCGHSA enrichment
  29. 2026-08-11 00:00 UTCEPSS rescore
  30. 2026-08-10 11:47 UTCVendor advisory
  31. 2026-08-10 11:46 UTCGHSA enrichment
  32. 2026-08-10 00:34 UTCEG score recompute
  33. 2026-08-10 00:34 UTCVendor advisory
  34. 2026-08-10 00:34 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 13:34 UTCVendor advisory
  37. 2026-08-09 13:34 UTCGHSA enrichment
  38. 2026-08-09 02:35 UTCEG score recompute
  39. 2026-08-09 02:35 UTCVendor advisory
  40. 2026-08-09 02:35 UTCGHSA enrichment
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 10:53 UTCVendor advisory
  43. 2026-08-08 10:53 UTCGHSA enrichment
  44. 2026-08-07 23:53 UTCEG score recompute
  45. 2026-08-07 23:53 UTCVendor advisory
  46. 2026-08-07 23:53 UTCGHSA enrichment
  47. 2026-08-07 12:53 UTCVendor advisory
  48. 2026-08-07 12:53 UTCGHSA enrichment
  49. 2026-08-07 01:54 UTCEG score recompute
  50. 2026-08-07 01:54 UTCVendor advisory
  51. 2026-08-07 01:54 UTCGHSA enrichment
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 11:50 UTCVendor advisory
  54. 2026-08-06 11:49 UTCGHSA enrichment
  55. 2026-08-06 00:50 UTCEG score recompute
  56. 2026-08-06 00:50 UTCVendor advisory
  57. 2026-08-06 00:50 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-05 13:51 UTCEG score recompute
  60. 2026-08-05 13:51 UTCVendor advisory
  61. 2026-08-05 13:51 UTCGHSA enrichment
  62. 2026-08-04 15:10 UTCEPSS rescore
  63. 2026-08-04 10:38 UTCEPSS rescore
  64. 2026-08-03 19:52 UTCEG score recompute
  65. 2026-08-03 19:52 UTCVendor advisory
  66. 2026-08-03 19:52 UTCGHSA enrichment
  67. 2026-08-03 10:36 UTCEPSS rescore
  68. 2026-08-03 03:59 UTCVendor advisory
  69. 2026-08-03 03:59 UTCGHSA enrichment
  70. 2026-08-02 16:06 UTCVendor advisory
  71. 2026-08-02 16:06 UTCGHSA enrichment
  72. 2026-08-02 05:07 UTCEG score recompute
  73. 2026-08-02 05:07 UTCVendor advisory
  74. 2026-08-02 05:07 UTCGHSA enrichment
  75. 2026-08-02 02:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43236?
CVE-2026-43236 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/atmel-hlcdc: fix use-after-free of drmcrtccommit after release The atmelhlcdcplaneatomicduplicate_state() callback was copying the atmelhlcdcplane state structure without properly duplicating the drmplanestate. In particular,…
When was CVE-2026-43236 disclosed?
CVE-2026-43236 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43236 actively exploited?
CVE-2026-43236 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43236?
CVE-2026-43236 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43236

Explore →

Is Your Infrastructure Affected by CVE-2026-43236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs