{"api_version":"1","generated_at":"2026-08-16T18:54:31+00:00","cve":"CVE-2026-74540","urls":{"html":"https://cve.report/CVE-2026-74540","api":"https://cve.report/api/cve/CVE-2026-74540.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74540","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74540"},"summary":{"title":"Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp\n\nl2cap_le_connect_rsp() obtains a channel via\n__l2cap_get_chan_by_ident() but neither holds a reference nor uses\nl2cap_chan_hold_unless_zero() before locking and operating on it.\nA concurrent l2cap_chan_del() triggered by a remote disconnect can\nfree the channel between the lookup and l2cap_chan_lock(), causing\na use-after-free.\n\nThe BR/EDR counterpart l2cap_connect_rsp() and the sibling handler\nl2cap_le_command_rej() already use l2cap_chan_hold_unless_zero()\nto safely hold a reference, but l2cap_le_connect_rsp() was left\nunprotected.\n\nFix by adding l2cap_chan_hold_unless_zero() after the ident lookup\nand l2cap_chan_put() on the exit path, consistent with other L2CAP\nresponse handlers.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:59","updated_at":"2026-08-15 13:17:59"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136","name":"https://git.kernel.org/stable/c/58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c4740e7f23ff9a8210198d8b4703259e21b9f69d","name":"https://git.kernel.org/stable/c/c4740e7f23ff9a8210198d8b4703259e21b9f69d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/09f447accc2570751e7d17f0dc0788b40d3edade","name":"https://git.kernel.org/stable/c/09f447accc2570751e7d17f0dc0788b40d3edade","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/522b730c62c53a1981604fd73524697fd347830d","name":"https://git.kernel.org/stable/c/522b730c62c53a1981604fd73524697fd347830d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/fd4c1e301bdec60a40728ea37de531cbccda501a","name":"https://git.kernel.org/stable/c/fd4c1e301bdec60a40728ea37de531cbccda501a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74540","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74540","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f1496dee9cbde2a62821f4441dadb0d3360f60c3 fd4c1e301bdec60a40728ea37de531cbccda501a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f1496dee9cbde2a62821f4441dadb0d3360f60c3 522b730c62c53a1981604fd73524697fd347830d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f1496dee9cbde2a62821f4441dadb0d3360f60c3 58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f1496dee9cbde2a62821f4441dadb0d3360f60c3 09f447accc2570751e7d17f0dc0788b40d3edade git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected f1496dee9cbde2a62821f4441dadb0d3360f60c3 c4740e7f23ff9a8210198d8b4703259e21b9f69d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.151 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.103 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["net/bluetooth/l2cap_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"fd4c1e301bdec60a40728ea37de531cbccda501a","status":"affected","version":"f1496dee9cbde2a62821f4441dadb0d3360f60c3","versionType":"git"},{"lessThan":"522b730c62c53a1981604fd73524697fd347830d","status":"affected","version":"f1496dee9cbde2a62821f4441dadb0d3360f60c3","versionType":"git"},{"lessThan":"58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136","status":"affected","version":"f1496dee9cbde2a62821f4441dadb0d3360f60c3","versionType":"git"},{"lessThan":"09f447accc2570751e7d17f0dc0788b40d3edade","status":"affected","version":"f1496dee9cbde2a62821f4441dadb0d3360f60c3","versionType":"git"},{"lessThan":"c4740e7f23ff9a8210198d8b4703259e21b9f69d","status":"affected","version":"f1496dee9cbde2a62821f4441dadb0d3360f60c3","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/bluetooth/l2cap_core.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.14"},{"lessThan":"3.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.151","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.103","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.151","versionStartIncluding":"3.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.103","versionStartIncluding":"3.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"3.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"3.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc6","versionStartIncluding":"3.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp\n\nl2cap_le_connect_rsp() obtains a channel via\n__l2cap_get_chan_by_ident() but neither holds a reference nor uses\nl2cap_chan_hold_unless_zero() before locking and operating on it.\nA concurrent l2cap_chan_del() triggered by a remote disconnect can\nfree the channel between the lookup and l2cap_chan_lock(), causing\na use-after-free.\n\nThe BR/EDR counterpart l2cap_connect_rsp() and the sibling handler\nl2cap_le_command_rej() already use l2cap_chan_hold_unless_zero()\nto safely hold a reference, but l2cap_le_connect_rsp() was left\nunprotected.\n\nFix by adding l2cap_chan_hold_unless_zero() after the ident lookup\nand l2cap_chan_put() on the exit path, consistent with other L2CAP\nresponse handlers."}],"providerMetadata":{"dateUpdated":"2026-08-15T12:27:51.522Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/fd4c1e301bdec60a40728ea37de531cbccda501a"},{"url":"https://git.kernel.org/stable/c/522b730c62c53a1981604fd73524697fd347830d"},{"url":"https://git.kernel.org/stable/c/58e3c5289ad230a7e24ae4b0c7b43f5ee6e32136"},{"url":"https://git.kernel.org/stable/c/09f447accc2570751e7d17f0dc0788b40d3edade"},{"url":"https://git.kernel.org/stable/c/c4740e7f23ff9a8210198d8b4703259e21b9f69d"}],"title":"Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74540","datePublished":"2026-08-15T12:27:51.522Z","dateReserved":"2026-08-15T05:44:03.913Z","dateUpdated":"2026-08-15T12:27:51.522Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:59","lastModifiedDate":"2026-08-15 13:17:59","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74540","Ordinal":"1","Title":"Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp","CVE":"CVE-2026-74540","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74540","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp\n\nl2cap_le_connect_rsp() obtains a channel via\n__l2cap_get_chan_by_ident() but neither holds a reference nor uses\nl2cap_chan_hold_unless_zero() before locking and operating on it.\nA concurrent l2cap_chan_del() triggered by a remote disconnect can\nfree the channel between the lookup and l2cap_chan_lock(), causing\na use-after-free.\n\nThe BR/EDR counterpart l2cap_connect_rsp() and the sibling handler\nl2cap_le_command_rej() already use l2cap_chan_hold_unless_zero()\nto safely hold a reference, but l2cap_le_connect_rsp() was left\nunprotected.\n\nFix by adding l2cap_chan_hold_unless_zero() after the ident lookup\nand l2cap_chan_put() on the exit path, consistent with other L2CAP\nresponse handlers.","Type":"Description","Title":"Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp"}]}}}