The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-986840 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL

    There exists a possible scenario in which dwc3_gadget_init() can fail:
    during during host -> peripheral mode switch in dwc3_set_mode(), and     a pending gadget driver fails to bind.  Then, if the DRD undergoes     another mode switch from peripheral->host the resulting     dwc3_gadget_exit() will attempt to reference an invalid and dangling     dwc->gadget pointer as well as call dma_free_coherent() on unmapped     DMA pointers.

    The exact scenario can be reproduced as follows:
     - Start DWC3 in peripheral mode
     - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs)
     - Run FunctionFS userspace application (open EPs, write descriptors, etc)
     - Bind gadget driver to DWC3's UDC
     - Switch DWC3 to host mode        => dwc3_gadget_exit() is called. usb_del_gadget() will put the             ConfigFS driver instance on the gadget_driver_pending_list
     - Stop FunctionFS application (closes the ep files)
     - Switch DWC3 to peripheral mode        => dwc3_gadget_init() fails as usb_add_gadget() calls             check_pending_gadget_drivers() and attempts to rebind the UDC             to the ConfigFS gadget but fails with -19 (-ENODEV) because the             FFS instance is not in FFS_ACTIVE state (userspace has not             re-opened and written the descriptors yet, i.e. desc_ready!=0).
     - Switch DWC3 back to host mode        => dwc3_gadget_exit() is called again, but this time dwc->gadget             is invalid.

    Although it can be argued that userspace should take responsibility     for ensuring that the FunctionFS application be ready prior to     allowing the composite driver bind to the UDC, failure to do so     should not result in a panic from the kernel driver.

    Fix this by setting dwc->gadget to NULL in the failure path of     dwc3_gadget_init() and add a check to dwc3_gadget_exit() to bail out     unless the gadget pointer is valid.

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

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

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

  - Linux カーネルにおいて、以下の脆弱性は解決されました： usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL There exists a possible scenario in which dwc3_gadget_init() can fail: during during host -> peripheral mode switch in dwc3_set_mode(), and a pending gadget driver fails to bind. Then, if the DRD undergoes another mode switch from peripheral->host the resulting dwc3_gadget_exit() will attempt to reference an invalid and dangling dwc->gadget pointer as well as call dma_free_coherent() on unmapped DMA pointers. The exact scenario can be reproduced as follows: - Start DWC3 in peripheral mode - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs) - Run FunctionFS userspace application (open EPs, write descriptors, etc) - Bind gadget driver to DWC3's UDC - Switch DWC3 to host mode => dwc3_gadget_exit() is called. usb_del_gadget() will put the ConfigFS driver instance on the gadget_driver_pending_list - Stop FunctionFS application (closes the ep files) - Switch DWC3 to peripheral mode => dwc3_gadget_init() fails as usb_add_gadget() calls check_pending_gadget_drivers() and attempts to rebind the UDC to the ConfigFS gadget but fails with -19 (-ENODEV) because the FFS instance is not in FFS_ACTIVE state (userspace has not re-opened and written the descriptors yet, i.e. desc_ready!=0). - Switch DWC3 back to host mode => dwc3_gadget_exit() is called again, but this time dwc->gadget is invalid. Although it can be argued that userspace should take responsibility for ensuring that the FunctionFS application be ready prior to allowing the composite driver bind to the UDC, failure to do so should not result in a panic from the kernel driver. Fix this by setting dwc->gadget to NULL in the failure path of dwc3_gadget_init() and add a check to dwc3_gadget_exit() to bail out unless the gadget pointer is valid. (CVE-2021-47272)

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

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

  - 在 Linux 内核中，已解决以下漏洞： usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL There exists a possible scenario in which dwc3_gadget_init() can fail: during during host -> peripheral mode switch in dwc3_set_mode(), and a pending gadget driver fails to bind. Then, if the DRD undergoes another mode switch from peripheral->host the resulting dwc3_gadget_exit() will attempt to reference an invalid and dangling dwc->gadget pointer as well as call dma_free_coherent() on unmapped DMA pointers. The exact scenario can be reproduced as follows: - Start DWC3 in peripheral mode - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs) - Run FunctionFS userspace application (open EPs, write descriptors, etc) - Bind gadget driver to DWC3's UDC - Switch DWC3 to host mode => dwc3_gadget_exit() is called. usb_del_gadget() will put the ConfigFS driver instance on the gadget_driver_pending_list - Stop FunctionFS application (closes the ep files) - Switch DWC3 to peripheral mode => dwc3_gadget_init() fails as usb_add_gadget() calls check_pending_gadget_drivers() and attempts to rebind the UDC to the ConfigFS gadget but fails with -19 (-ENODEV) because the FFS instance is not in FFS_ACTIVE state (userspace has not re-opened and written the descriptors yet, i.e. desc_ready!=0). - Switch DWC3 back to host mode => dwc3_gadget_exit() is called again, but this time dwc->gadget is invalid. Although it can be argued that userspace should take responsibility for ensuring that the FunctionFS application be ready prior to allowing the composite driver bind to the UDC, failure to do so should not result in a panic from the kernel driver. Fix this by setting dwc->gadget to NULL in the failure path of dwc3_gadget_init() and add a check to dwc3_gadget_exit() to bail out unless the gadget pointer is valid. (CVE-2021-47272)

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

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

  - 在 Linux 核心中，已解決下列弱點： usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL There exists a possible scenario in which dwc3_gadget_init() can fail: during during host -> peripheral mode switch in dwc3_set_mode(), and a pending gadget driver fails to bind. Then, if the DRD undergoes another mode switch from peripheral->host the resulting dwc3_gadget_exit() will attempt to reference an invalid and dangling dwc->gadget pointer as well as call dma_free_coherent() on unmapped DMA pointers. The exact scenario can be reproduced as follows: - Start DWC3 in peripheral mode - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs) - Run FunctionFS userspace application (open EPs, write descriptors, etc) - Bind gadget driver to DWC3's UDC - Switch DWC3 to host mode => dwc3_gadget_exit() is called. usb_del_gadget() will put the ConfigFS driver instance on the gadget_driver_pending_list - Stop FunctionFS application (closes the ep files) - Switch DWC3 to peripheral mode => dwc3_gadget_init() fails as usb_add_gadget() calls check_pending_gadget_drivers() and attempts to rebind the UDC to the ConfigFS gadget but fails with -19 (-ENODEV) because the FFS instance is not in FFS_ACTIVE state (userspace has not re-opened and written the descriptors yet, i.e. desc_ready!=0). - Switch DWC3 back to host mode => dwc3_gadget_exit() is called again, but this time dwc->gadget is invalid. Although it can be argued that userspace should take responsibility for ensuring that the FunctionFS application be ready prior to allowing the composite driver bind to the UDC, failure to do so should not result in a panic from the kernel driver. Fix this by setting dwc->gadget to NULL in the failure path of dwc3_gadget_init() and add a check to dwc3_gadget_exit() to bail out unless the gadget pointer is valid. (CVE-2021-47272)

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

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: usb: dwc3: gadget: Bail from     dwc3_gadget_exit() if dwc->gadget is NULL There exists a possible scenario in which dwc3_gadget_init() can     fail: during during host -> peripheral mode switch in dwc3_set_mode(), and a pending gadget driver fails     to bind. Then, if the DRD undergoes another mode switch from peripheral->host the resulting     dwc3_gadget_exit() will attempt to reference an invalid and dangling dwc->gadget pointer as well as call     dma_free_coherent() on unmapped DMA pointers. The exact scenario can be reproduced as follows: - Start     DWC3 in peripheral mode - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs) - Run     FunctionFS userspace application (open EPs, write descriptors, etc) - Bind gadget driver to DWC3's UDC -     Switch DWC3 to host mode => dwc3_gadget_exit() is called. usb_del_gadget() will put the ConfigFS driver     instance on the gadget_driver_pending_list - Stop FunctionFS application (closes the ep files) - Switch     DWC3 to peripheral mode => dwc3_gadget_init() fails as usb_add_gadget() calls     check_pending_gadget_drivers() and attempts to rebind the UDC to the ConfigFS gadget but fails with -19     (-ENODEV) because the FFS instance is not in FFS_ACTIVE state (userspace has not re-opened and written the     descriptors yet, i.e. desc_ready!=0). - Switch DWC3 back to host mode => dwc3_gadget_exit() is called     again, but this time dwc->gadget is invalid. Although it can be argued that userspace should take     responsibility for ensuring that the FunctionFS application be ready prior to allowing the composite     driver bind to the UDC, failure to do so should not result in a panic from the kernel driver. Fix this by     setting dwc->gadget to NULL in the failure path of dwc3_gadget_init() and add a check to     dwc3_gadget_exit() to bail out unless the gadget pointer is valid. (CVE-2021-47272)

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988904 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL

    There exists a possible scenario in which dwc3_gadget_init() can fail:
    during during host -> peripheral mode switch in dwc3_set_mode(), and     a pending gadget driver fails to bind.  Then, if the DRD undergoes     another mode switch from peripheral->host the resulting     dwc3_gadget_exit() will attempt to reference an invalid and dangling     dwc->gadget pointer as well as call dma_free_coherent() on unmapped     DMA pointers.

    The exact scenario can be reproduced as follows:
     - Start DWC3 in peripheral mode
     - Configure ConfigFS gadget with FunctionFS instance (or use g_ffs)
     - Run FunctionFS userspace application (open EPs, write descriptors, etc)
     - Bind gadget driver to DWC3's UDC
     - Switch DWC3 to host mode        => dwc3_gadget_exit() is called. usb_del_gadget() will put the             ConfigFS driver instance on the gadget_driver_pending_list
     - Stop FunctionFS application (closes the ep files)
     - Switch DWC3 to peripheral mode        => dwc3_gadget_init() fails as usb_add_gadget() calls             check_pending_gadget_drivers() and attempts to rebind the UDC             to the ConfigFS gadget but fails with -19 (-ENODEV) because the             FFS instance is not in FFS_ACTIVE state (userspace has not             re-opened and written the descriptors yet, i.e. desc_ready!=0).
     - Switch DWC3 back to host mode        => dwc3_gadget_exit() is called again, but this time dwc->gadget             is invalid.

    Although it can be argued that userspace should take responsibility     for ensuring that the FunctionFS application be ready prior to     allowing the composite driver bind to the UDC, failure to do so     should not result in a panic from the kernel driver.

    Fix this by setting dwc->gadget to NULL in the failure path of     dwc3_gadget_init() and add a check to dwc3_gadget_exit() to bail out     unless the gadget pointer is valid.

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

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

ID	Name	Product	Family	Published	Updated	Severity
268709	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986840)	Nessus	Unity Linux Local Security Checks	10/7/2025	10/15/2025	medium
229869	Linux Distros のパッチ未適用の脆弱性: CVE-2021-47272	Nessus	Misc.	3/5/2025	9/14/2025	medium
229869	Linux Distros 未修补的漏洞: CVE-2021-47272	Nessus	Misc.	3/5/2025	9/14/2025	medium
229869	Linux Distros 未修補弱點：CVE-2021-47272	Nessus	Misc.	3/5/2025	9/14/2025	medium
229869	Linux Distros Unpatched Vulnerability : CVE-2021-47272	Nessus	Misc.	3/5/2025	9/14/2025	medium
273829	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988904)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium

Detections

Analytics

Plugins Search

medium

medium

medium

medium

medium

medium