CVEvulnerability

CVE-2025-38174

5.5 MEDIUM Published 2025-07-04 Modified 2026-07-30 Official page ↗
Status
Modified
Published
2025-07-04
Last modified
2026-07-30
Assigner
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS 3.1 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)
8.8 HIGH — CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 3.1 ([email protected])
5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Description

In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Do not double dequeue a configuration request Some of our devices crash in tb_cfg_request_dequeue(): general protection fault, probably for non-canonical address 0xdead000000000122 CPU: 6 PID: 91007 Comm: kworker/6:2 Tainted: G U W 6.6.65 RIP: 0010:tb_cfg_request_dequeue+0x2d/0xa0 Call Trace: <TASK> ? tb_cfg_request_dequeue+0x2d/0xa0 tb_cfg_request_work+0x33/0x80 worker_thread+0x386/0x8f0 kthread+0xed/0x110 ret_from_fork+0x38/0x50 ret_from_fork_asm+0x1b/0x30 The circumstances are unclear, however, the theory is that tb_cfg_request_work() can be scheduled twice for a request: first time via frame.callback from ring_work() and second time from tb_cfg_request(). Both times kworkers will execute tb_cfg_request_dequeue(), which results in double list_del() from the ctl->request_queue (the list poison deference hints at it: 0xdead000000000122). Do not dequeue requests that don't have TB_CFG_REQUEST_ACTIVE bit set.

Affected configurations

• linux linux kernel (>= 3.17 < 5.4.295) • linux linux kernel (>= 5.5 < 5.10.239) • linux linux kernel (>= 5.11 < 5.15.186) • linux linux kernel (>= 5.16 < 6.1.142) • linux linux kernel (>= 6.2 < 6.6.94) • linux linux kernel (>= 6.7 < 6.12.33) • linux linux kernel (>= 6.13 < 6.14.11) • linux linux kernel (>= 6.15 < 6.15.2) • debian debian linux 11.0

References