Answer in brief
CVE-2025-39994 records a Unknown severity vulnerability in media: tuner: xc5000: Fix use-after-free in xc5000_release. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-39994 records a Unknown severity vulnerability in media: tuner: xc5000: Fix use-after-free in xc5000_release. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <e2f5eaafc0306a76fb1cb760aae804b065b8a341 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <3f876cd47ed8bca1e28d68435845949f51f90703 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <df0303b4839520b84d9367c2fad65b13650a4d42 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <71ed8b81a4906cb785966910f39cf7f5ad60a69e || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <effb1c19583bca7022fa641a70766de45c6d41ac || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <9a00de20ed8ba90888479749b87bc1532cded4ce || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <4266f012806fc18e46da4a04d130df59a4946f93 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <40b7a19f321e65789612ebaca966472055dab48c | bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8, e2f5eaafc0306a76fb1cb760aae804b065b8a341, 3f876cd47ed8bca1e28d68435845949f51f90703, df0303b4839520b84d9367c2fad65b13650a4d42, 71ed8b81a4906cb785966910f39cf7f5ad60a69e, effb1c19583bca7022fa641a70766de45c6d41ac, 9a00de20ed8ba90888479749b87bc1532cded4ce, 4266f012806fc18e46da4a04d130df59a4946f93, 40b7a19f321e65789612ebaca966472055dab48c |
| Linux/Linuxgeneric | 3.16 | Not reported |
Published upstream
Oct 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <e2f5eaafc0306a76fb1cb760aae804b065b8a341 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <3f876cd47ed8bca1e28d68435845949f51f90703 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <df0303b4839520b84d9367c2fad65b13650a4d42 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <71ed8b81a4906cb785966910f39cf7f5ad60a69e || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <effb1c19583bca7022fa641a70766de45c6d41ac || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <9a00de20ed8ba90888479749b87bc1532cded4ce || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <4266f012806fc18e46da4a04d130df59a4946f93 || >=f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 <40b7a19f321e65789612ebaca966472055dab48c | bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8, e2f5eaafc0306a76fb1cb760aae804b065b8a341, 3f876cd47ed8bca1e28d68435845949f51f90703, df0303b4839520b84d9367c2fad65b13650a4d42, 71ed8b81a4906cb785966910f39cf7f5ad60a69e, effb1c19583bca7022fa641a70766de45c6d41ac, 9a00de20ed8ba90888479749b87bc1532cded4ce, 4266f012806fc18e46da4a04d130df59a4946f93, 40b7a19f321e65789612ebaca966472055dab48c |
| Linux/Linuxgeneric | 3.16 | Not reported |
Published upstream
Oct 15, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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]
Quoted source text, attributed separately from HOL analysis.