LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38174: thunderbolt: Do not double dequeue a configuration request

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux Thunderbolt request-handling flaw can remove the same queued request twice, corrupting kernel state and crashing the system. The supplied severity is high, with CVSS 8.8. The source directly documents crashes; broader confidentiality or integrity impact is assessed by the CVSS vector but not demonstrated in the description.

Executive priority

Treat as an expedited kernel-maintenance issue for Thunderbolt-capable systems, especially operationally critical endpoints. It does not currently warrant an exploitation-driven emergency response because active exploitation is unsupported, but the documented kernel crash creates meaningful availability risk.

Technical view

Two worker paths may schedule the same configuration request and both call tb_cfg_request_dequeue(), causing a double list deletion and poisoned-pointer dereference. The kernel fix prevents dequeueing unless TB_CFG_REQUEST_ACTIVE is set. The triggering circumstances remain unclear.

Likely exposure

Exposure is concentrated on systems running affected Linux kernel branches with the Thunderbolt subsystem and relevant devices. The bundle spans multiple kernel versions but does not provide sufficient distribution-package mapping; administrators should verify exact exposure through their Linux vendor.

Exploitation context

The supplied CVSS vector requires adjacent access but no privileges or user interaction. CISA KEV status is false, and the sources provide no evidence of active exploitation or a public exploit. Reliable triggering is uncertain because the reported circumstances were unclear.

Researcher notes

The proposed root cause is duplicate scheduling through frame.callback and tb_cfg_request(), followed by two dequeue operations. The poisoned address supports a double-list-deletion theory. Sources do not establish deterministic reproduction, attacker control, privilege escalation, or exploitation beyond the observed kernel crash.

Mitigation direction

  • Install a vendor kernel update containing the referenced Linux stable fix.
  • Reboot affected systems so the corrected kernel is actually running.
  • Prioritize systems using Thunderbolt hardware or exposing Thunderbolt connectivity.
  • Consult distribution guidance when package-to-kernel commit mapping is uncertain.

Validation and detection

  • Inventory running kernel versions and identify systems using the Thunderbolt subsystem.
  • Compare installed vendor packages with advisories covering CVE-2025-38174.
  • Confirm the running kernel contains the active-request dequeue guard after reboot.
  • Review kernel logs for tb_cfg_request_dequeue faults, list poisoning, or related kworker crashes.
Prepared
Confidence
medium
Sources
6

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-2025-38174 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
12Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-38174Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eeb, 16603153666d22df544ae9f9b3764fd18da28eebunaffected
LinuxLinux3.17, 0, 5.4.295, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.33, 6.14.11, 6.15.2, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.