{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-21824 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-21824 is a medium-severity vulnerability in Linux kernel, published on 27 Feb 2025. 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-2025-21824 and fix it if it is affected.\n\nWhat it is: CVE-2025-21824 is a medium-severity vulnerability in Linux kernel, published on 27 Feb 2025. 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-2025-21824 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-2025-21824/ (Markdown: https://insights.sbomify.com/CVE-2025-21824/index.md)","id":"CVE-2025-21824","markdown":"https://insights.sbomify.com/CVE-2025-21824/index.md","name":"CVE-2025-21824","record":{"aliases":["BELL-CVE-2025-21824","DEBIAN-CVE-2025-21824","GHSA-x45r-q45r-hq9w","UBUNTU-CVE-2025-21824"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel GPU driver","requires_auth":"low_privilege","summary":"A use of an uninitialized mutex in the Linux kernel host1x driver can cause a system warning and potential crash when debug options are enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"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":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpu: host1x: Fix a use of uninitialized mutex\n\ncommit c8347f915e67 (\"gpu: host1x: Fix boot regression for Tegra\")\ncaused a use of uninitialized mutex leading to below warning when\nCONFIG_DEBUG_MUTEXES and CONFIG_DEBUG_LOCK_ALLOC are enabled.\n\n[   41.662843] ------------[ cut here ]------------\n[   41.663012] DEBUG_LOCKS_WARN_ON(lock-\u003emagic != lock)\n[   41.663035] WARNING: CPU: 4 PID: 794 at kernel/locking/mutex.c:587 __mutex_lock+0x670/0x878\n[   41.663458] Modules linked in: rtw88_8822c(+) bluetooth(+) rtw88_pci rtw88_core mac80211 aquantia libarc4 crc_itu_t cfg80211 tegra194_cpufreq dwmac_tegra(+) arm_dsu_pmu stmmac_platform stmmac pcs_xpcs rfkill at24 host1x(+) tegra_bpmp_thermal ramoops reed_solomon fuse loop nfnetlink xfs mmc_block rpmb_core ucsi_ccg ina3221 crct10dif_ce xhci_tegra ghash_ce lm90 sha2_ce sha256_arm64 sha1_ce sdhci_tegra pwm_fan sdhci_pltfm sdhci gpio_keys rtc_tegra cqhci mmc_core phy_tegra_xusb i2c_tegra tegra186_gpc_dma i2c_tegra_bpmp spi_tegra114 dm_mirror dm_region_hash dm_log dm_mod\n[   41.665078] CPU: 4 UID: 0 PID: 794 Comm: (udev-worker) Not tainted 6.11.0-29.31_1538613708.el10.aarch64+debug #1\n[   41.665838] Hardware name: NVIDIA NVIDIA Jetson AGX Orin Developer Kit/Jetson, BIOS 36.3.0-gcid-35594366 02/26/2024\n[   41.672555] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n[   41.679636] pc : __mutex_lock+0x670/0x878\n[   41.683834] lr : __mutex_lock+0x670/0x878\n[   41.688035] sp : ffff800084b77090\n[   41.691446] x29: ffff800084b77160 x28: ffffdd4bebf7b000 x27: ffffdd4be96b1000\n[   41.698799] x26: 1fffe0002308361c x25: 1ffff0001096ee18 x24: 0000000000000000\n[   41.706149] x23: 0000000000000000 x22: 0000000000000002 x21: ffffdd4be6e3c7a0\n[   41.713500] x20: ffff800084b770f0 x19: ffff00011841b1e8 x18: 0000000000000000\n[   41.720675] x17: 0000000000000000 x16: 0000000000000000 x15: 0720072007200720\n[   41.728023] x14: 0000000000000000 x13: 0000000000000001 x12: ffff6001a96eaab3\n[   41.735375] x11: 1fffe001a96eaab2 x10: ffff6001a96eaab2 x9 : ffffdd4be4838bbc\n[   41.742723] x8 : 00009ffe5691554e x7 : ffff000d4b755593 x6 : 0000000000000001\n[   41.749985] x5 : ffff000d4b755590 x4 : 1fffe0001d88f001 x3 : dfff800000000000\n[   41.756988] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff0000ec478000\n[   41.764251] Call trace:\n[   41.766695]  __mutex_lock+0x670/0x878\n[   41.770373]  mutex_lock_nested+0x2c/0x40\n[   41.774134]  host1x_intr_start+0x54/0xf8 [host1x]\n[   41.778863]  host1x_runtime_resume+0x150/0x228 [host1x]\n[   41.783935]  pm_generic_runtime_resume+0x84/0xc8\n[   41.788485]  __rpm_callback+0xa0/0x478\n[   41.792422]  rpm_callback+0x15c/0x1a8\n[   41.795922]  rpm_resume+0x698/0xc08\n[   41.799597]  __pm_runtime_resume+0xa8/0x140\n[   41.803621]  host1x_probe+0x810/0xbc0 [host1x]\n[   41.807909]  platform_probe+0xcc/0x1a8\n[   41.811845]  really_probe+0x188/0x800\n[   41.815347]  __driver_probe_device+0x164/0x360\n[   41.819810]  driver_probe_device+0x64/0x1a8\n[   41.823834]  __driver_attach+0x180/0x490\n[   41.827773]  bus_for_each_dev+0x104/0x1a0\n[   41.831797]  driver_attach+0x44/0x68\n[   41.835296]  bus_add_driver+0x23c/0x4e8\n[   41.839235]  driver_register+0x15c/0x3a8\n[   41.843170]  __platform_register_drivers+0xa4/0x208\n[   41.848159]  tegra_host1x_init+0x4c/0xff8 [host1x]\n[   41.853147]  do_one_initcall+0xd4/0x380\n[   41.856997]  do_init_module+0x1dc/0x698\n[   41.860758]  load_module+0xc70/0x1300\n[   41.864435]  __do_sys_init_module+0x1a8/0x1d0\n[   41.868721]  __arm64_sys_init_module+0x74/0xb0\n[   41.873183]  invoke_syscall.constprop.0+0xdc/0x1e8\n[   41.877997]  do_el0_svc+0x154/0x1d0\n[   41.881671]  el0_svc+0x54/0x140\n[   41.884820]  el0t_64_sync_handler+0x120/0x130\n[   41.889285]  el0t_64_sync+0x1a4/0x1a8\n[   41.892960] irq event stamp: 69737\n[   41.896370] hardirqs last  enabled at (69737): [\u003cffffdd4be6d7768c\u003e] _raw_spin_unlock_irqrestore+0x44/0xe8\n[   41.905739] hardirqs last disabled at (69736):\n---truncated---","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":"gpu: host1x: Fix a use of uninitialized mutex","id":"CVE-2025-21824","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: Cancel the running bpf_timer through kworker for PREEMPT_RT","id":"CVE-2025-21825"},"packages":[],"prev":{"headline":"batman-adv: Drop unmanaged ELP metric worker","id":"CVE-2025-21823"},"products":["Linux"],"published":"2025-02-27","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"A use of an uninitialized mutex in the Linux kernel host1x driver can cause a system warning and potential crash when debug options are enabled.","url":"https://insights.sbomify.com/CVE-2025-21824/"}