CVE-2021-47521: can: sja1000: fix use after free in ems_pcmcia_add_card()
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1a295fea90e1acbe80c6d4940f5ff856edcd6bec, 1dd5b819f7e406dc15bbc7670596ff25261aaa2a, 3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1a295fea90e1acbe80c6d4940f5ff856edcd6bec, 1dd5b819f7e406dc15bbc7670596ff25261aaa2a, 3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: can: sja1000: fix use after free in ems_pcmcia_add_card() If the last channel is not available then "dev" is freed. Fortunately, we can just use "pdev->irq" instead. Also we should check if at least one channel was set up.
- Published
- May 24, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-416
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.2affected
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before cbd86110546f7f730a1f5d7de56c944a336c15c4affected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before 1dd5b819f7e406dc15bbc7670596ff25261aaa2aaffected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before c8718026ba287168ff9ad0ccc4f9a413062cba36affected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before ccf070183e4655824936c0f96c4a2bcca93419aaaffected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before 1a295fea90e1acbe80c6d4940f5ff856edcd6becaffected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before 923f4dc5df679f678e121c20bf2fd70f7bf3e288affected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before 474f9a8534f5f89841240a7e978bafd6e1e039ceaffected · git
- fd734c6f25aea4b2b44b045e489aec67b388577e and later · before 3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45affected · git
- before 3.2not affected · semver
Affected versions · NVD (7)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.2 and later · before 4.4.295
- linux linux kernel4.5 and later · before 4.9.293
- linux linux kernel4.10 and later · before 4.14.258
- linux linux kernel4.15 and later · before 4.19.221
- linux linux kernel4.20 and later · before 5.4.165
- linux linux kernel5.5 and later · before 5.10.85
- linux linux kernel5.11 and later · before 5.15.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.15.15-1 | 5.15.15-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2021-47519May 24, 2024 · can: m_can: m_can_read_fifo: fix memory leak in error branch22Monitor
- ← EarlierCVE-2021-47520May 24, 2024 · can: pch_can: pch_can_rx_normal: fix use after free31Monitor
- Later →CVE-2021-47522May 24, 2024 · HID: bigbenff: prevent null pointer dereference22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1a295fea90e1acbe80c6d4940f5ff856edcd6bec | Vendor (CNA) |
| Linux Linux | 1dd5b819f7e406dc15bbc7670596ff25261aaa2a | Vendor (CNA) |
| Linux Linux | 3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45 | Vendor (CNA) |
| Linux Linux | 474f9a8534f5f89841240a7e978bafd6e1e039ce | Vendor (CNA) |
| Linux Linux | 923f4dc5df679f678e121c20bf2fd70f7bf3e288 | Vendor (CNA) |
| Linux Linux | c8718026ba287168ff9ad0ccc4f9a413062cba36 | Vendor (CNA) |
| Linux Linux | cbd86110546f7f730a1f5d7de56c944a336c15c4 | Vendor (CNA) |
| Linux Linux | ccf070183e4655824936c0f96c4a2bcca93419aa | Vendor (CNA) |
| debian:linux | 5.15.15-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-0551 · May 27, 2024(Linux Kernel Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1dd5b819f7e406dc15bbc7670596ff25261aaa2a
- git.kernel.org/stable/c/3ec6ca6b1a8e64389f0212b5a1b0f6fed1909e45
- git.kernel.org/stable/c/474f9a8534f5f89841240a7e978bafd6e1e039ce
- git.kernel.org/stable/c/923f4dc5df679f678e121c20bf2fd70f7bf3e288
- git.kernel.org/stable/c/c8718026ba287168ff9ad0ccc4f9a413062cba36
- git.kernel.org/stable/c/cbd86110546f7f730a1f5d7de56c944a336c15c4
- git.kernel.org/stable/c/ccf070183e4655824936c0f96c4a2bcca93419aa
Vendor advisories and official records. Exploit/PoC links are deliberately left out.