CVE-2023-53475: usb: xhci: tegra: fix sleep in atomic call
In the Linux kernel, the following vulnerability has been resolved:
usb: xhci: tegra: fix sleep in atomic call
When we set the dual-role port to Host mode, we observed the following
splat:
[ 167.057718] BUG: sleeping function called from invalid context at
include/linux/sched/mm.h:229
[ 167.057872] Workqueue: events tegra_xusb_usb_phy_work
[ 167.057954] Call trace:
[ 167.057962] dump_backtrace+0x0/0x210
[ 167.057996] show_stack+0x30/0x50
[ 167.058020] dump_stack_lvl+0x64/0x84
[ 167.058065] dump_stack+0x14/0x34
[ 167.058100] __might_resched+0x144/0x180
[ 167.058140] __might_sleep+0x64/0xd0
[ 167.058171] slab_pre_alloc_hook.constprop.0+0xa8/0x110
[ 167.058202] __kmalloc_track_caller+0x74/0x2b0
[ 167.058233] kvasprintf+0xa4/0x190
[ 167.058261] kasprintf+0x58/0x90
[ 167.058285] tegra_xusb_find_port_node.isra.0+0x58/0xd0
[ 167.058334] tegra_xusb_find_port+0x38/0xa0
[ 167.058380] tegra_xusb_padctl_get_usb3_companion+0x38/0xd0
[ 167.058430] tegra_xhci_id_notify+0x8c/0x1e0
[ 167.058473] notifier_call_chain+0x88/0x100
[ 167.058506] atomic_notifier_call_chain+0x44/0x70
[ 167.058537] tegra_xusb_usb_phy_work+0x60/0xd0
[ 167.058581] process_one_work+0x1dc/0x4c0
[ 167.058618] worker_thread+0x54/0x410
[ 167.058650] kthread+0x188/0x1b0
[ 167.058672] ret_from_fork+0x10/0x20
The function tegra_xusb_padctl_get_usb3_companion eventually calls
tegra_xusb_find_port and this in turn calls kasprintf which might sleep
and so cannot be called from an atomic context.
Fix this by moving the call to tegra_xusb_padctl_get_usb3_companion to
the tegra_xhci_id_work function where it is really needed.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53475 is a Linux kernel issue in the Tegra USB xHCI driver. Switching a dual-role USB port to Host mode can trigger an invalid sleep-in-atomic kernel warning. The public record identifies a kernel fix, but provides no CVSS score or confirmed exploitation evidence.
Executive priority
Treat as a targeted kernel maintenance item, not a broad emergency. Prioritize embedded or appliance fleets using Tegra USB dual-role ports, especially where USB role switching affects availability or field reliability.
Technical view
The vulnerable path calls tegra_xusb_padctl_get_usb3_companion from an atomic notifier context. That path reaches tegra_xusb_find_port, which calls kasprintf and may sleep. The kernel fix moves the companion lookup into tegra_xhci_id_work, where it is actually needed and not in the atomic call path.
Likely exposure
Exposure appears limited to Linux systems using the Tegra xHCI/XUSB dual-role USB functionality on affected kernel versions. General Linux servers without Tegra USB hardware or this driver path are unlikely to be exposed based on the supplied sources.
Exploitation context
The source describes reproduction when setting a dual-role port to Host mode. There is no KEV listing and no cited evidence of active exploitation. The described impact is a kernel invalid-context warning and potential device reliability issue; broader security impact is not established in the sources.
Researcher notes
The public CVE data lacks CVSS, CWE, and detailed exploitability analysis. The issue is driver-specific and tied to kernel context rules. Analysis should focus on affected kernel branches, downstream backports, and whether device configurations exercise Tegra dual-role USB Host transitions.
Mitigation direction
Update affected Linux kernels to versions containing the referenced stable fixes.
Prioritize Tegra-based devices using dual-role USB Host mode.
Use distribution or device-vendor kernel advisories for exact package guidance.
If no update is available, ask the vendor for supported mitigation guidance.
Validation and detection
Inventory Linux devices using Tegra xHCI/XUSB hardware or drivers.
Compare running kernel builds against vendor advisories and referenced stable commits.
Review kernel logs for sleep-in-atomic warnings involving tegra_xhci_id_notify.
Confirm updated kernels include the fix moving companion lookup to tegra_xhci_id_work.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53475 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 1, 2025, 11:42 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.