NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 549c6db503dbb85dbff4840830971853feac6625, 6404898af86d986db1dbbe06177c143e40652e49, 796e77c14c4c1e2cd36473760fb6cc66c695eb47.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 549c6db503dbb85dbff4840830971853feac6625, 6404898af86d986db1dbbe06177c143e40652e49, 796e77c14c4c1e2cd36473760fb6cc66c695eb47 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-11102

Published: May 6, 2026
Updated: Aug 5, 2026
EPSS: 0.1% · 2th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 31 / 40 · 7.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CNA vs NVD score

NVD: —
CNA · Linux: 7.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel4.1 and later · before 5.10.252
linux linux kernel5.11 and later · before 5.15.202
linux linux kernel5.16 and later · before 6.1.165
linux linux kernel6.2 and later · before 6.6.128
linux linux kernel6.7 and later · before 6.12.75
linux linux kernel6.13 and later · before 6.18.16
linux linux kernel6.19 and later · before 6.19.6

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 4.1affected
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before fd4a4d0711f48a99b25bcd45e00eef8339eff82daffected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before 6404898af86d986db1dbbe06177c143e40652e49affected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before 796e77c14c4c1e2cd36473760fb6cc66c695eb47affected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before ac2d898da5095d46bd1ff8585fdd753d58ad91e7affected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before a205740a7231e967ac77cb731171642901c327afaffected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before 7b4d0fab3ff2c00c6d34e1952c9df5129a826aeeaffected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before 549c6db503dbb85dbff4840830971853feac6625affected · git
- 2389fc1305fc1e2cf8b310a75463fefd3058bf48 and later · before bc847787233277a337788568e90a6ee1557595ebaffected · git
- before 4.1not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.170-1	6.1.170-1
Debian:13	linux	before 6.12.85-1	6.12.85-1
Debian:14	linux	before 6.19.6-1	6.19.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-43232May 6, 2026 · net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets
35Monitor
← EarlierCVE-2026-43235May 6, 2026 · media: iris: Add missing platform data entries for SM8750
22Monitor
Later →CVE-2026-43241May 6, 2026 · ntb: ntb_hw_switchtec: Fix array-index-out-of-bounds access
28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	549c6db503dbb85dbff4840830971853feac6625	Vendor (CNA)
Linux Linux	6404898af86d986db1dbbe06177c143e40652e49	Vendor (CNA)
Linux Linux	796e77c14c4c1e2cd36473760fb6cc66c695eb47	Vendor (CNA)
Linux Linux	7b4d0fab3ff2c00c6d34e1952c9df5129a826aee	Vendor (CNA)
Linux Linux	a205740a7231e967ac77cb731171642901c327af	Vendor (CNA)
Linux Linux	ac2d898da5095d46bd1ff8585fdd753d58ad91e7	Vendor (CNA)
Linux Linux	bc847787233277a337788568e90a6ee1557595eb	Vendor (CNA)
Linux Linux	fd4a4d0711f48a99b25bcd45e00eef8339eff82d	Vendor (CNA)
debian:linux	6.1.170-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0196 · May 8, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Someone with local access to the system can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Local
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records