{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74534 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74534 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-74534 and fix it if it is affected.\n\nWhat it is: CVE-2026-74534 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-74534 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-74534/ (Markdown: https://insights.sbomify.com/CVE-2026-74534/index.md)","id":"CVE-2026-74534","markdown":"https://insights.sbomify.com/CVE-2026-74534/index.md","name":"CVE-2026-74534","record":{"aliases":["BELL-CVE-2026-74534","DEBIAN-CVE-2026-74534","GHSA-f45g-2gpw-92wg","UBUNTU-CVE-2026-74534"],"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 Bluetooth","requires_auth":"none","summary":"A race condition in the Linux kernel Bluetooth ISO subsystem causes a 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":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/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\nBluetooth: ISO: fix refcounting of iso_conn\n\niso_conn_del() and iso_chan_del() have a race that results to double-put\nof iso_conn:\n\n    [Task hdev-\u003eworkqueue]         [Task 2]\n    iso_conn_del                   iso_chan_del\n      iso_conn_hold_unless_zero      iso_conn_lock\n      iso_conn_lock                  conn-\u003esk = NULL\n                                     iso_conn_unlock\n      sk = iso_sock_hold(conn)  \u003c---------´\n      if (!sk) iso_conn_put          iso_conn_put\n      iso_conn_put /* UAF */\n\nThe extra put for !sk in iso_conn_del() is currently required since\nfailing iso_chan_add() may leave iso_conn not associated with any sk.\n\nFix by having iso_pi(sk)-\u003econn own refcount when non-NULL, so\niso_conn_del does not need to put it.  Adjust the iso_conn_add()\nrefcounting so that conn is put if it does not get associated with an\nsk.","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":"Bluetooth: ISO: fix refcounting of iso_conn","id":"CVE-2026-74534","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":"Bluetooth: ISO: avoid deadlocks in iso_sock_timeout","id":"CVE-2026-74535"},"packages":[],"prev":{"headline":"Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero","id":"CVE-2026-74533"},"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-23","vendors":["Linux"]},"summary":"A race condition in the Linux kernel Bluetooth ISO subsystem causes a use-after-free, potentially allowing local attackers to execute code or escalate privileges.","url":"https://insights.sbomify.com/CVE-2026-74534/"}