NVD / CVE Program· CNA Linux

CVE-2024-56538: drm: zynqmp_kms: Unplug DRM device before removal

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.26% (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 2e07c88914fc5289c21820b1aa94f058feb38197, 4fb97432e28a7e136b2d76135d50e988ada8e1af, 692f52aedccbf79b212a1e14e3735192b4c24a7d; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 2e07c88914fc5289c21820b1aa94f058feb38197, 4fb97432e28a7e136b2d76135d50e988ada8e1af, 692f52aedccbf79b212a1e14e3735192b4c24a7d; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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: zynqmp_kms: Unplug DRM device before removal Prevent userspace accesses to the DRM device from causing use-after-frees by unplugging the device before we remove it. This causes any further userspace accesses to result in an error without further calls into this driver's internals.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2025-07220

Published: Dec 27, 2024
Updated: Aug 5, 2026
EPSS: 0.2% · 19th 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.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 7.8
CNA · Linux: 7.8; agree

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 kernel5.9 and later · before 6.6.64
linux linux kernel6.7 and later · before 6.11.11
linux linux kernel6.12 and later · before 6.12.2

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
- 5.9affected
- d76271d22694e874ed70791702db9252ffe96a4c and later · before a17b9afe58c474657449cf87e238b1788200576baffected · git
- d76271d22694e874ed70791702db9252ffe96a4c and later · before 4fb97432e28a7e136b2d76135d50e988ada8e1afaffected · git
- d76271d22694e874ed70791702db9252ffe96a4c and later · before 692f52aedccbf79b212a1e14e3735192b4c24a7daffected · git
- d76271d22694e874ed70791702db9252ffe96a4c and later · before 2e07c88914fc5289c21820b1aa94f058feb38197affected · git
- before 5.9not affected · semver
- 6.6.64 and later · up to and including 6.6.*not affected · semver
- 6.11.11 and later · up to and including 6.11.*not affected · semver
- 6.12.2 and later · up to and including 6.12.*not affected · semver
- 6.13 and laternot affected · original_commit_for_fix

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	from 0	—
Debian:13	linux	before 6.12.3-1	6.12.3-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-2024-56536Dec 27, 2024 · wifi: cw1200: Fix potential NULL dereference
22Monitor
← EarlierCVE-2024-56537Dec 27, 2024 · drm: xlnx: zynqmp_disp: layer may be null while releasing
22Monitor
Later →CVE-2024-56539Dec 27, 2024 · wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan()
22Monitor

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	2e07c88914fc5289c21820b1aa94f058feb38197	Vendor (CNA)
Linux Linux	4fb97432e28a7e136b2d76135d50e988ada8e1af	Vendor (CNA)
Linux Linux	692f52aedccbf79b212a1e14e3735192b4c24a7d	Vendor (CNA)
Linux Linux	a17b9afe58c474657449cf87e238b1788200576b	Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.0	6.6.64.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.0	6.6.64.2-1 · CBL-Mariner Releases	Microsoft (MSRC)
debian:linux	6.12.3-1 · Debian:13	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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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).

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-primary

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:09 PM UTC

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

References

git.kernel.org/stable/c/2e07c88914fc5289c21820b1aa94f058feb38197

Show all references (3 more)

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

All records