Can an android device infect a USB C PD (PPS) Charger with a malware which then will compromise other device and spread it?
retained text
I was on an airport previously using my laptop plugged in a wall with its USB C fast charger (PD PPS), then asked if they can plug in their Chinese-brand smartphone for a short while (which I agreed to not to be rude). Now, knowing that some chargers, especially those Apple ones, have an updatable firmware; and hearing of BadUSB years ago, is it possible for an Android (potentially with malware) to infect the firmware of my charger, which in turn infect my laptop? I've read other forums saying no, but I think they are referring to normal copper-only charger without the new "smart" thingy nowadays. I have some confidential stuff in my laptop, not something like state level, just university research and for publication, so very unlikely that I am targeted, but still I am wary that this may compromise my system (I am using Linux). ChatGPT and Claude suggested watching journalctl -kf when I plugged in the charger, as well as to inspect lsusb -t and lspci -nn. The fwupdmgr get-devices does not gave firmware for the charger too, so I suppose it is nonprogrammable thus cannot be a vector without being physically compromised? Nov 10 21:07:51 sysmain kernel: usb 3-3.1: reset full-speed USB device number 4 using xhci\_hcd Nov 10 21:08:19 sysmain kernel: asus\_wmi: Unknown key code 0x77 Nov 10 21:08:20 sysmain kernel: asus\_wmi: Unknown key code 0x77 Nov 10 21:08:20 sysmain kernel: asus\_wmi: Unknown key code 0x77 Nov 10 21:08:20 sysmain kernel: asus\_wmi: Unknown key code 0x97 Nov 10 21:08:30 sysmain kernel: ucsi\_acpi USBC000:00: GET\_CURRENT\_CAM command failed Nov 10 21:08:51 sysmain kernel: usb 3-3.1: reset full-speed USB device number 4 using xhci\_hcd 00:00.0 Host bridge \[0600\]: Intel Corporation Core Ultra 200V Series Processors with 4 P-Cores 4 E-Cores Host Bridge \[8086:6400\] (rev 04) 00:02.0 VGA compatible controller \[0300\]: Intel Corporation Core Ultra 200V Series Processors Arc Graphics 130V/140V GPU \[8086:64a0\] (rev 04) 00:04.0 Signal processing controller \[1180\]: Intel Corporation Core Ultra 200V Series Processors Dynamic Tuning Technology (DTT) \[8086:641d\] (rev 04) 00:07.0 PCI bridge \[0604\]: Intel Corporation Core Ultra 200V Series Processors USB Type-C Subsystem PCIe Root Port #21 \[8086:a84e\] (rev 10) 00:07.1 PCI bridge \[0604\]: Intel Corporation Core Ultra 200V Series Processors USB Type-C Subsystem PCIe Root Port #22 \[8086:a84f\] (rev 10) 00:0a.0 Signal processing controller \[1180\]: Intel Corporation Core Ultra 200V Series Processors Crash Log and Telemetry \[8086:647d\] (rev 04) 00:0b.0 Processing accelerators \[1200\]: Intel Corporation Core Ultra 200V Series Processors NPU \[8086:643e\] (rev 04) 00:0d.0 USB controller \[0c03\]: Intel Corporation Core Ultra 200V Series Processors Type-C Subsystem xHCI \[8086:a831\] (rev 10) 00:0d.2 USB controller \[0c03\]: Intel Corporation Core Ultra 200V Series Processors Thunderbolt DMA0 \[8086:a833\] (rev 10) 00:12.0 Serial controller \[0700\]: Intel Corporation Core Ultra 200V Series Processors Integrated Sensor Hub (ISH) \[8086:a845\] (rev 10) 00:13.0 Communication controller \[0780\]: Intel Corporation Core Ultra 200V Series Processors CSME HECI #1 \[8086:a862\] (rev 10) 00:14.0 USB controller \[0c03\]: Intel Corporation Core Ultra 200V Series Processors Standalone xHCI Controller \[8086:a87d\] (rev 10) 00:14.2 RAM memory \[0500\]: Intel Corporation Core Ultra 200V Series Processors Shared SRAM \[8086:a87f\] (rev 10) 00:14.3 Network controller \[0280\]: Intel Corporation BE200 Series Wi-Fi 7 \[8086:a840\] (rev 10) 00:16.0 Communication controller \[0780\]: Intel Corporation Core Ultra 200V Series Processors CSME HECI #1 (CSE) \[8086:a870\] (rev 10) 00:19.0 Serial bus controller \[0c80\]: Intel Corporation Core Ultra 200V Series Processors I2C #4 \[8086:a850\] (rev 10) 00:1c.0 PCI bridge \[0604\]: Intel Corporation Core Ultra 200V Series Processors PCIe Root Port #1 \[8086:a838\] (rev 10) 00:1e.0 Communication controller \[0780\]: Intel Corporation Core Ultra 200V Series Processors UART #0 \[8086:a825\] (rev 10) 00:1e.3 Serial bus controller \[0c80\]: Intel Corporation Core Ultra 200V Series Processors GSPI #1 \[8086:a830\] (rev 10) 00:1f.0 ISA bridge \[0601\]: Intel Corporation Core Ultra 200V Series Processors eSPI Controller \[8086:a807\] (rev 10) 00:1f.3 Multimedia audio controller \[0401\]: Intel Corporation Core Ultra 200V Series Processors HD Audio \[8086:a828\] (rev 10) 00:1f.4 SMBus \[0c05\]: Intel Corporation Lunar Lake-M SMbus Controller \[8086:a822\] (rev 10) 00:1f.5 Serial bus controller \[0c80\]: Intel Corporation Core Ultra 200V Series Processors SPI (flash) Controller \[8086:a823\] (rev 10) 55:00.0 Non-Volatile memory controller \[0108\]: Sandisk Corp WD PC SN5000S M.2 2280 NVMe SSD (DRAM-less) \[15b7:5036\] /: Bus 001.Port 001: Dev 001, Class=root\_hub, Driver=xhci\_hcd/1p, 480M /: Bus 002.Port 001: Dev 001, Class=root\_hub, Driver=xhci\_hcd/2p, 20000M/x2 /: Bus 003.Port 001: Dev 001, Class=root\_hub, Driver=xhci\_hcd/8p, 480M |\_\_ Port 003: Dev 002, If 0, Class=Hub, Driver=hub/2p, 480M |\_\_ Port 001: Dev 004, If 0, Class=Diagnostic, Driver=\[none\], 12M |\_\_ Port 002: Dev 006, If 0, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 002: Dev 006, If 1, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 002: Dev 006, If 2, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 005: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M |\_\_ Port 005: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M |\_\_ Port 005: Dev 003, If 2, Class=Video, Driver=uvcvideo, 480M |\_\_ Port 005: Dev 003, If 3, Class=Video, Driver=uvcvideo, 480M |\_\_ Port 005: Dev 003, If 4, Class=Application Specific Interface, Driver=\[none\], 480M |\_\_ Port 006: Dev 005, If 0, Class=Wireless, Driver=btusb, 12M |\_\_ Port 006: Dev 005, If 1, Class=Wireless, Driver=btusb, 12M /: Bus 004.Port 001: Dev 001, Class=root\_hub, Driver=xhci\_hcd/2p, 20000M/x2
document fetched 2026-11-11 00:23 · canonical https://reddit.com/r/cybersecurity/comments/1xste1f/can_an_android_device_infect_a_usb_c_pd_pps