{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-53046 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-53046 is a medium-severity vulnerability in Linux kernel, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53046 and fix it if it is affected.\n\nWhat it is: CVE-2024-53046 is a medium-severity vulnerability in Linux kernel, published on 19 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-53046 in the wild and no public exploit code.\n\nAffected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-53046/ (Markdown: https://insights.sbomify.com/CVE-2024-53046/index.md)","id":"CVE-2024-53046","markdown":"https://insights.sbomify.com/CVE-2024-53046/index.md","name":"CVE-2024-53046","record":{"aliases":["AZL-53858","BELL-CVE-2024-53046","DEBIAN-CVE-2024-53046","GHSA-8hgx-89h7-3vhm","UBUNTU-CVE-2024-53046"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Incorrect device tree configuration causes a kernel warning and potential instability during SPI flash initialization on i.MX8ULP devices.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\narm64: dts: imx8ulp: correct the flexspi compatible string\n\nThe flexspi on imx8ulp only has 16 LUTs, and imx8mm flexspi has\n32 LUTs, so correct the compatible string here, otherwise will\nmeet below error:\n\n[    1.119072] ------------[ cut here ]------------\n[    1.123926] WARNING: CPU: 0 PID: 1 at drivers/spi/spi-nxp-fspi.c:855 nxp_fspi_exec_op+0xb04/0xb64\n[    1.133239] Modules linked in:\n[    1.136448] CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-rc6-next-20240902-00001-g131bf9439dd9 #69\n[    1.146821] Hardware name: NXP i.MX8ULP EVK (DT)\n[    1.151647] pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[    1.158931] pc : nxp_fspi_exec_op+0xb04/0xb64\n[    1.163496] lr : nxp_fspi_exec_op+0xa34/0xb64\n[    1.168060] sp : ffff80008002b2a0\n[    1.171526] x29: ffff80008002b2d0 x28: 0000000000000000 x27: 0000000000000000\n[    1.179002] x26: ffff2eb645542580 x25: ffff800080610014 x24: ffff800080610000\n[    1.186480] x23: ffff2eb645548080 x22: 0000000000000006 x21: ffff2eb6455425e0\n[    1.193956] x20: 0000000000000000 x19: ffff80008002b5e0 x18: ffffffffffffffff\n[    1.201432] x17: ffff2eb644467508 x16: 0000000000000138 x15: 0000000000000002\n[    1.208907] x14: 0000000000000000 x13: ffff2eb6400d8080 x12: 00000000ffffff00\n[    1.216378] x11: 0000000000000000 x10: ffff2eb6400d8080 x9 : ffff2eb697adca80\n[    1.223850] x8 : ffff2eb697ad3cc0 x7 : 0000000100000000 x6 : 0000000000000001\n[    1.231324] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 00000000000007a6\n[    1.238795] x2 : 0000000000000000 x1 : 00000000000001ce x0 : 00000000ffffff92\n[    1.246267] Call trace:\n[    1.248824]  nxp_fspi_exec_op+0xb04/0xb64\n[    1.253031]  spi_mem_exec_op+0x3a0/0x430\n[    1.257139]  spi_nor_read_id+0x80/0xcc\n[    1.261065]  spi_nor_scan+0x1ec/0xf10\n[    1.264901]  spi_nor_probe+0x108/0x2fc\n[    1.268828]  spi_mem_probe+0x6c/0xbc\n[    1.272574]  spi_probe+0x84/0xe4\n[    1.275958]  really_probe+0xbc/0x29c\n[    1.279713]  __driver_probe_device+0x78/0x12c\n[    1.284277]  driver_probe_device+0xd8/0x15c\n[    1.288660]  __device_attach_driver+0xb8/0x134\n[    1.293316]  bus_for_each_drv+0x88/0xe8\n[    1.297337]  __device_attach+0xa0/0x190\n[    1.301353]  device_initial_probe+0x14/0x20\n[    1.305734]  bus_probe_device+0xac/0xb0\n[    1.309752]  device_add+0x5d0/0x790\n[    1.313408]  __spi_add_device+0x134/0x204\n[    1.317606]  of_register_spi_device+0x3b4/0x590\n[    1.322348]  spi_register_controller+0x47c/0x754\n[    1.327181]  devm_spi_register_controller+0x4c/0xa4\n[    1.332289]  nxp_fspi_probe+0x1cc/0x2b0\n[    1.336307]  platform_probe+0x68/0xc4\n[    1.340145]  really_probe+0xbc/0x29c\n[    1.343893]  __driver_probe_device+0x78/0x12c\n[    1.348457]  driver_probe_device+0xd8/0x15c\n[    1.352838]  __driver_attach+0x90/0x19c\n[    1.356857]  bus_for_each_dev+0x7c/0xdc\n[    1.360877]  driver_attach+0x24/0x30\n[    1.364624]  bus_add_driver+0xe4/0x208\n[    1.368552]  driver_register+0x5c/0x124\n[    1.372573]  __platform_driver_register+0x28/0x34\n[    1.377497]  nxp_fspi_driver_init+0x1c/0x28\n[    1.381888]  do_one_initcall+0x80/0x1c8\n[    1.385908]  kernel_init_freeable+0x1c4/0x28c\n[    1.390472]  kernel_init+0x20/0x1d8\n[    1.394138]  ret_from_fork+0x10/0x20\n[    1.397885] ---[ end trace 0000000000000000 ]---\n[    1.407908] ------------[ cut here ]------------","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"arm64: dts: imx8ulp: correct the flexspi compatible string","id":"CVE-2024-53046","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"other","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"mptcp: init: protect sched with rcu_read_lock","id":"CVE-2024-53047"},"packages":[],"prev":{"headline":"ASoC: dapm: fix bounds checker error in dapm_widget_list_create","id":"CVE-2024-53045"},"products":["Linux"],"published":"2024-11-19","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"Incorrect device tree configuration causes a kernel warning and potential instability during SPI flash initialization on i.MX8ULP devices.","url":"https://insights.sbomify.com/CVE-2024-53046/"}