Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-39994: media: tuner: xc5000: Fix use-after-free in xc5000_release

HighCVSS 7.3 · v3.1—No exploit Fix available

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

JSON

Action score

29

Monitor

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.

Follow CVE-2025-39994

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE 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, at most 30 a day (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
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

    • 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.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.171.1.el8_104.18.0-553.171.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.171.1.rt7.512.el8_104.18.0-553.171.1.rt7.512.el8_10

+67

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-39992Oct 15, 2025 · mm: swap: check for stable address space before operating on the VMA
    0Monitor
  • ← 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 probe
    0Monitor

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 Linux3f876cd47ed8bca1e28d68435845949f51f90703Vendor (CNA)
Linux Linux40b7a19f321e65789612ebaca966472055dab48cVendor (CNA)
Linux Linux4266f012806fc18e46da4a04d130df59a4946f93Vendor (CNA)
Linux Linux71ed8b81a4906cb785966910f39cf7f5ad60a69eVendor (CNA)
Linux Linux9a00de20ed8ba90888479749b87bc1532cded4ceVendor (CNA)
Linux Linuxbc4ffd962ce16a154c44c68853b9d93f5b6fc4b8Vendor (CNA)
Linux Linuxdf0303b4839520b84d9367c2fad65b13650a4d42Vendor (CNA)
Linux Linuxe2f5eaafc0306a76fb1cb760aae804b065b8a341Vendor (CNA)
Linux Linuxeffb1c19583bca7022fa641a70766de45c6d41acVendor (CNA)
azl3 kernel 6.6.104.2-4 on Azure Linux 3.06.6.112.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.171.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.171.1.rt7.512.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.158-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.17.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kernel-source-longterm6.18.16-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:kernel-rt0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.171.1.rt7.512.el8_10 · Red Hat:enterprise_linux:8::nfvPackage 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.

References

All records