CVE-2026-46226

NONECVSS 0.0

0.0

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

spi: fsl: fix controller deregistration

Make sure to deregister the controller before releasing underlying resources like DMA during driver unbind.

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

Published

May 28, 2026

Last Modified

May 28, 2026

References (5)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/562d954a144950ec2aa6a874ae657cb3fa31fe53
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/5750743a39c9d46ac9fcf57ffe000956da4942cf
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/9b7abfed4c3754062d1f3ffd452e65a38667f586
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/ca3195c7b88362d7c81efe685948663a9f9db0e6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e888308222375ac28bae69134dae288178718a96

Vendor Advisories for CVE-2026-46226(1)

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

GHSA-h384-m94j-8hmh
GitHub Security Advisoriesunknown
In the Linux kernel, the following vulnerability has been resolved: spi: fsl: fix controller...

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-28 10:09 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-46226?

CVE-2026-46226 is a none vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: fsl: fix controller deregistration Make sure to deregister the controller before releasing underlying resources like DMA during driver unbind.

When was CVE-2026-46226 disclosed?

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

Is CVE-2026-46226 actively exploited?

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

How do I remediate CVE-2026-46226?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46226, 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-46226

Explore →

Is Your Infrastructure Affected by CVE-2026-46226?

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

Start Free Scan →Browse All CVEs

CVE-2026-46226

📅 Published

🔄 Last Modified

🔗 References (5)

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