{"api_version":"1","generated_at":"2026-10-28T16:52:39+00:00","cve":"CVE-2026-99008","urls":{"html":"https://cve.report/CVE-2026-99008","api":"https://cve.report/api/cve/CVE-2026-99008.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99008","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99008"},"summary":{"title":"Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown\n\nsyzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an\nRFCOMM tty is closed.\n\nrfcomm_dev_add() puts the new device on rfcomm_dev_list first and only\nthen registers the tty device and saves it in dev->tty_dev. If that\nregistration fails, dev->tty_dev is never set at all. The device can be\nlooked up in the meantime, so an open() of /dev/rfcommN gets through\nrfcomm_tty_install() and attaches to it. When that tty is closed again,\nrfcomm_dev_shutdown() uses dev->tty_dev without checking it:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]\n  RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131\n  Call Trace:\n   tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372\n   tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705\n   tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718\n   __fput+0x418/0xa50 fs/file_table.c:512\n\nrfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the\nsame check to rfcomm_dev_shutdown(), so the tty device is only moved\nwhen it was actually registered.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-10-23 13:17:23","updated_at":"2026-10-23 13:17:23"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/d0aef0b0374678153244f162df507106d728af39","name":"https://git.kernel.org/stable/c/d0aef0b0374678153244f162df507106d728af39","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/d5c372ad03330f02962d4860df4d355ab25487df","name":"https://git.kernel.org/stable/c/d5c372ad03330f02962d4860df4d355ab25487df","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a661f401f83b8462f2d424e0a1a72b7681e92ea2","name":"https://git.kernel.org/stable/c/a661f401f83b8462f2d424e0a1a72b7681e92ea2","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/08e90633377f1b2567ab5ad6810b74c552246a07","name":"https://git.kernel.org/stable/c/08e90633377f1b2567ab5ad6810b74c552246a07","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/3fd5164bdb04635caa7942ddb554b0ec699a9433","name":"https://git.kernel.org/stable/c/3fd5164bdb04635caa7942ddb554b0ec699a9433","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99008","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99008","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cad348a17e170451ea8688b532a6ca3e98c63b60 d5c372ad03330f02962d4860df4d355ab25487df git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cad348a17e170451ea8688b532a6ca3e98c63b60 3fd5164bdb04635caa7942ddb554b0ec699a9433 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cad348a17e170451ea8688b532a6ca3e98c63b60 a661f401f83b8462f2d424e0a1a72b7681e92ea2 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cad348a17e170451ea8688b532a6ca3e98c63b60 d0aef0b0374678153244f162df507106d728af39 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected cad348a17e170451ea8688b532a6ca3e98c63b60 08e90633377f1b2567ab5ad6810b74c552246a07 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.12","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.12 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.160 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.113 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.57 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.11 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3 * 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/rfcomm/tty.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"d5c372ad03330f02962d4860df4d355ab25487df","status":"affected","version":"cad348a17e170451ea8688b532a6ca3e98c63b60","versionType":"git"},{"lessThan":"3fd5164bdb04635caa7942ddb554b0ec699a9433","status":"affected","version":"cad348a17e170451ea8688b532a6ca3e98c63b60","versionType":"git"},{"lessThan":"a661f401f83b8462f2d424e0a1a72b7681e92ea2","status":"affected","version":"cad348a17e170451ea8688b532a6ca3e98c63b60","versionType":"git"},{"lessThan":"d0aef0b0374678153244f162df507106d728af39","status":"affected","version":"cad348a17e170451ea8688b532a6ca3e98c63b60","versionType":"git"},{"lessThan":"08e90633377f1b2567ab5ad6810b74c552246a07","status":"affected","version":"cad348a17e170451ea8688b532a6ca3e98c63b60","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["net/bluetooth/rfcomm/tty.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.12"},{"lessThan":"3.12","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.160","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.113","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.57","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.160","versionStartIncluding":"3.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.113","versionStartIncluding":"3.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.57","versionStartIncluding":"3.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.11","versionStartIncluding":"3.12","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3","versionStartIncluding":"3.12","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown\n\nsyzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an\nRFCOMM tty is closed.\n\nrfcomm_dev_add() puts the new device on rfcomm_dev_list first and only\nthen registers the tty device and saves it in dev->tty_dev. If that\nregistration fails, dev->tty_dev is never set at all. The device can be\nlooked up in the meantime, so an open() of /dev/rfcommN gets through\nrfcomm_tty_install() and attaches to it. When that tty is closed again,\nrfcomm_dev_shutdown() uses dev->tty_dev without checking it:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]\n  RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131\n  Call Trace:\n   tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372\n   tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705\n   tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718\n   __fput+0x418/0xa50 fs/file_table.c:512\n\nrfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the\nsame check to rfcomm_dev_shutdown(), so the tty device is only moved\nwhen it was actually registered."}],"providerMetadata":{"dateUpdated":"2026-10-23T12:20:33.355Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/d5c372ad03330f02962d4860df4d355ab25487df"},{"url":"https://git.kernel.org/stable/c/3fd5164bdb04635caa7942ddb554b0ec699a9433"},{"url":"https://git.kernel.org/stable/c/a661f401f83b8462f2d424e0a1a72b7681e92ea2"},{"url":"https://git.kernel.org/stable/c/d0aef0b0374678153244f162df507106d728af39"},{"url":"https://git.kernel.org/stable/c/08e90633377f1b2567ab5ad6810b74c552246a07"}],"title":"Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99008","datePublished":"2026-10-23T12:20:33.355Z","dateReserved":"2026-09-25T10:25:14.385Z","dateUpdated":"2026-10-23T12:20:33.355Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-10-23 13:17:23","lastModifiedDate":"2026-10-23 13:17:23","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99008","Ordinal":"1","Title":"Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_sh","CVE":"CVE-2026-99008","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99008","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_shutdown\n\nsyzbot hit a NULL pointer dereference in rfcomm_dev_shutdown() when an\nRFCOMM tty is closed.\n\nrfcomm_dev_add() puts the new device on rfcomm_dev_list first and only\nthen registers the tty device and saves it in dev->tty_dev. If that\nregistration fails, dev->tty_dev is never set at all. The device can be\nlooked up in the meantime, so an open() of /dev/rfcommN gets through\nrfcomm_tty_install() and attaches to it. When that tty is closed again,\nrfcomm_dev_shutdown() uses dev->tty_dev without checking it:\n\n  Oops: general protection fault, probably for non-canonical address\n  KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]\n  RIP: 0010:rfcomm_dev_shutdown+0x48/0xb0 net/bluetooth/rfcomm/tty.c:131\n  Call Trace:\n   tty_port_shutdown+0x1bf/0x220 drivers/tty/tty_port.c:372\n   tty_port_close+0x4e/0x150 drivers/tty/tty_port.c:705\n   tty_release+0x359/0x1670 drivers/tty/tty_io.c:1718\n   __fput+0x418/0xa50 fs/file_table.c:512\n\nrfcomm_dev_destruct() already copes with a NULL dev->tty_dev. Add the\nsame check to rfcomm_dev_shutdown(), so the tty device is only moved\nwhen it was actually registered.","Type":"Description","Title":"Bluetooth: RFCOMM: Fix NULL tty_dev dereference in rfcomm_dev_sh"}]}}}