CVE-2024-53046: arm64: dts: imx8ulp: correct the flexspi compatible string
In the Linux kernel, the following vulnerability has been resolved:
arm64: dts: imx8ulp: correct the flexspi compatible string
The flexspi on imx8ulp only has 16 LUTs, and imx8mm flexspi has 32 LUTs, so correct the compatible string here, otherwise will meet below error:
[ 1.119072] ------------[ cut here ]------------ [ 1.123926] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-nxp-fspi.c:855 nxpfspiexecop+0xb04/0xb64 [ 1.133239] Modules linked in: [ 1.136448] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc6-next-20240902-00001-g131bf9439dd9 #69 [ 1.146821] Hardware name: NXP i.MX8ULP EVK (DT) [ 1.151647] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 1.158931] pc : nxpfspiexecop+0xb04/0xb64 [ 1.163496] lr : nxpfspiexecop+0xa34/0xb64 [ 1.168060] sp : ffff80008002b2a0 [ 1.171526] x29: ffff80008002b2d0 x28: 0000000000000000 x27: 0000000000000000 [ 1.179002] x26: ffff2eb645542580 x25: ffff800080610014 x24: ffff800080610000 [ 1.186480] x23: ffff2eb645548080 x22: 0000000000000006 x21: ffff2eb6455425e0 [ 1.193956] x20: 0000000000000000 x19: ffff80008002b5e0 x18: ffffffffffffffff [ 1.201432] x17: ffff2eb644467508 x16: 0000000000000138 x15: 0000000000000002 [ 1.208907] x14: 0000000000000000 x13: ffff2eb6400d8080 x12: 00000000ffffff00 [ 1.216378] x11: 0000000000000000 x10: ffff2eb6400d8080 x9 : ffff2eb697adca80 [ 1.223850] x8 : ffff2eb697ad3cc0 x7 : 0000000100000000 x6 : 0000000000000001 [ 1.231324] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000000007a6 [ 1.238795] x2 : 0000000000000000 x1 : 00000000000001ce x0 : 00000000ffffff92 [ 1.246267] Call trace: [ 1.248824] nxpfspiexecop+0xb04/0xb64 [ 1.253031] spimemexecop+0x3a0/0x430 [ 1.257139] spinorreadid+0x80/0xcc [ 1.261065] spinorscan+0x1ec/0xf10 [ 1.264901] spinorprobe+0x108/0x2fc [ 1.268828] spimemprobe+0x6c/0xbc [ 1.272574] spiprobe+0x84/0xe4 [ 1.275958] reallyprobe+0xbc/0x29c [ 1.279713] driverprobedevice+0x78/0x12c [ 1.284277] driverprobedevice+0xd8/0x15c [ 1.288660] deviceattachdriver+0xb8/0x134 [ 1.293316] busforeachdrv+0x88/0xe8 [ 1.297337] deviceattach+0xa0/0x190 [ 1.301353] deviceinitialprobe+0x14/0x20 [ 1.305734] busprobedevice+0xac/0xb0 [ 1.309752] deviceadd+0x5d0/0x790 [ 1.313408] spiadddevice+0x134/0x204 [ 1.317606] ofregisterspidevice+0x3b4/0x590 [ 1.322348] spiregistercontroller+0x47c/0x754 [ 1.327181] devmspiregistercontroller+0x4c/0xa4 [ 1.332289] nxpfspiprobe+0x1cc/0x2b0 [ 1.336307] platformprobe+0x68/0xc4 [ 1.340145] reallyprobe+0xbc/0x29c [ 1.343893] driverprobedevice+0x78/0x12c [ 1.348457] driverprobedevice+0xd8/0x15c [ 1.352838] driverattach+0x90/0x19c [ 1.356857] busforeachdev+0x7c/0xdc [ 1.360877] driverattach+0x24/0x30 [ 1.364624] busadddriver+0xe4/0x208 [ 1.368552] driverregister+0x5c/0x124 [ 1.372573] platformdriverregister+0x28/0x34 [ 1.377497] nxpfspidriverinit+0x1c/0x28 [ 1.381888] dooneinitcall+0x80/0x1c8 [ 1.385908] kernelinitfreeable+0x1c4/0x28c [ 1.390472] kernelinit+0x20/0x1d8 [ 1.394138] retfromfork+0x10/0x20 [ 1.397885] ---[ end trace 0000000000000000 ]--- [ 1.407908] ------------[ cut here ]------------
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53046?
The severity of CVE-2024-53046 is moderate, as it involves a compatibility issue in the Linux kernel.
How do I fix CVE-2024-53046?
To fix CVE-2024-53046, update your Linux kernel to a version that includes the patch addressing the compatible string for the flexspi on imx8ulp.
Which Linux kernel versions are affected by CVE-2024-53046?
CVE-2024-53046 affects Linux kernel versions between 6.6 and 6.11.7, including 6.12 release candidates.
What issue does CVE-2024-53046 address?
CVE-2024-53046 addresses an incorrect compatible string for the flexspi in the imx8ulp, which could lead to errors due to an incorrect number of logical unit textures (LUTs).
Is there a workaround for CVE-2024-53046?
There is no known workaround for CVE-2024-53046 other than applying the recommended kernel update.