CVE-2026-46074: spi: ch341: fix memory leaks on probe failures
In the Linux kernel, the following vulnerability has been resolved:
spi: ch341: fix memory leaks on probe failures
Make sure to deregister the controller, disable pins, and kill and free
the RX URB on probe failures to mirror disconnect and avoid memory
leaks and use-after-free.
Also add an explicit URB kill on disconnect for symmetry (even if that
is not strictly required as USB core would have stopped it in the
current setup).
Security readout for executives and security teams
Plain-English summary
CVE-2026-46074 is a Linux kernel issue in the CH341 SPI USB driver. On certain probe failures, cleanup was incomplete, causing memory leaks and possible use-after-free. The sources do not provide CVSS, impact rating, or confirmed exploitation.
Executive priority
Treat this as a targeted Linux kernel maintenance item, not a broad emergency from current evidence. Prioritize patch tracking for systems using CH341 SPI hardware or permissive USB environments, and wait for vendor severity guidance where unavailable.
Technical view
The fix makes probe-failure cleanup mirror disconnect behavior: deregistering the controller, disabling pins, killing the RX URB, and freeing related resources. An explicit URB kill was also added on disconnect for symmetry. The available record identifies Linux kernel versions and stable commits but lacks exploitability detail.
Likely exposure
Exposure is most relevant to Linux systems with affected kernels where the CH341 SPI driver can be used. Practical exposure depends on kernel build, device availability, and distribution backports, which are not fully detailed in the sources.
Exploitation context
The source bundle does not report active exploitation, KEV listing, public exploit code, or attacker prerequisites. The issue appears tied to driver probe-failure cleanup, but the sources do not establish whether exploitation is local, physical, or otherwise reachable.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. Key missing data includes CVSS, CWE, exact affected branch ranges, attacker model, and proof of exploitability. Avoid assuming remote reachability or active exploitation.
Mitigation direction
Review vendor or distribution advisories for fixed kernel packages.
Prioritize systems using CH341 SPI or related USB hardware.
Upgrade to a kernel containing the cited stable fixes.
Apply normal controls for untrusted peripheral attachment where relevant.
Validation and detection
Inventory Linux kernel versions across affected assets.
Check whether the CH341 SPI driver is built or loadable.
Confirm distribution kernels include one of the cited fixes or backports.
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-2026-46074 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:58 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.