CVE-2021-47520: can: pch_can: pch_can_rx_normal: fix use after free
In the Linux kernel, the following vulnerability has been resolved:
can: pch_can: pch_can_rx_normal: fix use after free
After calling netif_receive_skb(skb), dereferencing skb is unsafe.
Especially, the can_frame cf which aliases skb memory is dereferenced
just after the call netif_receive_skb(skb).
Reordering the lines solves the issue.
Security readout for executives and security teams
Plain-English summary
CVE-2021-47520 is a Linux kernel bug in the pch_can CAN driver. The driver could use packet memory after handing it to the network stack, creating a use-after-free condition. The public record does not provide CVSS, impact details, or active exploitation evidence.
Executive priority
Handle through normal kernel patch management, with higher priority for operational technology, embedded, or vehicle-adjacent systems using CAN interfaces. There is not enough public evidence to justify emergency response solely from this CVE record.
Technical view
In pch_can_rx_normal, code dereferenced skb-backed can_frame data after netif_receive_skb(skb). The CVE states that dereferencing skb after that call is unsafe and that reordering the operations resolves the issue. Upstream stable kernel commits are referenced as fixes.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions with the pch_can CAN driver present and used. The CVE data has no CPEs and only lists Linux kernel versions and commits, so environment-specific validation is required.
Exploitation context
The source bundle does not report public exploitation, KEV listing, exploitability conditions, privilege requirements, or attacker position. Treat this as a kernel memory-safety issue until vendor advisories or distribution notices clarify impact.
Researcher notes
The key issue is lifetime ordering around skb ownership transfer to netif_receive_skb. The record says reordering fixes the unsafe dereference, but does not document practical impact, reachability, crashability, or privilege boundaries.
Mitigation direction
Update to a kernel containing the referenced upstream stable pch_can fix.
Check Linux distribution advisories for backported fixes and package names.
Prioritize systems that use CAN interfaces or load the pch_can driver.
If immediate patching is not possible, review vendor guidance for safe temporary mitigations.
Validation and detection
Inventory Linux kernel versions against the CVE affected-version data.
Check whether the pch_can driver is built, installed, or loaded.
Confirm updated kernels include one of the referenced stable commits or a vendor backport.
Review vendor security advisories for corrected package versions.
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-2021-47520 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.