In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 8at 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 size8 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 8at 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 size8 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 8at 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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 size8 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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
| linux | | https://git.kernel.org/linus/949fe9b35570361bc6ee2652f89a0561b26eec98 | https://git.kernel.org/linus/e6d9c80b7ca1504411ad6d7acdb8683e4ae1c9cd | ubuntu |
</details>
二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:can: peak_pci: peak_pci_remove(): fix UAFWhen remove the module peek_pci, referencing chan again afterreleasing 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