CVE-2023-53475
BaseFortify
Publication date: 2025-10-01
Last updated on: 2025-10-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nvidia | tegra_xhci | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's USB subsystem for Tegra devices. Specifically, when setting the dual-role USB port to Host mode, a function that may sleep (kasprintf) is called from an atomic context, which is invalid and causes a kernel bug (crash). The issue arises because the function tegra_xusb_padctl_get_usb3_companion calls tegra_xusb_find_port, which calls kasprintf that can sleep, but this call happens in an atomic context where sleeping is not allowed. The fix involved moving this call to a different function (tegra_xhci_id_work) where sleeping is permitted.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or become unstable when the affected USB port is set to Host mode on Tegra devices. This can lead to system instability, potential denial of service, and disruption of USB functionality.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by checking your system logs for the specific kernel BUG message related to sleeping function called from invalid context in the tegra xhci driver. Use the command: dmesg | grep -i 'BUG: sleeping function called from invalid context' to look for the error trace indicating the issue when setting the dual-role port to Host mode.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation is to update your Linux kernel to a version that includes the fix for this vulnerability, where the call to tegra_xusb_padctl_get_usb3_companion is moved to the correct work function (tegra_xhci_id_work) to avoid sleeping in atomic context. Until then, avoid setting the dual-role port to Host mode on affected Tegra systems to prevent triggering the bug.