Answer in brief
CVE-2024-36977 records a Unknown severity vulnerability in usb: dwc3: Wait unconditionally after issuing EndXfer command. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <341eb08dbca9eae05308c442fbfab1813a44c97a || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <ec96bcf5f96a7a5c556b0e881ac3e5c3924d542c || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <4a387e032909c6dc2b479452c5bbe9a252057925 || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <1ba145f05b5c8f0b1a947a0633b5edff5dd1f1c5 || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <1d26ba0944d398f88aaf997bda3544646cf21945 | 341eb08dbca9eae05308c442fbfab1813a44c97a, ec96bcf5f96a7a5c556b0e881ac3e5c3924d542c, 4a387e032909c6dc2b479452c5bbe9a252057925, 1ba145f05b5c8f0b1a947a0633b5edff5dd1f1c5, 1d26ba0944d398f88aaf997bda3544646cf21945 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Jun 18, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Wait unconditionally after issuing EndXfer command Currently all controller IP/revisions except DWC3_usb3 >= 310a wait 1ms unconditionally for ENDXFER completion when IOC is not set. This is because DWC_usb3 controller revisions >= 3.10a supports GUCTL2[14: Rst_actbitlater] bit which allows polling CMDACT bit to know whether ENDXFER command is completed. Consider a case where an IN request was queued, and parallelly soft_disconnect was called (due to ffs_epfile_release). This eventually calls stop_active_transfer with IOC cleared, hence send_gadget_ep_cmd() skips waiting for CMDACT cleared during EndXfer. For DWC3 controllers with revisions >= 310a, we don't forcefully wait for 1ms either, and we proceed by unmapping the requests. If ENDXFER didn't complete by this time, it leads to SMMU faults since the controller would still be accessing those requests. Fix this by ensuring ENDXFER completion by adding 1ms delay in __dwc3_stop_active_transfer() unconditionally.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-36977 records a Unknown severity vulnerability in usb: dwc3: Wait unconditionally after issuing EndXfer command. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <341eb08dbca9eae05308c442fbfab1813a44c97a || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <ec96bcf5f96a7a5c556b0e881ac3e5c3924d542c || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <4a387e032909c6dc2b479452c5bbe9a252057925 || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <1ba145f05b5c8f0b1a947a0633b5edff5dd1f1c5 || >=b353eb6dc285a0775a447f53e5b2a50bf3f9684f <1d26ba0944d398f88aaf997bda3544646cf21945 | 341eb08dbca9eae05308c442fbfab1813a44c97a, ec96bcf5f96a7a5c556b0e881ac3e5c3924d542c, 4a387e032909c6dc2b479452c5bbe9a252057925, 1ba145f05b5c8f0b1a947a0633b5edff5dd1f1c5, 1d26ba0944d398f88aaf997bda3544646cf21945 |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
Jun 18, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: Wait unconditionally after issuing EndXfer command Currently all controller IP/revisions except DWC3_usb3 >= 310a wait 1ms unconditionally for ENDXFER completion when IOC is not set. This is because DWC_usb3 controller revisions >= 3.10a supports GUCTL2[14: Rst_actbitlater] bit which allows polling CMDACT bit to know whether ENDXFER command is completed. Consider a case where an IN request was queued, and parallelly soft_disconnect was called (due to ffs_epfile_release). This eventually calls stop_active_transfer with IOC cleared, hence send_gadget_ep_cmd() skips waiting for CMDACT cleared during EndXfer. For DWC3 controllers with revisions >= 310a, we don't forcefully wait for 1ms either, and we proceed by unmapping the requests. If ENDXFER didn't complete by this time, it leads to SMMU faults since the controller would still be accessing those requests. Fix this by ensuring ENDXFER completion by adding 1ms delay in __dwc3_stop_active_transfer() unconditionally.
Quoted source text, attributed separately from HOL analysis.