CVE-2026-74441: usb: typec: ucsi: Fix race condition and ordering in port unregistration
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 07f8aaffee705e552c1f723ac8bf7eb137ad59c2, 11483d80267db97fbe49f2df66385434256cc3b0, 3f7b3728dd9011c915cbeaea77274ebe8366550d.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 07f8aaffee705e552c1f723ac8bf7eb137ad59c2, 11483d80267db97fbe49f2df66385434256cc3b0, 3f7b3728dd9011c915cbeaea77274ebe8366550d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: Fix race condition and ordering in port unregistration A synchronization issue exists during port unregistration where pending partner work items can race against workqueue destruction, leading to use-after-free conditions: cros_ec_ucsi cros_ec_ucsi.3.auto: error -ETIMEDOUT: PPM init failed BUG: kernel NULL pointer dereference, address: 0000000000000000 RIP: 0010:__queue_work+0x83/0x4a0 Call Trace: <IRQ> __cfi_delayed_work_timer_fn+0x10/0x10 run_timer_softirq+0x3b6/0xbd0 sched_clock_cpu+0xc/0x110 irq_exit_rcu+0x18d/0x330 fred_sysvec_apic_timer_interrupt+0x5e/0x80 Fix this by ensuring strict ordering and proper serialization during teardown: 1. Move ucsi_unregister_partner() to the beginning of the teardown sequence and protect it under the connector mutex lock. 2. Ensure all pending partner tasks are explicitly flushed and finished before the workqueue is destroyed. 3. Switch from mod_delayed_work() to a cancel_delayed_work() and queue_delayed_work() sequence. This guarantees that items currently marked as pending won't be scheduled an additional time, preventing a double release of resources which leads to the following crash: Oops: general protection fault, probably for non-canonical address 0xdead000000000122: 0000 [#1] SMP NOPTI Workqueue: cros_ec_ucsi.3.auto-con2 ucsi_poll_worker RIP: 0010:ucsi_poll_worker+0x65/0x1e0 Call Trace: <TASK> process_scheduled_works+0x218/0x6d0 worker_thread+0x188/0x3f0 __cfi_worker_thread+0x10/0x10 kthread+0x226/0x2a0 To ensure these rules are applied identically across both the normal teardown and the ucsi_init() error paths, consolidate the cleanup logic into a new helper, ucsi_unregister_port().
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.16affected
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before 7b63c680ff605f60f056e5f2c323f1a602aee182affected · git
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before 07f8aaffee705e552c1f723ac8bf7eb137ad59c2affected · git
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before 11483d80267db97fbe49f2df66385434256cc3b0affected · git
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before 3f7b3728dd9011c915cbeaea77274ebe8366550daffected · git
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before bc7a0f721123ea260a42f1ded06dab844ba49434affected · git
- b9aa02ca39a49740926c2c450a1505a4a0f8954a and later · before 7aa7d4bf9d3fa9a6a47b640ad103ab433b7ff261affected · git
- before 5.16not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.151 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74436Aug 15, 2026 · rxrpc: serialize kernel accept preallocation with socket teardown39Monitor
- ← EarlierCVE-2026-74439Aug 15, 2026 · iommu/vt-d: Clear Present bit before tearing down scalable-mode context entry37Monitor
- Later →CVE-2026-74442Aug 15, 2026 · drm/vmwgfx: avoid destroy_workqueue(NULL) on vkms init failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 07f8aaffee705e552c1f723ac8bf7eb137ad59c2 | Vendor (CNA) |
| Linux Linux | 11483d80267db97fbe49f2df66385434256cc3b0 | Vendor (CNA) |
| Linux Linux | 3f7b3728dd9011c915cbeaea77274ebe8366550d | Vendor (CNA) |
| Linux Linux | 7aa7d4bf9d3fa9a6a47b640ad103ab433b7ff261 | Vendor (CNA) |
| Linux Linux | 7b63c680ff605f60f056e5f2c323f1a602aee182 | Vendor (CNA) |
| Linux Linux | bc7a0f721123ea260a42f1ded06dab844ba49434 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/11483d80267db97fbe49f2df66385434256cc3b0
- git.kernel.org/stable/c/3f7b3728dd9011c915cbeaea77274ebe8366550d
- git.kernel.org/stable/c/7aa7d4bf9d3fa9a6a47b640ad103ab433b7ff261
- git.kernel.org/stable/c/7b63c680ff605f60f056e5f2c323f1a602aee182
- git.kernel.org/stable/c/bc7a0f721123ea260a42f1ded06dab844ba49434
Vendor advisories and official records. Exploit/PoC links are deliberately left out.