{"id":"AZL-110852","summary":"CVE-2026-99008 affecting package kernel 6.6.157.1-1","details":"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-\u003etty_dev. If that\nregistration fails, dev-\u003etty_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-\u003etty_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-\u003etty_dev. Add the\nsame check to rfcomm_dev_shutdown(), so the tty device is only moved\nwhen it was actually registered.","modified":"2026-10-25T05:30:37Z","published":"2026-10-23T13:17:23Z","upstream":["CVE-2026-99008"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99008"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.157.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-110852.json"}}],"schema_version":"1.9.0"}