Kernel memory corruption via freed device access
Published May 24, 2024 · Updated May 11, 2026
Use-after-free in the Linux SJA1000 EMS PCMCIA CAN driver allows local users to corrupt kernel memory during card setup. The ems_pcmcia_add_card function frees dev when the final channel is unavailable, then reads dev->irq while registering the shared interrupt. The faulty path occurs only while a supported PCMCIA CAN card is being added and its last channel cannot be initialized; resulting corruption can crash the kernel or alter protected state.
Summary
What happened
Use-after-free in the Linux SJA1000 EMS PCMCIA CAN driver allows local users to corrupt kernel memory during card setup. The ems_pcmcia_add_card function frees dev when the final channel is unavailable, then reads dev->irq while registering the shared interrupt. The faulty path occurs only while a supported PCMCIA CAN card is being added and its last channel cannot be initialized; resulting corruption can crash the kernel or alter protected state.
The record
- CVE
- CVE-2021-47521
- Published
- May 24, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 24, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.2
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <1a295fea90e1acbe80c6d4940f5ff856edcd6bec
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <1dd5b819f7e406dc15bbc7670596ff25261aaa2a
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <474f9a8534f5f89841240a7e978bafd6e1e039ce
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <923f4dc5df679f678e121c20bf2fd70f7bf3e288
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <c8718026ba287168ff9ad0ccc4f9a413062cba36
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <cbd86110546f7f730a1f5d7de56c944a336c15c4
- Affected versionversion=fd734c6f25aea4b2b44b045e489aec67b388577e <ccf070183e4655824936c0f96c4a2bcca93419aa
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo