nday
CVE-2026-98694

thunderbolt: Fix KASAN reported use-after-free when request is canceled

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
10-18T15:46Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

thunderbolt: Fix KASAN reported use-after-free when request is canceled

Alan reported that when doing stress testing sometimes KASAN notices use-after-free during control channel operation (stripped down keeping the relevant parts):

BUG: KASAN: slab-use-after-free in tb_cfg_request_sync+0x240/0x250 [thunderbolt]
Read of size 24 at addr ffff88811067f290 by task kworker/u40:2/1760
 <TASK>
 tb_cfg_request_sync+0x240/0x250 [thunderbolt]
 tb_cfg_read_raw+0x367/0x510 [thunderbolt]
 tb_cfg_read+0xec/0x240 [thunderbolt]
 tb_port_get_link_generation+0x258/0x420 [thunderbolt]
 tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]
 tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]
 tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]
 tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]
 tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]
 process_one_work+0x675/0x1230
 worker_thread+0x5e6/0xf70
 kthread+0x365/0x470
 ret_from_fork+0x54d/0x710
 ret_from_fork_asm+0x1a/0x30
 </TASK>

Allocated by task 1760:
 __kmalloc_cache_noprof+0x1ee/0x550
 tb_cfg_read_raw+0x1d3/0x510 [thunderbolt]
 tb_cfg_read+0xec/0x240 [thunderbolt]
 tb_port_get_link_generation+0x258/0x420 [thunderbolt]
 tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]
 tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]
 tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]
 tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]
 tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]
 process_one_work+0x675/0x1230
 worker_thread+0x5e6/0xf70
 kthread+0x365/0x470
 ret_from_fork+0x54d/0x710
 ret_from_fork_asm+0x1a/0x30

Freed by task 926:
 kfree+0x18f/0x4a0
 tb_cfg_request_put+0xb7/0xe0 [thunderbolt]
 tb_cfg_request_work+0x82/0x120 [thunderbolt]
 process_one_work+0x675/0x1230
 worker_thread+0x5e6/0xf70
 kthread+0x365/0x470
 ret_from_fork+0x54d/0x710
 ret_from_fork_asm+0x1a/0x30

Second to last potentially related work creation:

__queue_work+0x575/0xd00
queue_work_on+0x77/0x80
tb_cfg_request_cancel+0xc7/0x260 [thunderbolt]
tb_cfg_request_sync+0x1f6/0x250 [thunderbolt]
tb_cfg_read_raw+0x367/0x510 [thunderbolt]
tb_cfg_read+0xec/0x240 [thunderbolt]
tb_port_get_link_generation+0x258/0x420 [thunderbolt]
tb_usb3_consumed_bandwidth+0x1c1/0x2c0 [thunderbolt]
tb_tunnel_consumed_bandwidth+0xfd/0x910 [thunderbolt]
tb_available_bandwidth+0x5f2/0xeb0 [thunderbolt]
tb_recalc_estimated_bandwidth+0x2a0/0x1bc0 [thunderbolt]
tb_handle_dp_bandwidth_request+0x1897/0x5e20 [thunderbolt]
process_one_work+0x675/0x1230
worker_thread+0x5e6/0xf70
kthread+0x365/0x470
ret_from_fork+0x54d/0x710
ret_from_fork_asm+0x1a/0x30

The last stack trace is helpful because it shows that we are cancelling a request and looking at tb_cfg_request_cancel() what might happen is that tb_cfg_request_work() completes right before tb_cfg_request_cancel() starts and because of this it will call schedule_work() queueing the same work to run again. However, it is already removed from the request_queue and reference count is dropped so when tb_cfg_request_work() triggers again it will access memory that is already released.

Fix this so that we first make sure a cancelled request is not handed away from tb_cfg_request_find() or scheduled to run. Then instead of relying on the worker to clean up the request we will do it in tb_cfg_request_cancel() after the work is canceled from running. Make tb_cfg_request_dequeue() release the request only if it was actually removed from the queue.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 457980,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-98694",
  "occurred_at": "2026-10-18T15:46:18.654Z",
  "observed_at": "2026-11-13T05:40:20.493151Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2026-10-18T15:46:18.654Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.