{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74513 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74513 is a high-severity use after free 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-74513 and fix it if it is affected.\n\nWhat it is: CVE-2026-74513 is a high-severity use after free 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-74513 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-74513/ (Markdown: https://insights.sbomify.com/CVE-2026-74513/index.md)","id":"CVE-2026-74513","markdown":"https://insights.sbomify.com/CVE-2026-74513/index.md","name":"CVE-2026-74513","record":{"aliases":["BELL-CVE-2026-74513","DEBIAN-CVE-2026-74513","GHSA-p4c6-79fv-gqjg","UBUNTU-CVE-2026-74513"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel DIBS loopback driver allows a use-after-free, potentially enabling 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":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/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\ndibs: fix use-after-free of dmb_node in loopback attach/detach/unregister\n\ndibs_lo_attach_dmb(), dibs_lo_detach_dmb() and dibs_lo_unregister_dmb()\nlook up the dmb_node under dmb_ht_lock, drop the lock and only then\noperate on the node's refcount. Nothing keeps the node alive across\nthat window: __dibs_lo_unregister_dmb() removes the node from the hash\ntable under the write lock and immediately frees it.\n\nA concurrent final put can therefore free the node between the lookup\nand the refcount operation:\n\nCPU0 (attach)                     CPU1 (owner unregisters)\n\nread_lock_bh(\u0026dmb_ht_lock)\nfind dmb_node (refcnt == 1)\nread_unlock_bh(\u0026dmb_ht_lock)\n                                  refcount_dec_and_test() 1 -\u003e 0\n                                  write_lock_bh(\u0026dmb_ht_lock)\n                                  hash_del(\u0026dmb_node-\u003elist)\n                                  write_unlock_bh(\u0026dmb_ht_lock)\n                                  kfree(dmb_node)\nrefcount_inc_not_zero(\u0026dmb_node-\u003erefcnt)  \u003c-- use-after-free\n\nThe same window exists for the refcount_dec_and_test() calls in the\ndetach and unregister paths.\n\nClose the race structurally by making hash table membership and the\nrefcount transitions atomic with respect to each other:\n\n- Perform the final refcount_dec_and_test() and hash_del() in a single\n  dmb_ht_lock write-side critical section, in both the unregister and\n  the detach path. Freeing the node still happens after the lock is\n  dropped, which is safe because a node whose refcount reached zero has\n  left the hash table and can no longer be found.\n\n- This establishes the invariant that any node found in the hash table\n  holds at least one reference, and that the final reference can only\n  be dropped under the write lock. dibs_lo_attach_dmb() can thus take\n  its reference with a plain refcount_inc() while still holding the\n  read lock; refcount_inc_not_zero() is no longer needed.\n\n__dibs_lo_unregister_dmb() no longer touches the hash table and is\nrenamed to dibs_lo_free_dmb() accordingly.\n\nNote: commit cc21191b584c (\"dibs: Move data path to dibs layer\") moved\nthe code to its current location; the race was introduced earlier by\ncommit c3a910f2380f (\"net/smc: implement DMB-merged operations of\nloopback-ism\").\n\nTested SMC-D via ISM and dibs loopback.","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":"dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister","id":"CVE-2026-74513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"KVM: s390: pci: Fix memory accounting for pinned/unpinned pages","id":"CVE-2026-74514"},"packages":[],"prev":{"headline":"audit: fix potential use-after-free in audit_del_rule()","id":"CVE-2026-74512"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A race condition in the Linux kernel DIBS loopback driver allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-74513/"}