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

  - 已解決 Linux 核心中的下列弱點：binder: fix async_free_space accounting for empty parcels In 4.13, commit 74310e06be4d (android: binder: Move buffer out of area shared with user space) fixed a kernel structure visibility issue. As part of that patch, sizeof(void *) was used as the buffer size for 0-length data payloads so the driver could detect abusive clients sending 0-length asynchronous transactions to a server by enforcing limits on async_free_size. Unfortunately, on the free side, the accounting of async_free_space did not add the sizeof(void *) back. The result was that up to 8-bytes of async_free_space were leaked on every async transaction of 8-bytes or less. These small transactions are uncommon, so this accounting issue has gone undetected for several years. The fix is to use buffer_size (the allocated buffer size) instead of size (the logical buffer size) when updating the async_free_space during the free operation. These are the same except for this corner case of asynchronous transactions with payloads < 8 bytes. (CVE-2021-46935)

請注意，Nessus 依賴供應商報告的套件存在。

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

  - 已修复 Linux 内核中的下列漏洞：binder: fix async_free_space accounting for empty parcels In 4.13, commit 74310e06be4d (android: binder: Move buffer out of area shared with user space) fixed a kernel structure visibility issue. As part of that patch, sizeof(void *) was used as the buffer size for 0-length data payloads so the driver could detect abusive clients sending 0-length asynchronous transactions to a server by enforcing limits on async_free_size. Unfortunately, on the free side, the accounting of async_free_space did not add the sizeof(void *) back. The result was that up to 8-bytes of async_free_space were leaked on every async transaction of 8-bytes or less. These small transactions are uncommon, so this accounting issue has gone undetected for several years. The fix is to use buffer_size (the allocated buffer size) instead of size (the logical buffer size) when updating the async_free_space during the free operation. These are the same except for this corner case of asynchronous transactions with payloads < 8 bytes. (CVE-2021-46935)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: binder: fix async_free_space accounting for empty parcels In 4.13, commit 74310e06be4d (android: binder: Move buffer out of area shared with user space) fixed a kernel structure visibility issue. As part of that patch, sizeof(void *) was used as the buffer size for 0-length data payloads so the driver could detect abusive clients sending 0-length asynchronous transactions to a server by enforcing limits on async_free_size. Unfortunately, on the free side, the accounting of async_free_space did not add the sizeof(void *) back. The result was that up to 8-bytes of async_free_space were leaked on every async transaction of 8-bytes or less. These small transactions are uncommon, so this accounting issue has gone undetected for several years. The fix is to use buffer_size (the allocated buffer size) instead of size (the logical buffer size) when updating the async_free_space during the free operation. These are the same except for this corner case of asynchronous transactions with payloads < 8 bytes. (CVE-2021-46935)

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

An update of the linux package has been released.

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

  - In the Linux kernel, the following vulnerability has been resolved: binder: fix async_free_space     accounting for empty parcels In 4.13, commit 74310e06be4d (android: binder: Move buffer out of area     shared with user space) fixed a kernel structure visibility issue. As part of that patch, sizeof(void *)     was used as the buffer size for 0-length data payloads so the driver could detect abusive clients sending     0-length asynchronous transactions to a server by enforcing limits on async_free_size. Unfortunately, on     the free side, the accounting of async_free_space did not add the sizeof(void *) back. The result was     that up to 8-bytes of async_free_space were leaked on every async transaction of 8-bytes or less. These     small transactions are uncommon, so this accounting issue has gone undetected for several years. The fix     is to use buffer_size (the allocated buffer size) instead of size (the logical buffer size) when     updating the async_free_space during the free operation. These are the same except for this corner case of     asynchronous transactions with payloads < 8 bytes. (CVE-2021-46935)

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

ID	Name	Product	Family	Published	Updated	Severity
246200	Linux Distros 未修補的弱點：CVE-2021-46935	Nessus	Misc.	8/8/2025	9/30/2025	medium
246200	Linux Distros 未修补的漏洞：CVE-2021-46935	Nessus	Misc.	8/8/2025	9/30/2025	medium
246200	Linux Distros のパッチ未適用の脆弱性: CVE-2021-46935	Nessus	Misc.	8/8/2025	9/30/2025	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	9/22/2025	high
246200	Linux Distros Unpatched Vulnerability : CVE-2021-46935	Nessus	Misc.	8/8/2025	9/30/2025	medium

Detections

Analytics

Plugins Search

medium

medium

medium

high

medium