Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - mediatunerxc5000修正 xc5000_release 中的釋放後使用。原始程式碼在 xc5000_release() 中使用 cancel_delayed_work()如果已經執行延遲的工作項目 timer_sleep 則無法保證其已完全完成。這會導致釋放後使用狀況其中xc5000_release() 可能在 timer_sleep 仍處於作用中且嘗試解除參照 xc5000_priv 時釋放 xc5000_priv。典型爭用情形如下圖所示 CPU 0 (釋放執行緒) | CPU 1 (延遲工作回呼) xc5000_release() | xc5000_do_timer_sleep() cancel_delayed_work() | hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAF 將 cancel_delayed_work() 取代為 cancel_delayed_work_sync()可確保在解除配置 xc5000_priv 記憶體之前正確取消 timer_sleep。考慮了鎖死問題在處理程序內容中呼叫 xc5000_release()xc5000_release() 並未保留 timer_sleep 工作項目可能也需要的任何鎖定。因此在這裡使用 _sync() 變體是安全的。此錯誤最初是透過靜態分析發現的。 [hverkuil修正主體中的錯字tunner -> tuner] (CVE-2025-39994)

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - mediatunerxc5000xc5000_release の use-after-free を修正します 元のコードが xc5000_release() のCancel_delayed_work() を使用します。これは、すでに実行されている場合、遅延した作業項目 timer_sleep が完全に完了することを保証しません。これは、timer_sleep がまだアクティブで xc5000_priv の逆参照を試みる間に、xc5000_release() が xc5000_priv を解放する可能性がある use-after-free シナリオにつながります。いくつかの競合状態を以下に示します。CPU 0リリーススレッド| CPU 1遅延した作業コールバック xc5000_release() | xc5000_do_timer_sleep()Cancel_delayed_work()| hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAFCancel_delayed_work() をCancel_delayed_work_sync() で置換し、xc5000_priv メモリが割り当て解除される前に timer_sleep が適切にキャンセルされるようにします。デッドロックの懸念が考慮されましたxc5000_release() はプロセスコンテキストで呼び出され、timer_sleep 作業項目も必要とする可能性のあるロックを保持していません。したがって、_sync() バリアントの使用はここでは安全です。このバグは当初、静的分析によって特定されました。 [hverkuilSubject の誤字を修正しますtunner ->tuner]CVE-2025-39994

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - mediatunerxc5000修复 xc5000_release 中的释放后使用。原始代码在 xc5000_release() 中使用 cancel_delayed_work()这不能保证延迟的工作项目 timer_sleep 在已经运行时也能完全完成。这会导致释放后使用的情况其中 xc5000_release() 可能会在 timer_sleep 仍处于活动状态并尝试取消引用 xc5000_priv 时释放 xc5000_priv。一个典型的争用条件如下所示：CPU 0（发布线程）| CPU 1延迟工作回调xc5000_release() | | xc5000_do_timer_sleep() cancel_delayed_work() | hybrid_tuner_release_state(priv) | Hybrid_tuner_release_state(priv) | kfree(priv) | | priv = container_of() // UAF 将 cancel_delayed_work() 替换为 cancel_delayed_work_sync()以确保 timer_sleep 在取消分配 xc5000_priv 内存之前已正确取消。我们已考虑死锁问题在进程上下文中调用 xc5000_release() 并且未持有 timer_sleep 工作项目可能也需要的任何锁定。因此，_sync() 变体的使用在此处是安全的。最初通过静态分析发现此缺陷。 [hverkuil修复了 Subject: tunner -> tuner 中的拼写错误CVE-2025-39994

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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]     (CVE-2025-39994)

Note that Nessus relies on the presence of the package as reported by the vendor.

An update of the linux package has been released.

The remote Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6053 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6053-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     November 11, 2025                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2025-21861 CVE-2025-39929 CVE-2025-39931 CVE-2025-39934                      CVE-2025-39937 CVE-2025-39938 CVE-2025-39942 CVE-2025-39943                      CVE-2025-39944 CVE-2025-39945 CVE-2025-39946 CVE-2025-39949                      CVE-2025-39951 CVE-2025-39953 CVE-2025-39955 CVE-2025-39957                      CVE-2025-39964 CVE-2025-39967 CVE-2025-39968 CVE-2025-39969                      CVE-2025-39970 CVE-2025-39971 CVE-2025-39972 CVE-2025-39973                      CVE-2025-39977 CVE-2025-39978 CVE-2025-39980 CVE-2025-39982                      CVE-2025-39985 CVE-2025-39986 CVE-2025-39987 CVE-2025-39988                      CVE-2025-39993 CVE-2025-39994 CVE-2025-39995 CVE-2025-39996                      CVE-2025-39998 CVE-2025-40001 CVE-2025-40006 CVE-2025-40008                      CVE-2025-40010 CVE-2025-40011 CVE-2025-40013 CVE-2025-40018                      CVE-2025-40019 CVE-2025-40020 CVE-2025-40021 CVE-2025-40022                      CVE-2025-40026 CVE-2025-40027 CVE-2025-40029 CVE-2025-40030                      CVE-2025-40032 CVE-2025-40035 CVE-2025-40036 CVE-2025-40040                      CVE-2025-40042 CVE-2025-40043 CVE-2025-40044 CVE-2025-40048                      CVE-2025-40049 CVE-2025-40051 CVE-2025-40053 CVE-2025-40055                      CVE-2025-40056 CVE-2025-40060 CVE-2025-40062 CVE-2025-40068                      CVE-2025-40070 CVE-2025-40078 CVE-2025-40080 CVE-2025-40081                      CVE-2025-40084 CVE-2025-40085 CVE-2025-40087 CVE-2025-40088                      CVE-2025-40092 CVE-2025-40093 CVE-2025-40094 CVE-2025-40095                      CVE-2025-40096 CVE-2025-40099 CVE-2025-40100 CVE-2025-40103                      CVE-2025-40104 CVE-2025-40105 CVE-2025-40106 CVE-2025-40107                      CVE-2025-40109

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the oldstable distribution (bookworm), these problems have been fixed     in version 6.1.158-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
271554	Linux Distros 未修補的弱點：CVE-2025-39994	Nessus	Misc.	10/27/2025	10/27/2025	critical
271554	Linux Distros のパッチ未適用の脆弱性: CVE-2025-39994	Nessus	Misc.	10/27/2025	10/27/2025	critical
271554	Linux Distros 未修补的漏洞：CVE-2025-39994	Nessus	Misc.	10/27/2025	10/27/2025	critical
271554	Linux Distros Unpatched Vulnerability : CVE-2025-39994	Nessus	Misc.	10/27/2025	10/27/2025	critical
271366	Photon OS 5.0: Linux PHSA-2025-5.0-0655	Nessus	PhotonOS Local Security Checks	10/24/2025	10/24/2025	high
274816	Debian dsa-6053 : affs-modules-6.1.0-37-4kc-malta-di - security update	Nessus	Debian Local Security Checks	11/11/2025	11/11/2025	medium

Detections

Analytics

Plugins Search

critical

critical

critical

critical

high

medium