{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74401 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74401 is a critical use after free vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-74401 and fix it if it is affected.\n\nWhat it is: CVE-2026-74401 is a critical use after free vulnerability in Linux, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-74401 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-74401/ (Markdown: https://insights.sbomify.com/CVE-2026-74401/index.md)","id":"CVE-2026-74401","markdown":"https://insights.sbomify.com/CVE-2026-74401/index.md","name":"CVE-2026-74401","record":{"aliases":["BELL-CVE-2026-74401","DEBIAN-CVE-2026-74401","GHSA-wgc9-j6gh-934m","UBUNTU-CVE-2026-74401"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel DLM","requires_auth":"none","summary":"A race condition in the Linux kernel Distributed Lock Manager can lead to use-after-free, potentially allowing local attackers to execute code or escalate privileges.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndlm: fix add msg handle in send_queue ordered\n\nIn a benchmark scenario triggering a lot of requests that triggers a lot\nof DLM messages on the network it can be that the mh-\u003eseq is not ordered\naccording the oldest seq number. This ordering is required by\ndlm_receive_ack as \"before(mh-\u003eseq, seq)\" will stop to check for older\nsequence numbers that are ordered in the tail of \"node-\u003esend_queue\".\n\nThe side effects of not having it correct ordered regarding\n\"before(mh-\u003eseq, seq)\" are refcounting issues and use-after free.\n\nI only was able to reproduce this issue in a experimental DLM branch\nand a user space DLM benchmark that uses io_uring. After changing this I\ndon't experienced any refcounting with the sending buffer issues anymore.","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":"dlm: fix add msg handle in send_queue ordered","id":"CVE-2026-74401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"crypto: atmel-sha204a - fix blocking and non-blocking rng logic","id":"CVE-2026-74402"},"packages":[],"prev":{"headline":"bpf: fix crash in bpf_[set|remove]_dentry_xattr for negative dentries","id":"CVE-2026-74400"},"products":["Linux"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Distributed Lock Manager can lead to use-after-free, potentially allowing local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-74401/"}