CVE-2021-47456

can: peak_pci: peak_pci_remove(): fix UAF

HIGH

8.4

CVSS Score

Published: May 22, 2024 at 06:19 AM UTC

Updated: June 17, 2026 at 04:17 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.4

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.4 ≤ v < 4.14.2533.4 ≤ v < 4.19.2143.4 ≤ v < 4.4.2903.4 ≤ v < 4.9.2883.4 ≤ v < 5.10.763.4 ≤ v < 5.14.153.4 ≤ v < 5.153.4 ≤ v < 5.4.1564.10 ≤ v < 4.14.2534.15 ≤ v < 4.19.2144.20 ≤ v < 5.4.1564.5 ≤ v < 4.9.2885.11 ≤ v < 5.14.155.5 ≤ v < 5.10.765.15 rc1 5.15 rc2 5.15 rc3 5.15 rc4 5.15 rc5 5.15 rc6e6d9c80b7ca1e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd

Vendor states this is fixed in 0e5afdc2315b0737edcf55bede4ee1640d2d464d (fixed)

Vendor states this is fixed in 1248582e47a9f7ce0ecd156c39fc61f8b6aa3699 (fixed)

Vendor states this is fixed in 1c616528ba4aeb1125a06b407572ab7b56acae38 (fixed)

Vendor states this is fixed in 28f28e4bc3a5e0051faa963f10b778ab38c1db69 (fixed)

Vendor states this is fixed in 34914971bb3244db4ce2be44e9438a9b30c56250 (fixed)

Vendor states this is fixed in 447d44cd2f67a20b596ede3ca3cd67086dfd9ca9 (fixed)

Vendor states this is fixed in 949fe9b35570361bc6ee2652f89a0561b26eec98 (fixed)

Vendor states this is fixed in adbda14730aacce41c0d3596415aa39ad63eafd9 (fixed)

Vendor states this is fixed in 3.4 (unaffected)

Vendor states this is fixed in 4.14.253 (unaffected)

Vendor states this is fixed in 4.19.214 (unaffected)

Vendor states this is fixed in 4.4.290 (unaffected)

Vendor states this is fixed in 4.9.288 (unaffected)

Vendor states this is fixed in 5.10.76 (unaffected)

Vendor states this is fixed in 5.14.15 (unaffected)

Vendor states this is fixed in 5.15 (unaffected)

Vendor states this is fixed in 5.4.156 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references