LiveActive security incident?Get immediate response
CVE Record

CVE-2021-47456: can: peak_pci: peak_pci_remove(): fix UAF

In the Linux kernel, the following vulnerability has been resolved: can: peak_pci: peak_pci_remove(): fix UAF When remove the module peek_pci, referencing 'chan' again after releasing 'dev' will cause UAF. Fix this by releasing 'dev' later. The following log reveals it: [ 35.961814 ] BUG: KASAN: use-after-free in peak_pci_remove+0x16f/0x270 [peak_pci] [ 35.963414 ] Read of size 8 at addr ffff888136998ee8 by task modprobe/5537 [ 35.965513 ] Call Trace: [ 35.965718 ] dump_stack_lvl+0xa8/0xd1 [ 35.966028 ] print_address_description+0x87/0x3b0 [ 35.966420 ] kasan_report+0x172/0x1c0 [ 35.966725 ] ? peak_pci_remove+0x16f/0x270 [peak_pci] [ 35.967137 ] ? trace_irq_enable_rcuidle+0x10/0x170 [ 35.967529 ] ? peak_pci_remove+0x16f/0x270 [peak_pci] [ 35.967945 ] __asan_report_load8_noabort+0x14/0x20 [ 35.968346 ] peak_pci_remove+0x16f/0x270 [peak_pci] [ 35.968752 ] pci_device_remove+0xa9/0x250

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory safety flaw in the PEAK PCI CAN driver. When the driver is removed, it can use memory after it has already been freed. On systems using this driver, the impact could be serious, but the evidence provided points to local driver removal behavior, not internet-facing exploitation.

Executive priority

Treat this as a targeted high-priority kernel update for systems using PEAK PCI CAN functionality. It is less likely to be a broad enterprise emergency unless those drivers are deployed, but affected operational or embedded systems should be patched promptly through normal kernel maintenance channels.

Technical view

CVE-2021-47456 is a use-after-free in Linux kernel peak_pci_remove() for the CAN peak_pci driver. The provided KASAN trace shows peak_pci_remove() reading a freed chan-related object after dev was released. The fix changes cleanup ordering so dev is released later.

Likely exposure

Exposure is most likely on Linux systems with the PEAK PCI CAN driver present and reachable through device or module removal paths. This is especially relevant to industrial, automotive, embedded, or lab systems using PEAK-System CAN PCI hardware. Generic Linux servers without this driver or hardware are less likely exposed.

Exploitation context

The bundle reports CVSS 8.4 with local attack vector and no privileges required. It does not cite CISA KEV listing or other evidence of active exploitation. The available evidence supports a serious local kernel memory-corruption risk, not confirmed in-the-wild exploitation.

Researcher notes

Evidence is limited to the CVE record description, CVSS, affected Linux version data, and kernel stable references. The trigger is driver removal cleanup, with KASAN confirming a use-after-free. No exploit details, exploit maturity, or distribution-specific fixed package versions are provided in the source bundle.

Mitigation direction

  • Update affected Linux kernels to vendor-supported builds containing the referenced stable fixes.
  • Prioritize systems using PEAK PCI CAN hardware or loading the peak_pci driver.
  • If immediate patching is unavailable, check Linux distribution guidance for supported mitigations.
  • Limit local access to systems where the affected driver is present.
  • Avoid ad hoc kernel or module changes outside vendor-supported maintenance procedures.

Validation and detection

  • Inventory systems for Linux kernels in the affected version ranges from the CVE record.
  • Check whether the peak_pci driver is built, installed, or loaded.
  • Confirm installed kernel packages include the relevant stable fix commits or vendor backports.
  • Review distribution advisories for CVE-2021-47456 applicability to shipped kernels.
  • Validate remediation in staging before production rollout on CAN-connected systems.
Prepared
Confidence
medium
Sources
10

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.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-467: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-47456 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
High
CVSS
8.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2021-47456Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd, e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cdunaffected
LinuxLinux3.4, 0, 4.4.290, 4.9.288, 4.14.253, 4.19.214, 5.4.156, 5.10.76, 5.14.15, 5.15affected
Weakness

CWE details

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

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-467 · source CWE mapping

Use of sizeof() on a Pointer Type

Use of sizeof() on a Pointer Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.