Skip to content
Noroxi
CVE-2025-40316· NVD / CVE Program· CNA Linux

drm/mediatek: Fix device use-after-free on unbind

Noroxi assessment

Priority: Monitor (action score 0/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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 0142fe895986addf35885b43440718e567121155, 6.12.58, 6.17.

Low priority for now. Upgrade to Linux Linux 0142fe895986addf35885b43440718e567121155, 6.12.58, 6.17 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: Fix device use-after-free on unbind A recent change fixed device reference leaks when looking up drm platform device driver data during bind() but failed to remove a partial fix which had been added by commit 80805b62ea5b ("drm/mediatek: Fix kobject put for component sub-drivers"). This results in a reference imbalance on component bind() failures and on unbind() which could lead to a user-after-free. Make sure to only drop the references after retrieving the driver data by effectively reverting the previous partial fix. Note that holding a reference to a device does not prevent its driver data from going away so there is no point in keeping the reference.

—No exploit Fix available
Published
Dec 8, 2025
Updated
Oct 14, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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.

Follow CVE-2025-40316

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

—

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

    • fae58d0155a979a8c414bbc12db09dd4b2f910d0, 6.17affected
    • 7d98166183d627c0b9daca7672b2191fae0f8a03 and later · before a5a896f8315de358a2932e2c23c42d550256046aaffected · git
    • 31ce7c089b50c3d3056c37e0e25e7535e4428ae1 and later · before 0142fe895986addf35885b43440718e567121155affected · git
    • 1f403699c40f0806a707a9a6eed3b8904224021a and later · before 8ba827e09eb586e952d10e39406fa02d10bb591eaffected · git
    • 1f403699c40f0806a707a9a6eed3b8904224021a and later · before 926d002e6d7e2f1fd5c1b53cf6208153ee7d380daffected · git
    • 6.6.105 and later · before 6.6.117affected · semver
    • 6.12.45 and later · before 6.12.58affected · semver
    • 6.16.5 and later · before 6.17affected · semver
    • before 6.17not affected · semver
    • 6.6.117 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40314Dec 8, 2025 · usb: cdns3: gadget: Use-after-free during failed initialization and exit of cdnsp gadget
    0Monitor
  • ← EarlierCVE-2025-40315Dec 8, 2025 · usb: gadget: f_fs: Fix epfile null pointer access after ep enable.
    0Monitor
  • Later →CVE-2025-40317Dec 8, 2025 · regmap: slimbus: fix bus_context pointer in regmap init calls
    31Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Linux Linux0142fe895986addf35885b43440718e567121155Vendor (CNA)
Linux Linux6.12.58Vendor (CNA)
Linux Linux6.17Vendor (CNA)
Linux Linux6.6.117Vendor (CNA)
Linux Linux8ba827e09eb586e952d10e39406fa02d10bb591eVendor (CNA)
Linux Linux926d002e6d7e2f1fd5c1b53cf6208153ee7d380dVendor (CNA)
Linux Linuxa5a896f8315de358a2932e2c23c42d550256046aVendor (CNA)
debian:linux6.12.63-1 · Debian:13Package 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.

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Fix✗ → ✓

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

References

All records