CVE-2024-53181

um: vector: Do not use drvdata in release

MEDIUM

5.5

CVSS Score

Published: December 27, 2024 at 01:49 PM UTC

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

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

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

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: um: vector: Do not use drvdata in release The drvdata is not available in release. Let's just use container_of() to get the vector_device instance. Otherwise, removing a vector device will result in a crash: RIP: 0033:vector_device_release+0xf/0x50 RSP: 00000000e187bc40 EFLAGS: 00010202 RAX: 0000000060028f61 RBX: 00000000600f1baf RCX: 00000000620074e0 RDX: 000000006220b9c0 RSI: 0000000060551c80 RDI: 0000000000000000 RBP: 00000000e187bc50 R08: 00000000603ad594 R09: 00000000e187bb70 R10: 000000000000135a R11: 00000000603ad422 R12: 00000000623ae028 R13: 000000006287a200 R14: 0000000062006d30 R15: 00000000623700b6 Kernel panic - not syncing: Segfault with no mm CPU: 0 UID: 0 PID: 16 Comm: kworker/0:1 Not tainted 6.12.0-rc6-g59b723cd2adb #1 Workqueue: events mc_work_proc Stack: 60028f61 623ae028 e187bc80 60276fcd 6220b9c0 603f5820 623ae028 00000000 e187bcb0 603a2bcd 623ae000 62370010 Call Trace: [<60028f61>] ? vector_device_release+0x0/0x50 [<60276fcd>] device_release+0x70/0xba [<603a2bcd>] kobject_put+0xba/0xe7 [<60277265>] put_device+0x19/0x1c [<60281266>] platform_device_put+0x26/0x29 [<60281e5f>] platform_device_unregister+0x2c/0x2e [<60029422>] vector_remove+0x52/0x58 [<60031316>] ? mconsole_reply+0x0/0x50 [<600310c8>] mconsole_remove+0x160/0x1cc [<603b19f4>] ? strlen+0x0/0x15 [<60066611>] ? __dequeue_entity+0x1a9/0x206 [<600666a7>] ? set_next_entity+0x39/0x63 [<6006666e>] ? set_next_entity+0x0/0x63 [<60038fa6>] ? um_set_signals+0x0/0x43 [<6003070c>] mc_work_proc+0x77/0x91 [<60057664>] process_scheduled_works+0x1b3/0x2dd [<60055f32>] ? assign_work+0x0/0x58 [<60057f0a>] worker_thread+0x1e9/0x293 [<6005406f>] ? set_pf_worker+0x0/0x64 [<6005d65d>] ? arch_local_irq_save+0x0/0x2d [<6005d748>] ? kthread_exit+0x0/0x3a [<60057d21>] ? worker_thread+0x0/0x293 [<6005dbf1>] kthread+0x126/0x12b [<600219c5>] new_thread_handler+0x85/0xb6

Affected

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

Linux Kernel · Linux

95%

v < 4.19.3254.17 ≤ v < 4.19.3254.17 ≤ v < 5.10.2314.17 ≤ v < 5.15.1744.17 ≤ v < 5.4.2874.17 ≤ v < 6.1.1204.17 ≤ v < 6.11.114.17 ≤ v < 6.12.24.17 ≤ v < 6.134.17 ≤ v < 6.6.644.20 ≤ v < 5.4.2875.11 ≤ v < 5.15.1745.16 ≤ v < 6.1.1205.5 ≤ v < 5.10.2316.12 ≤ v < 6.12.26.2 ≤ v < 6.6.646.7 ≤ v < 6.11.114.1749da7e64f33e80edffb1a9eeb230fa4c3f42dffb

Vendor states this is fixed in 12f52e373d63f008ee386f371bdd82a3a3779199 (fixed)

Vendor states this is fixed in 35f8f72b45791a6a71b81140c59d02a6183b6f3b (fixed)

Vendor states this is fixed in 376c7f0beb8f6f3800fc3013ef2f422d0cbfbf92 (fixed)

Vendor states this is fixed in 51b39d741970742a5c41136241a9c48ac607cf82 (fixed)

Vendor states this is fixed in 8204dd589c4f25a7618eece5da3f0871e02af8ae (fixed)

Vendor states this is fixed in 8ed7793f6f589b4e1f0b38f8448578d2a48f9c82 (fixed)

Vendor states this is fixed in bef9a2835011668c221851a7572b6c8433087f85 (fixed)

Vendor states this is fixed in dc5251b1af5c9a0749322bf58bd5aa673f545fe2 (fixed)

Vendor states this is fixed in e9d36f7e71a907ec507f84ee5d60a622c345cac4 (fixed)

Vendor states this is fixed in 4.17 (unaffected)

Vendor states this is fixed in 4.19.325 (unaffected)

Vendor states this is fixed in 5.10.231 (unaffected)