Answer in brief
CVE-2025-38174 records a Unknown severity vulnerability in thunderbolt: Do not double dequeue a configuration request. 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.
Answer in brief
CVE-2025-38174 records a Unknown severity vulnerability in thunderbolt: Do not double dequeue a configuration request. 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 | >=16603153666d22df544ae9f9b3764fd18da28eeb <e49e994cd83705f7ca30eda1e304abddfd96a37a || >=16603153666d22df544ae9f9b3764fd18da28eeb <0a3011d47dbc92a33621861c423cb64833d7fe57 || >=16603153666d22df544ae9f9b3764fd18da28eeb <2f62eda4d974c26bc595425eafd429067541f2c9 || >=16603153666d22df544ae9f9b3764fd18da28eeb <85286e634ebbaf9c0fb1cdf580add2f33fc7628c || >=16603153666d22df544ae9f9b3764fd18da28eeb <5a057f261539720165d03d85024da2b52e67f63d || >=16603153666d22df544ae9f9b3764fd18da28eeb <eb2d5e794fb966b3ef8bde99eb8561446a53509f || >=16603153666d22df544ae9f9b3764fd18da28eeb <0771bcbe2f6e5d5f263cf466efe571d2754a46da || >=16603153666d22df544ae9f9b3764fd18da28eeb <cdb4feab2f39e75a66239e3a112beced279612a8 || >=16603153666d22df544ae9f9b3764fd18da28eeb <0f73628e9da1ee39daf5f188190cdbaee5e0c98c | e49e994cd83705f7ca30eda1e304abddfd96a37a, 0a3011d47dbc92a33621861c423cb64833d7fe57, 2f62eda4d974c26bc595425eafd429067541f2c9, 85286e634ebbaf9c0fb1cdf580add2f33fc7628c, 5a057f261539720165d03d85024da2b52e67f63d, eb2d5e794fb966b3ef8bde99eb8561446a53509f, 0771bcbe2f6e5d5f263cf466efe571d2754a46da, cdb4feab2f39e75a66239e3a112beced279612a8, 0f73628e9da1ee39daf5f188190cdbaee5e0c98c |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Jul 4, 2025
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: 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.
Quoted source text, attributed separately from HOL analysis.
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 | >=16603153666d22df544ae9f9b3764fd18da28eeb <e49e994cd83705f7ca30eda1e304abddfd96a37a || >=16603153666d22df544ae9f9b3764fd18da28eeb <0a3011d47dbc92a33621861c423cb64833d7fe57 || >=16603153666d22df544ae9f9b3764fd18da28eeb <2f62eda4d974c26bc595425eafd429067541f2c9 || >=16603153666d22df544ae9f9b3764fd18da28eeb <85286e634ebbaf9c0fb1cdf580add2f33fc7628c || >=16603153666d22df544ae9f9b3764fd18da28eeb <5a057f261539720165d03d85024da2b52e67f63d || >=16603153666d22df544ae9f9b3764fd18da28eeb <eb2d5e794fb966b3ef8bde99eb8561446a53509f || >=16603153666d22df544ae9f9b3764fd18da28eeb <0771bcbe2f6e5d5f263cf466efe571d2754a46da || >=16603153666d22df544ae9f9b3764fd18da28eeb <cdb4feab2f39e75a66239e3a112beced279612a8 || >=16603153666d22df544ae9f9b3764fd18da28eeb <0f73628e9da1ee39daf5f188190cdbaee5e0c98c | e49e994cd83705f7ca30eda1e304abddfd96a37a, 0a3011d47dbc92a33621861c423cb64833d7fe57, 2f62eda4d974c26bc595425eafd429067541f2c9, 85286e634ebbaf9c0fb1cdf580add2f33fc7628c, 5a057f261539720165d03d85024da2b52e67f63d, eb2d5e794fb966b3ef8bde99eb8561446a53509f, 0771bcbe2f6e5d5f263cf466efe571d2754a46da, cdb4feab2f39e75a66239e3a112beced279612a8, 0f73628e9da1ee39daf5f188190cdbaee5e0c98c |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Jul 4, 2025
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: 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.
Quoted source text, attributed separately from HOL analysis.