CVE-2024-58054: staging: media: max96712: fix kernel oops when removing module
In the Linux kernel, the following vulnerability has been resolved:
staging: media: max96712: fix kernel oops when removing module
The following kernel oops is thrown when trying to remove the max96712 module:
Unable to handle kernel paging request at virtual address 00007375746174db Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=000000010af89000 [00007375746174db] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: crct10difce polyvalce mxcjpegencdec flexcan sndsocfslsai sndsocfslasoccard sndsocfslmicfil dwcmipicsi2 imxcsiformatter polyvalgeneric v4l2jpeg imxpcmdma candev sndsocimxaudmux sndsocwm8962 sndsocimxcard sndsocfslutils max96712(C-) rpmsgctrl rpmsgchar pwmfan fuse [last unloaded: imx8isi] CPU: 0 UID: 0 PID: 754 Comm: rmmod Tainted: G C 6.12.0-rc6-06364-g327fec852c31 #17 Tainted: [C]=CRAP Hardware name: NXP i.MX95 19X19 board (DT) pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : ledput+0x1c/0x40 lr : v4l2subdevputprivacyled+0x48/0x58 sp : ffff80008699bbb0 x29: ffff80008699bbb0 x28: ffff00008ac233c0 x27: 0000000000000000 x26: 0000000000000000 x25: 0000000000000000 x24: 0000000000000000 x23: ffff000080cf1170 x22: ffff00008b53bd00 x21: ffff8000822ad1c8 x20: ffff000080ff5c00 x19: ffff00008b53be40 x18: 0000000000000000 x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 x14: 0000000000000004 x13: ffff0000800f8010 x12: 0000000000000000 x11: ffff000082acf5c0 x10: ffff000082acf478 x9 : ffff0000800f8010 x8 : 0101010101010101 x7 : 7f7f7f7f7f7f7f7f x6 : fefefeff6364626d x5 : 8080808000000000 x4 : 0000000000000020 x3 : 00000000553a3dc1 x2 : ffff00008ac233c0 x1 : ffff00008ac233c0 x0 : ff00737574617473 Call trace: ledput+0x1c/0x40 v4l2subdevputprivacyled+0x48/0x58 v4l2asyncunregistersubdev+0x2c/0x1a4 max96712remove+0x1c/0x38 [max96712] i2cdeviceremove+0x2c/0x9c deviceremove+0x4c/0x80 devicereleasedriverinternal+0x1cc/0x228 driverdetach+0x4c/0x98 busremovedriver+0x6c/0xbc driverunregister+0x30/0x60 i2cdeldriver+0x54/0x64 max96712i2cdriverexit+0x18/0x1d0 [max96712] arm64sysdeletemodule+0x1a4/0x290 invokesyscall+0x48/0x10c el0svccommon.constprop.0+0xc0/0xe0 doel0svc+0x1c/0x28 el0svc+0x34/0xd8 el0t64synchandler+0x120/0x12c el0t64sync+0x190/0x194 Code: f9000bf3 aa0003f3 f9402800 f9402000 (f9403400) ---[ end trace 0000000000000000 ]---
This happens because in v4l2i2csubdevinit(), the i2csetcliendata() is called again and the data is overwritten to point to sd, instead of priv. So, in remove(), the wrong pointer is passed to v4l2asyncunregistersubdev(), leading to a crash.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-58054?
CVE-2024-58054 has been categorized as a moderate severity vulnerability due to its impact on kernel stability.
What are the potential impacts of CVE-2024-58054?
CVE-2024-58054 can cause kernel oops errors, leading to crashes or unexpected behavior when attempting to remove the max96712 module.
How do I fix CVE-2024-58054?
To fix CVE-2024-58054, update to the latest version of the Linux kernel where the issue has been resolved.
Which versions of the Linux kernel are affected by CVE-2024-58054?
CVE-2024-58054 affects specific versions of the Linux kernel that contain the vulnerable max96712 module.
When was CVE-2024-58054 disclosed?
CVE-2024-58054 was disclosed in a recent update to the Linux kernel addressing module removal issues.