CVE-2025-39994: media: tuner: xc5000: Fix use-after-free in xc5000_release
Noroxi assessment
Priority: Monitor (action score 29/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. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 3f876cd47ed8bca1e28d68435845949f51f90703, 40b7a19f321e65789612ebaca966472055dab48c, 4266f012806fc18e46da4a04d130df59a4946f93; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 3f876cd47ed8bca1e28d68435845949f51f90703, 40b7a19f321e65789612ebaca966472055dab48c, 4266f012806fc18e46da4a04d130df59a4946f93; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-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: 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]
- Published
- Oct 15, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- —
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.3 / 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
- —
- CNA · Linux
- 7.3
- NVD has not scored this yet; the score shown is the CNA’s.
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.
Is your version affected? Check itNoroxi 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 helpAffected 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
- 3.16affected
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8affected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before e2f5eaafc0306a76fb1cb760aae804b065b8a341affected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before 3f876cd47ed8bca1e28d68435845949f51f90703affected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before df0303b4839520b84d9367c2fad65b13650a4d42affected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before 71ed8b81a4906cb785966910f39cf7f5ad60a69eaffected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before effb1c19583bca7022fa641a70766de45c6d41acaffected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before 9a00de20ed8ba90888479749b87bc1532cded4ceaffected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before 4266f012806fc18e46da4a04d130df59a4946f93affected · git
- f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 and later · before 40b7a19f321e65789612ebaca966472055dab48caffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.171.1.el8_10 | 4.18.0-553.171.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-devel | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
| AlmaLinux:8 | kernel-rt-modules | before 4.18.0-553.171.1.rt7.512.el8_10 | 4.18.0-553.171.1.rt7.512.el8_10 |
+67
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-39992Oct 15, 2025 · mm: swap: check for stable address space before operating on the VMA0Monitor
- ← EarlierCVE-2025-39993Oct 15, 2025 · media: rc: fix races with imon_disconnect()31Monitor
- Later →CVE-2025-39995Oct 15, 2025 · media: i2c: tc358743: Fix use-after-free bugs caused by orphan timer in probe0Monitor
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 | 3f876cd47ed8bca1e28d68435845949f51f90703 | Vendor (CNA) |
| Linux Linux | 40b7a19f321e65789612ebaca966472055dab48c | Vendor (CNA) |
| Linux Linux | 4266f012806fc18e46da4a04d130df59a4946f93 | Vendor (CNA) |
| Linux Linux | 71ed8b81a4906cb785966910f39cf7f5ad60a69e | Vendor (CNA) |
| Linux Linux | 9a00de20ed8ba90888479749b87bc1532cded4ce | Vendor (CNA) |
| Linux Linux | bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8 | Vendor (CNA) |
| Linux Linux | df0303b4839520b84d9367c2fad65b13650a4d42 | Vendor (CNA) |
| Linux Linux | e2f5eaafc0306a76fb1cb760aae804b065b8a341 | Vendor (CNA) |
| Linux Linux | effb1c19583bca7022fa641a70766de45c6d41ac | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:bpftool | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.171.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-core | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-debug-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-devel | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-rt-modules-extra | 4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.17.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:kernel-source-longterm | 6.18.16-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:kernel-rt | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-core | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
| red hat:kernel-rt-debug-debuginfo | 0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfv | Package registry (OSV) |
+9
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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- 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
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
nvd-secondary
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/40b7a19f321e65789612ebaca966472055dab48c
- git.kernel.org/stable/c/4266f012806fc18e46da4a04d130df59a4946f93
- git.kernel.org/stable/c/71ed8b81a4906cb785966910f39cf7f5ad60a69e
- git.kernel.org/stable/c/9a00de20ed8ba90888479749b87bc1532cded4ce
- git.kernel.org/stable/c/bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8
- git.kernel.org/stable/c/df0303b4839520b84d9367c2fad65b13650a4d42
- git.kernel.org/stable/c/e2f5eaafc0306a76fb1cb760aae804b065b8a341
- git.kernel.org/stable/c/effb1c19583bca7022fa641a70766de45c6d41ac
Vendor advisories and official records. Exploit/PoC links are deliberately left out.