[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-39994":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":21,"related":22,"reserved_at":9,"published_at":23,"modified_at":24,"state":9,"summary":25,"references_raw":27,"kevs":34,"epss":9,"epss_history":35,"metrics":36,"affected":37},"DEBIAN-CVE-2025-39994","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]",null,[],[],[],[14],{"_key":15},"CVE-2025-39994",[17,19],{"_key":18},"DLA-4379-1",{"_key":20},"DSA-6053-1",[],[],"2025-10-15T08:15:37.567Z","2026-04-28T20:30:25.178625Z",{"cisa_kev":26,"cisa_ransomware":26,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[28],{"url":29,"sources":30,"tags":32},"https://security-tracker.debian.org/tracker/CVE-2025-39994",[31],"osv_debian",[33],"Advisory",[],[],[],[38,59],{"ecosystem":39,"name":40,"vendor":41,"product":40,"cpe_part":9,"purl_type":42,"purl_namespace":41,"purl_name":40,"source":9,"versions":43},"Debian","linux","debian","deb",[44,50,53,56],{"version":45,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":48,"version_end_type":49,"fixed_in":9},"lt5_10_247_1",true,"ecosystem","5.10.247-1","excluding",{"version":51,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":52,"version_end_type":49,"fixed_in":9},"lt6_1_158_1","6.1.158-1",{"version":54,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":55,"version_end_type":49,"fixed_in":9},"lt6_12_57_1","6.12.57-1",{"version":57,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":58,"version_end_type":49,"fixed_in":9},"lt6_16_11_1","6.16.11-1",{"ecosystem":39,"name":60,"vendor":41,"product":60,"cpe_part":9,"purl_type":42,"purl_namespace":41,"purl_name":60,"source":9,"versions":61},"linux-6.1",[62],{"version":63,"is_range":46,"range_type":47,"version_start":9,"version_start_type":9,"version_end":64,"version_end_type":49,"fixed_in":9},"lt6_1_158_1~deb11u1","6.1.158-1~deb11u1"]