{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74331 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74331 is a denial of service vulnerability in Linux, published on 15 Aug 2026. 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-2026-74331 and fix it if it is affected.\n\nWhat it is: CVE-2026-74331 is a denial of service vulnerability in Linux, published on 15 Aug 2026. 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-2026-74331 in the wild and no public exploit code.\n\nAffected product: Linux. 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-2026-74331/ (Markdown: https://insights.sbomify.com/CVE-2026-74331/index.md)","id":"CVE-2026-74331","markdown":"https://insights.sbomify.com/CVE-2026-74331/index.md","name":"CVE-2026-74331","record":{"aliases":["BELL-CVE-2026-74331","DEBIAN-CVE-2026-74331","GHSA-2whr-3329-9322","UBUNTU-CVE-2026-74331"],"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":"none","summary":"A recursive locking deadlock in the Linux kernel firmware loader can cause a system hang during suspend or hibernation when memory allocation fails.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfirmware_loader: Fix recursive lock in device_cache_fw_images()\n\nA recursive locking deadlock can occur in the firmware loader's power\nmanagement notification handler.\n\nDuring system suspend or hibernation preparation, fw_pm_notify() calls\ndevice_cache_fw_images(). This function acquires fw_lock to set the\nfirmware cache state to FW_LOADER_START_CACHE and then iterates over all\ndevices using dpm_for_each_dev() while still holding the lock.\n\nFor each device, dev_cache_fw_image() schedules asynchronous work to cache\nthe firmware. If memory allocation for the async work entry fails (e.g., in\nout-of-memory conditions), async_schedule_node_domain() falls back to\nexecuting the work function synchronously in the current thread.\n\nThe synchronous execution path (__async_dev_cache_fw_image() -\u003e\ncache_firmware() -\u003e request_firmware() -\u003e assign_fw()) attempts to acquire\nfw_lock again. Since the current thread already holds fw_lock, this results\nin a recursive locking deadlock.\n\nFix this by releasing fw_lock immediately after updating the cache state\nand before calling dpm_for_each_dev(). The lock is only needed to protect\nthe state update. Concurrent firmware requests will correctly see the\nFW_LOADER_START_CACHE state and use the piggyback mechanism, which is\nindependently protected by its own fwc-\u003ename_lock.","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":"firmware_loader: Fix recursive lock in device_cache_fw_images()","id":"CVE-2026-74331","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"ASoC: amd: acp-sdw-sof: Bound DAI link iteration","id":"CVE-2026-74332"},"packages":[],"prev":{"headline":"configfs: fix lockless traversals of -\u003es_children","id":"CVE-2026-74330"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-17","vendors":["Linux"]},"summary":"A recursive locking deadlock in the Linux kernel firmware loader can cause a system hang during suspend or hibernation when memory allocation fails.","url":"https://insights.sbomify.com/CVE-2026-74331/"}