CVE-2025-39994High· 7.3▾ TwilightIn 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 …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 40.2 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.2%
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]
Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < bc4ffd962ce16a154c44c68853b9d93f5b6fc4b8Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < e2f5eaafc0306a76fb1cb760aae804b065b8a341Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < 3f876cd47ed8bca1e28d68435845949f51f90703Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < df0303b4839520b84d9367c2fad65b13650a4d42Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < 71ed8b81a4906cb785966910f39cf7f5ad60a69eLinux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < effb1c19583bca7022fa641a70766de45c6d41acLinux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < 9a00de20ed8ba90888479749b87bc1532cded4ceLinux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < 4266f012806fc18e46da4a04d130df59a4946f93Linux >= f7a27ff1fb77e114d1059a5eb2ed1cffdc508ce8 < 40b7a19f321e65789612ebaca966472055dab48cLinux 3.16Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets