Bug 216422 - BUG: kernel NULL pointer dereference, address: 0000000000000000
Summary: BUG: kernel NULL pointer dereference, address: 0000000000000000
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: USB (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Default virtual assignee for Drivers/USB
Depends on:
Reported: 2022-08-27 20:48 UTC by Jan
Modified: 2024-03-15 10:07 UTC (History)
4 users (show)

See Also:
Kernel Version: 5.18.0-rc1-1-00059-g87d0e2f41b8c
Regression: Yes
Bisected commit-id:

dmesg with NULL pointer dereferences. (129.82 KB, text/plain)
2022-08-27 20:48 UTC, Jan
bisect log (2.99 KB, text/plain)
2022-08-27 20:49 UTC, Jan

Description Jan 2022-08-27 20:48:06 UTC
Created attachment 301686 [details]
dmesg with NULL pointer dereferences.


Several users including me are experiencing an issue with Thinkpads becoming completely unresponsive after several hours. This seems to happen more often shortly after the system has been idle for some time.
The issue only occurs when the Thinkpad is already connected to a USB C docking station before booting.

dmesg shows regular
"BUG: kernel NULL pointer dereference, address: 0000000000000000"
that do not cause a crash however.
These only show up, when the systemd upower.service is running.

In the attached dmesg.txt, I booted with upower.service disabled and started it manually which immediately lead to the NULL pointer dereference (but no crash).

We bisected and found the offending commit in https://bbs.archlinux.org/viewtopic.php?id=279027

Please see the attached bisect-log.txt .
Comment 1 Jan 2022-08-27 20:49:15 UTC
Created attachment 301687 [details]
bisect log
Comment 2 Eric Haynes 2022-08-28 00:21:18 UTC
I am also experiencing this. I'm not sure if modern docking stations are more than just a USB C hub, but in case it matters, I have an external monitor and a keyboard connected via USB C but do not own a docking station.
Comment 3 The Linux kernel's regression tracker (Thorsten Leemhuis) 2022-08-28 11:28:42 UTC
Thx for the bisect. That commits is known to cause some trouble. See this thread:

A fix for that problem is heading towards mainline currently:

Might be worth giving it a shot.
Comment 4 Artem S. Tashkinov 2024-03-15 10:07:58 UTC
Is this still an issue in 6.7.9 or 6.8?

Note You need to log in before you can comment on or make changes to this bug.