NVD / CVE Program· CNA Linux

CVE-2023-53388: drm/mediatek: Clean dangling pointer on bind error path

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.15% (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 36aa8c61af55675ed967900fbe5deb32d776f051, 49cf87919daeeeeeb9e924c39bdd9203af434461, 6a89ddee1686a8872384aaa9f0bcfa6b675acd86.

Low priority for now. Upgrade to Linux Linux 36aa8c61af55675ed967900fbe5deb32d776f051, 49cf87919daeeeeeb9e924c39bdd9203af434461, 6a89ddee1686a8872384aaa9f0bcfa6b675acd86 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/mediatek: Clean dangling pointer on bind error path mtk_drm_bind() can fail, in which case drm_dev_put() is called, destroying the drm_device object. However a pointer to it was still being held in the private object, and that pointer would be passed along to DRM in mtk_drm_sys_prepare() if a suspend were triggered at that point, resulting in a panic. Clean the pointer when destroying the object in the error path to prevent this from happening.

HighCVSS 7.8 · v3.1—No exploit Fix available

Memory safety

BDU:2026-03331

Published: Sep 18, 2025
Updated: Aug 5, 2026
EPSS: 0.1% · 4th 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%

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 kernel4.7 and later · before 4.19.276
linux linux kernel4.20 and later · before 5.4.235
linux linux kernel5.5 and later · before 5.10.173
linux linux kernel5.11 and later · before 5.15.99
linux linux kernel5.16 and later · before 6.1.16
linux linux kernel6.2 and later · before 6.2.3

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.7affected
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before 9a48f99aa7bea15e0b1d8b0040c46b4792eddf3baffected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5affected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before 6a89ddee1686a8872384aaa9f0bcfa6b675acd86affected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before 49cf87919daeeeeeb9e924c39bdd9203af434461affected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before 7b551a501fa714890e55bae73efede1185728d72affected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before f3887c771576c5d740c5c5b8bf654a8ab8020b7daffected · git
- 119f5173628aa7a0c3cf9db83460d40709e8241d and later · before 36aa8c61af55675ed967900fbe5deb32d776f051affected · git
- before 4.7not affected · semver
- 4.19.276 and later · up to and including 4.19.*not 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.20-1	6.1.20-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-2023-53386Sep 18, 2025 · Bluetooth: Fix potential use-after-free when clear keys
31Monitor
← EarlierCVE-2023-53387Sep 18, 2025 · scsi: ufs: core: Fix device management cmd timeout flow
22Monitor
Later →CVE-2023-53389Sep 18, 2025 · drm/mediatek: dp: Only trigger DRM HPD events if bridge is attached
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	36aa8c61af55675ed967900fbe5deb32d776f051	Vendor (CNA)
Linux Linux	49cf87919daeeeeeb9e924c39bdd9203af434461	Vendor (CNA)
Linux Linux	6a89ddee1686a8872384aaa9f0bcfa6b675acd86	Vendor (CNA)
Linux Linux	7b551a501fa714890e55bae73efede1185728d72	Vendor (CNA)
Linux Linux	9a48f99aa7bea15e0b1d8b0040c46b4792eddf3b	Vendor (CNA)
Linux Linux	a161f1d92aabb3b8463f752bdc3474dc3a5ec0e5	Vendor (CNA)
Linux Linux	f3887c771576c5d740c5c5b8bf654a8ab8020b7d	Vendor (CNA)
debian:linux	6.1.20-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).

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

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

References

git.kernel.org/stable/c/36aa8c61af55675ed967900fbe5deb32d776f051

Show all references (6 more)

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

All records