CVE-2026-46074

NONECVSS 0.0

0.0

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).

CVSS v3: —
EG Score: 0.0(none)
EPSS: 4.9%
KEV: Not listed

Published

May 27, 2026

Last Modified

May 27, 2026

References (4)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/5c6518633702d7f7b1153e9d8e042af847f11ef3
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9bee2faf9e21c796d0d222c9d84a98f41bd303a0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b99e3ddb91b499d920e63a2daff8880be68cfe9e
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ff8a7996dc8bf433efe2126ffdaee5b374a89e30

Vendor Advisories for CVE-2026-46074(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

GHSA-rv45-g592-f3p6
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: spi: ch341: fix memory leaks...

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 14:08 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-46074?

CVE-2026-46074 is a none vulnerability published on May 27, 2026. 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…

When was CVE-2026-46074 disclosed?

CVE-2026-46074 was first published in the National Vulnerability Database on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-46074 actively exploited?

CVE-2026-46074 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2026-46074?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46074, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46074

Explore →

Is Your Infrastructure Affected by CVE-2026-46074?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-46074

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2026-46074(1)