CVE-2025-39994

media: tuner: xc5000: Fix use-after-free in xc5000_release

HIGH
7.3
CVSS Score
Published: October 15, 2025 at 07:58 AM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.3
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: media: tuner: xc5000: Fix use-after-free in xc5000_release The original code uses cancel_delayed_work() in xc5000_release(), which does not guarantee that the delayed work item timer_sleep has fully completed if it was already running. This leads to use-after-free scenarios where xc5000_release() may free the xc5000_priv while timer_sleep is still active and attempts to dereference the xc5000_priv. A typical race condition is illustrated below: CPU 0 (release thread) | CPU 1 (delayed work callback) xc5000_release() | xc5000_do_timer_sleep() cancel_delayed_work() | hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAF Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure that the timer_sleep is properly canceled before the xc5000_priv memory is deallocated. A deadlock concern was considered: xc5000_release() is called in a process context and is not holding any locks that the timer_sleep work item might also need. Therefore, the use of the _sync() variant is safe here. This bug was initially identified through static analysis. [hverkuil: fix typo in Subject: tunner -> tuner]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.16f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8
Vendor states this is fixed in 3f876cd47ed8bca1e28d68435845949f51f90703 (fixed)
Vendor states this is fixed in 40b7a19f321e65789612ebaca966472055dab48c (fixed)
Vendor states this is fixed in 4266f012806fc18e46da4a04d130df59a4946f93 (fixed)
Vendor states this is fixed in 71ed8b81a4906cb785966910f39cf7f5ad60a69e (fixed)
Vendor states this is fixed in 9a00de20ed8ba90888479749b87bc1532cded4ce (fixed)
Vendor states this is fixed in bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8 (fixed)
Vendor states this is fixed in df0303b4839520b84d9367c2fad65b13650a4d42 (fixed)
Vendor states this is fixed in e2f5eaafc0306a76fb1cb760aae804b065b8a341 (fixed)
Vendor states this is fixed in effb1c19583bca7022fa641a70766de45c6d41ac (fixed)
Vendor states this is fixed in 3.16 (unaffected)
Vendor states this is fixed in 5.10.246 (unaffected)
Vendor states this is fixed in 5.15.195 (unaffected)
Vendor states this is fixed in 5.4.301 (unaffected)
Vendor states this is fixed in 6.1.156 (unaffected)
Vendor states this is fixed in 6.12.51 (unaffected)
Vendor states this is fixed in 6.16.11 (unaffected)
Vendor states this is fixed in 6.17.1 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.111 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.3HIGHLinux
Vector?

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card