LiveActive security incident?Get immediate response
CVE Record

CVE-2026-46219: spi: mpc52xx: fix use-after-free on unbind

In the Linux kernel, the following vulnerability has been resolved: spi: mpc52xx: fix use-after-free on unbind The state machine work is scheduled by the interrupt handler and therefore needs to be cancelled after disabling interrupts to avoid a potential use-after-free.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-46219 is a Linux kernel use-after-free in the MPC52xx SPI driver during device unbind. It is most relevant to specialized systems using that driver. The public record does not provide CVSS, CWE, practical impact, or exploitation evidence.

Executive priority

Handle through normal kernel patch governance unless asset inventory shows critical embedded systems using MPC52xx SPI. Escalate if the driver is present on safety, operational, or difficult-to-maintain equipment.

Technical view

The interrupt handler can schedule state-machine work. During unbind, that work must be cancelled after interrupts are disabled; otherwise pending work can reference freed driver state. Linux stable commits are listed as the fix sources, but the bundle does not clearly map every affected version to each fixed release.

Likely exposure

Exposure appears limited to Linux systems that include and use the mpc52xx SPI driver, typically hardware needing MPC52xx SPI support. General Linux servers without this driver or hardware path are less likely to be affected.

Exploitation context

The source bundle marks KEV as false and provides no cited evidence of active exploitation, public exploit code, or remote attack path. Triggerability and impact beyond use-after-free are not documented in the provided sources.

Researcher notes

The record is sparse: no CVSS, CWE, exploitability analysis, or complete version-range explanation. Focus validation on driver reachability, unbind lifecycle behavior, and whether downstream kernels include the stable backport.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2026-46219.
  • Update to a kernel containing the referenced stable fix commits.
  • Prioritize systems using MPC52xx SPI hardware or the mpc52xx SPI driver.
  • If updates are unavailable, request vendor guidance for supported compensating controls.

Validation and detection

  • Inventory running kernel versions on potentially affected systems.
  • Check whether the mpc52xx SPI driver is built, loaded, or required.
  • Compare vendor kernel packages against the referenced upstream stable commits.
  • Confirm patch status through distribution CVE trackers or kernel changelogs.
Prepared
Confidence
medium
Sources
10

Public sources used

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-46219 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe0c6ce8424095c2da32a063d3fc027494c689817, cd5106c77d6d6828aa82449f01f4eb436d602a21, 373d55a47dc662e5e30d12ad5d334312f757c1f1, f65d85bc1ffd8a2c194bb2cd65e35ed3648ddd59, 90b72189de2cddacb26250579da0510b29a8b82b, 984836621aad98802d92c4a3047114cf518074c8, 984836621aad98802d92c4a3047114cf518074c8, 984836621aad98802d92c4a3047114cf518074c8, d0cde3911cf24e1bcdd4caa1d1b9ef57589db5a1, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5, 5.4.287unaffected
LinuxLinux6.13, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.90, 6.18.32, 7.0.9, 7.1affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.