cve.bz

CVE-2026-74575 linux linux

8.8 highEPSS 0.2%Fix available

High (8.8) in linux linux. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: thunderbolt: Prevent XDomain delayed work use-after-free on disconnect tb_xdp_handle_request() runs on system_wq and queues xd->state_work via queue_delayed_work() in three request handlers: PROPERTIES_CHANGED_REQUEST, UUID_REQUEST (via start_handshake), and LINK_STATE_CHANGE_REQUEST. Similarly, update_xdomain() queues xd->properties_changed_work when local properties change. Concurrently, tb_xdomain_remove() calls stop_handshake() which does cancel_delayed_work_sync() on both delayed works. Later, tb_xdomain_unregister() calls device_unregister() which eventually frees the xdomain. Since commit 559c1e1e0134 ("thunderbolt: Run tb_xdp_handle_request() in system workqueue") moved the request handler off tb->wq, the handler and the remove path are no longer serialized. If queue_delayed_work() executes after cancel_delayed_work_sync() but before the xdomain is freed, the delayed work fires on a freed object. Add xd->removing that tb_xdomain_remove() sets under xd->lock before calling stop_handshake(). Each external queue site holds the same lock and checks removing before calling queue_delayed_work(). This provides the mutual exclusion needed: either the queue site acquires the lock first and queues work that the subsequent cancel will see, or the remove path acquires the lock first and the queue site observes removing == true and skips the queue.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 5.10.266
  • Linux Linux: fixed in 5.15.217
  • Linux Linux: fixed in 6.1.184
  • Linux Linux: fixed in 6.6.151
  • Linux Linux: fixed in 6.12.103
  • Linux Linux: fixed in 6.18.44
  • Linux Linux: fixed in 7.1.8
  • Linux Linux: fixed in 7.2
  • Debian, Ubuntu, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-74575 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-74575?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-74575?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-74575 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux5.2 and later

Fixed in

ProductRelease lineFixed in
Linux5.105.10.266
Linux5.155.15.217
Linux6.16.1.184
Linux6.66.6.151
Linux6.126.12.103
Linux6.186.18.44
Linux7.17.1.8
Linuxlater releases7.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux6.1.187-1DEBIAN-CVE-2026-74575
Debian12linux-6.126.12.107-1~deb12u1DEBIAN-CVE-2026-74575
Debian13linux6.12.105-1DEBIAN-CVE-2026-74575
Debian14linux7.1.8-1DEBIAN-CVE-2026-74575
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-74575
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-74575
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-74575
Ubuntu22.04:LTSlinux5.15.0-202.212UBUNTU-CVE-2026-74575 USN-8961-1
Ubuntu22.04:LTSlinux-aws5.15.0-1119.126UBUNTU-CVE-2026-74575 USN-8961-1
Ubuntu22.04:LTSlinux-aws-6.86.8.0-1069.74~22.04.1UBUNTU-CVE-2026-74575 USN-9024-1
Ubuntu22.04:LTSlinux-azure5.15.0-1125.134UBUNTU-CVE-2026-74575 USN-8961-1
Ubuntu22.04:LTSlinux-azure-6.86.8.0-1073.82~22.04.1UBUNTU-CVE-2026-74575 USN-9026-1
Ubuntu22.04:LTSlinux-azure-fde5.15.0-1124.133UBUNTU-CVE-2026-74575
Ubuntu22.04:LTSlinux-azure-fde-6.86.8.0-1071.78~22.04.1UBUNTU-CVE-2026-74575 USN-9026-1
Ubuntu22.04:LTSlinux-gcp5.15.0-1120.130UBUNTU-CVE-2026-74575 USN-8961-1
Ubuntu22.04:LTSlinux-gcp-6.86.8.0-1073.81~22.04.1UBUNTU-CVE-2026-74575 USN-9024-1
81 more for Ubuntu in the JSON and on Ubuntu's page.
Alpaquita23linux-lts6.1.189-r0BELL-CVE-2026-74575
Alpaquita25linux-lts6.12.103-r0BELL-CVE-2026-74575
Alpaquitastreamlinux-lts6.18.46-r0BELL-CVE-2026-74575

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Thunderbolt XDomain delayed work can be queued after tb_xdomain_remove has already canceled pending work but before device_unregister frees the xdomain object. A remote peer on the Thunderbolt/USB4 link can send XDomain requests such as PROPERTIES_CHANGED_REQUEST, UUID_REQUEST, or LINK_STATE_CHANGE_REQUEST while disconnect handling is running, creating a race where state_work or properties_changed_work later runs on freed memory. For the CVSS the PR:N is used because the attacker does not need a local account or privileges on the victim host, but does need access to a connected Thunderbolt/USB4 peer or device path. The issue is not Internet network reachable and is best treated as physical or adjacent bus reachable. Impact is at least denial of service via kernel crash. Because this is a real use after free in kernel delayed work, worst case confidentiality and integrity impact are plausible and should be reviewed manually.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-74575.

References

Check your stackJSON