)]}'
{
  "log": [
    {
      "commit": "da3cc02587c629420603df4395179ec82955c941",
      "tree": "f56820ddae882453ec642f1ae5808e63dafd5b3d",
      "parents": [
        "98bab74158b0cb0b8e890adfaaf8b098b4a5e3ce"
      ],
      "author": {
        "name": "Xu Rao",
        "email": "raoxu@uniontech.com",
        "time": "Thu Nov 12 16:26:01 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 12 14:37:10 2026 -0500"
      },
      "message": "Bluetooth: hci_vhci: Report write readiness with queued input\n\nvhci_poll() returns only EPOLLIN and EPOLLRDNORM when readq is nonempty,\ndropping the write readiness bits it reports when the queue is empty.\nHowever, vhci_write() does not wait for readq to drain: incoming frames\nare handled independently by vhci_get_user().\n\nAs a result, userspace polling only for write readiness can time out or\nremain asleep while input is queued, even though it could submit a\nframe. Applications that drain input before waiting to write avoid this\ncase.\n\nAlways include EPOLLOUT and EPOLLWRNORM in the readiness mask, and add\nEPOLLIN and EPOLLRDNORM when readq contains data. Keep the existing wait\nqueue registration and empty-queue behavior unchanged.\n\nSigned-off-by: Xu Rao \u003craoxu@uniontech.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "98bab74158b0cb0b8e890adfaaf8b098b4a5e3ce",
      "tree": "1e14f023db7113af76aca99b34a35f7614da8436",
      "parents": [
        "c9644a9257d15b27882f4afb36c0341f81f8f35b",
        "3b069de8a5d688c7e8381b99d6cdb7467fcae0de"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 12 14:36:15 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 12 14:36:15 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "3b069de8a5d688c7e8381b99d6cdb7467fcae0de",
      "tree": "86af0a1e01e7a01423e72704f44926bae3d6b7f5",
      "parents": [
        "f3183d7ad10120437bcc3f4a751cd256ba69793f"
      ],
      "author": {
        "name": "Amir Abudubai",
        "email": "amirabudubai@gmail.com",
        "time": "Wed Nov 11 15:49:05 2026 -0600"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 12 14:35:14 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Fix size check for receive buffer space\n\nCheck that available receive space covers a full MTU-sized SDU and its\noverhead, rather than just the overhead. Otherwise, credits can be\nexhausted before an SDU is completed. This could result in a deadlock under\nsome configurations and SDU combinations.\n\nThis follows the SDU-sized credit policy from commit 96cd8eaa131f\n(\"Bluetooth: L2CAP: Derive rx credits from MTU and MPS\"). Clarify the\ncomment by replacing \"packet\" with \"SDU\".\n\nFixes: ce60b9231b66 (\"Bluetooth: compute LE flow credits based on recvbuf space\")\nSigned-off-by: Amir Abudubai \u003camirabudubai@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f3183d7ad10120437bcc3f4a751cd256ba69793f",
      "tree": "fe2e90b4dd7522c27376ef4f7aa7b8cd2930fb91",
      "parents": [
        "1752a2c40059f845123946e01646b8a1798eeea4"
      ],
      "author": {
        "name": "Weihong Guan",
        "email": "weihong.guan@gmail.com",
        "time": "Thu Nov 12 03:34:28 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 12 14:28:26 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Drop the command\u0027s sk reference\n\nhci_cmd_sync_alloc() takes a reference on the sk a command is sent for\n(sock_hold()), and hci_cmd_sync_complete() means to drop it, but looks\nfor the sk in the response skb, which never carries one. The reference\nis never dropped: every command sent with an sk leaks it, and with it\nthe sk and a reference on the bluetooth module.\n\nThe commands sent with an sk are LE Remove Advertising Set and LE\nClear Advertising Sets, for MGMT\u0027s Remove Advertising and the instance\nremovals, and Read Local OOB (Extended) Data. After each, the module\u0027s\nrefcnt stays one higher with no socket left open, and the module can\u0027t\nbe unloaded until a reboot.\n\nDrop the reference from the request command, hdev-\u003ereq_skb, before\nfreeing it.\n\nFixes: cba6b758711c (\"Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 2\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Weihong Guan \u003cweihong.guan@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "c9644a9257d15b27882f4afb36c0341f81f8f35b",
      "tree": "1c2cc45b40027db9705b4c7781379935294a04f8",
      "parents": [
        "0a30ad8313927ed34b8d8102a71d93aade3a157d"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu May 28 13:39:24 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:20:14 2026 -0500"
      },
      "message": "Bluetooth: Add EKS Opportunistic Encryption support\n\nAdd support for opportunistic encryption with Encryption Key Schedule,\nwhich encrypts a link without pairing when both devices support it:\n\n - The Opportunistic Encryption (Host Support) feature bit (Link Layer\n   feature bit 90) is set with LE Set Host Feature during\n   initialization, and eks_oppt_capable() checks the remote supports it.\n - When the remote features are read as Central and there is no LTK for\n   the peer, LE Enable Encryption v2 is sent with Encryption set to\n   opportunistic. The checks are repeated right before the command is\n   sent, so it is skipped if the link is gone, already encrypted, has\n   SMP encryption pending or SMP pairing has started in the meantime,\n   and the MIC length is taken at that point so the one requested by\n   L2CAP is used.\n - The new HCI_CONN_OPP_ENCRYPT flag marks the request in flight and,\n   once Encryption Change v3 reports it, an opportunistically encrypted\n   link, which is also marked as encrypted with AES-CCM. It doesn\u0027t\n   raise the security level, as it is not authenticated, and since it\n   has no key from pairing the L2CAP key size check is skipped for it.\n   A failure, or a command that cannot be sent, just leaves the link\n   unencrypted, as it was. Since opportunistic encryption can only be\n   started on an unencrypted link, reporting it for a link with a key\n   from pairing is a downgrade, which disconnects the link. A failure on\n   an opportunistically encrypted link is handled as for any encrypted\n   link, without the encryption flags it had.\n - SMP only distributes keys once a key from pairing encrypts the link,\n   not on opportunistic encryption.\n - HCI_CONN_ENCRYPT_PEND is not used for opportunistic encryption, so\n   it doesn\u0027t block SMP. Pairing over such a link completes: the Key\n   Refresh Complete of its key clears HCI_CONN_OPP_ENCRYPT and is\n   handled as Encryption Change is for an unencrypted link.\n - A Key Refresh Complete reporting opportunistic encryption, such as\n   one changing the MIC length, keeps the link opportunistically\n   encrypted. Opportunistic encryption can only be started on an\n   unencrypted link, so on a link with a key from pairing it would be a\n   downgrade, which disconnects the link.\n - The feature can be turned off with the MGMT system configuration TLV\n   0x0024; it is on by default. Changing it while the controller is up\n   updates the feature bit, which the controller only allows when there\n   are no connections.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "0a30ad8313927ed34b8d8102a71d93aade3a157d",
      "tree": "be686dfa85f89180fb4ba9f19f4e38141d0e59f3",
      "parents": [
        "daee0133436f0db19456ea184c65bf4d71c36c66"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed May 27 14:43:26 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:20:03 2026 -0500"
      },
      "message": "Bluetooth: Add HCI_OP_LE_SET_HDT_DEFAULT_PARAMS support\n\nAdd support for LE Set HDT Default Parameters, which sets the MIC\nlength, packet format and ACL rates the controller prefers on the LE\nHDT PHY. The command is sent during controller initialization when the\ncontroller supports HDT and the command, with the rates limited to the\nones the controller supports, preferring all of them if that leaves\nnone, and a packet format the controller doesn\u0027t support, Packet\nFormat 1 being optional, replaced by any supported one, since the\ncontroller would reject either and fail the initialization.\n\nThe defaults are stored in hci_dev, 128-bit MIC, no packet format\npreference and all HDT rates, and exposed through the MGMT system\nconfiguration TLVs 0x0021-0x0023 so userspace can change them; changing\nthem while the controller is up sends the command again.\n\nThe spec reserves the values other than 64 or 128 bits for the MIC\nlength (the 32-bit MIC being the one of the GFSK PHYs), the packet\nformats above 1 and the rate bits above HDT7.5. A TLV with a reserved\nvalue is rejected with Invalid Parameters, rather than sent to a\ncontroller that rejects it, which would fail the initialization.\n\nThe default MIC length applies when the connection did not request\none: to LE Enable Encryption v2, LE Set CIG Parameters v2 and LE Create\nBIG v2, so ACL, CIS and BIS are set up with the MIC length the host was\ntold to use.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "daee0133436f0db19456ea184c65bf4d71c36c66",
      "tree": "48a4e035e8e98d0d8ba75eb5bdce0d70993cffde",
      "parents": [
        "0c16445e4e7301fd8d12b2e12a65a8dd6dc2d0bd"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue May 26 18:06:43 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:19:54 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Add MIC length validation for HDT PHY\n\nAdd a mic_len field to struct bt_security so userspace can require a\nminimum MIC length on an L2CAP channel with BT_SECURITY, and read the\nMIC length in use on the link back. The field is added at the end of\nthe struct, so the shorter struct is still accepted by L2CAP and RFCOMM,\nleaving mic_len unset, and values other than 32, 64 and 128 bits are\nrejected.\n\nThe MIC length a channel requires is requested on the connection on\nevery path starting LE security, so LE Enable Encryption v2 asks for\nit, while the MIC length the controller reports with Encryption Change\nv3 and Encryption Key Refresh Complete v2 is kept separately, so a\nrequest never stands for what is in use. When a connection is\nencrypted on the LE HDT PHY with a MIC shorter than the channel\nrequires, the LE Credit Based and Enhanced Credit Based connection\nrequests are rejected with MIC Length Too Short.\n\nThe reported MIC length only applies on the LE HDT PHY, the MIC is\nalways 32 bits on the GFSK PHYs, so hci_conn_mic_len() reports it as\nsuch both for the check and for BT_SECURITY.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "0c16445e4e7301fd8d12b2e12a65a8dd6dc2d0bd",
      "tree": "3fb47b0712c48ac31f3431c01d30ac03deceb466",
      "parents": [
        "d9b633525975773b6ddd512870a53de38b307779"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Feb 17 16:23:07 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:19:44 2026 -0500"
      },
      "message": "Bluetooth: Add initial support for EKS\n\nAdd support for Encryption Key Schedule (EKS) introduced in Bluetooth\n7.0:\n\n - LE Enable Encryption v2, which replaces LE Start Encryption on EKS\n   capable controllers and carries the MIC length to use on the LE HDT\n   PHY. SMP now starts encryption through hci_le_enable_encrypt(),\n   which picks the version the controller supports, outside of the RCU\n   read-side section since queueing the command may sleep. If it can\u0027t\n   be queued SMP fails the pairing or doesn\u0027t consider the encryption\n   started. A Command Status error disconnects the link as it does for\n   LE Start Encryption, and so does a command that fails without one,\n   such as one that couldn\u0027t be sent. The Command Status error of LE\n   Start Encryption now also clears the pending encryption, so the two\n   don\u0027t both act on it. The command, which carries the key, is freed\n   with kfree_sensitive().\n - Encryption Change v3 and Encryption Key Refresh Complete v2, enabled\n   through Event Mask Page 2, which report the MIC length and whether\n   the key schedule is in use. The encryption change and key refresh\n   handling is moved to helpers shared by every version of the events.\n - The encryption key size Encryption Change v3 reports for BR/EDR is\n   used instead of reading it with HCI_Read_Encryption_Key_Size, saving\n   a round trip; it is validated the same way, in a helper shared with\n   the read\u0027s completion. The spec says to ignore it for LE, where it\n   comes from SMP, and a value outside its 0x07 to 0x10 range is read.\n - eks_capable() for the Encryption Key Schedule feature bit.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d9b633525975773b6ddd512870a53de38b307779",
      "tree": "613e2c5d8c1b8f59b710d2fcf955917f51501b5a",
      "parents": [
        "6833c8b542def06b9d0398063b3a4ecb96f26eb7"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Jan 07 14:44:25 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:19:34 2026 -0500"
      },
      "message": "Bluetooth: ISO: Add extended QoS with the HDT rates\n\nAdd struct bt_iso_qos_ext, an extensible version of struct bt_iso_qos,\nso new QoS fields can be added without defining a new socket option or\nstruct each time. It starts with two fields:\n\n - version tells which fields are valid, so later versions can add\n   fields while applications built for an earlier version keep working.\n - type tells which member of the union is in use, unicast or\n   broadcast. The QoS is usually set before bind() or connect(), when\n   the socket can\u0027t tell which one it was given, so without type the\n   two could only grow together. With it, each can be extended on its\n   own by adding fields at its end, which is also why the union is the\n   last member.\n\nBT_ISO_QOS_ANY leaves the type to connect() or listen(), which set it.\nThat works for version 1 since its unicast fields are a prefix of the\nbroadcast ones, and is what struct bt_iso_qos uses. A type that doesn\u0027t\nmatch how the socket is used makes connect() or listen() fail with\n-EINVAL, or setsockopt() on a socket that already has a connection,\nsuch as with deferred setup or a PA sync.\n\nVersion 1 adds the rates of each direction, BT_ISO_HDT_RATE_*, so\nuserspace can select the HDT rates of a CIS or BIS along with\nBT_ISO_PHY_HDT; 0 selects every rate the controller supports.\n\nBT_ISO_QOS accepts either struct: the length of struct bt_iso_qos\nselects it, as before, and any other length must carry struct\nbt_iso_qos_ext of a known version and type. The struct is copied field\nby field, so its padding is zeroed. Reading BT_ISO_QOS with a buffer\nshorter than struct bt_iso_qos_ext returns struct bt_iso_qos, so\nexisting userspace is not affected; otherwise the version and type in\nuse are reported, including for connections set up by the controller.\n\nThe ISO sockets keep the extended form internally, so the rates are\npassed to LE Set CIG Parameters v2 and LE Create BIG v2, and reported\nback from LE CIS Established v3 and LE Create BIG Complete v2.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "6833c8b542def06b9d0398063b3a4ecb96f26eb7",
      "tree": "281fc263a9d238bfe6654a79079aaac56687eb57",
      "parents": [
        "9c3e0d32c0ff8043cf84487c737764e49dac1d70"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Jan 05 16:24:47 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:19:25 2026 -0500"
      },
      "message": "Bluetooth: Add initial support for HDT PHY\n\nAdd support for the LE HDT PHY introduced by High Data Throughput (HDT)\nin Bluetooth 7.0:\n\n - The HDT feature bits (Link Layer feature bits 76-83) and the\n   le_feature() helper to access the FeatureSet pages above page 0,\n   along with hdt_capable() and the per-rate capability checks.\n - BT_PHY_HDT_* bits for the HDT2, HDT3, HDT4, HDT6 and HDT7.5 rates in\n   each direction, so userspace can select them with BT_PHY, which map\n   to the LE HDT PHY and the rate bits of PHY_Options in LE Set PHY.\n - LE Read Maximum Data Length v2 and LE Read/Write Suggested Default\n   Data Length v2, used instead of their v1 counterparts on HDT capable\n   controllers so the default data length is set for each PHY. The\n   values given to LE Write Suggested Default Data Length are clamped to\n   the maximum the specification allows.\n - LE Set CIG Parameters v2, LE CIS Established v3, LE Create BIG v2 and\n   LE Create BIG Complete v2, which carry the HDT rates, MIC length and\n   packet format of a CIS or BIS. The CIS and BIS default to all the HDT\n   rates the controller supports when the HDT PHY is selected.\n - MGMT_SETTING_HDT to report HDT support to userspace.\n\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "9c3e0d32c0ff8043cf84487c737764e49dac1d70",
      "tree": "3ae514caca6b84121a20f253d993becbbc9a5a2d",
      "parents": [
        "50932a1567d614cd7f9b8be686e2f892c8c1188a",
        "1752a2c40059f845123946e01646b8a1798eeea4"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:13:23 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 15:13:23 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "1752a2c40059f845123946e01646b8a1798eeea4",
      "tree": "52b152e1475ef09f2547a28e5e95418206ae8d9b",
      "parents": [
        "fd038b82c71baa8dfb80e1781e53c0dbbda84e70"
      ],
      "author": {
        "name": "Chandrashekar Devegowda",
        "email": "chandrashekar.devegowda@intel.com",
        "time": "Wed Nov 11 19:48:22 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:52:30 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Fix SCP DBGC base address\n\nBTINTEL_PCIE_DBGC_BASE_ADDR_SCP was entered as 0xf0d5d500 by mistake\nwhen the define was added. The base of the SCP debug controller is\n0xf0d5d400, as documented in the Intel SCP SAS document, so the value\nis one register row too high. The status and wrap-around registers\nderived from it at offsets 0x1C and 0x2C therefore point at the wrong\naddresses, and the debug buffer status and wrap-around state read while\ndumping SCP debug traces are incorrect.\n\nUse 0xf0d5d400 so that the derived offsets land on the intended\nregisters.\n\nTested on an SCP platform by triggering a firmware exception and\ncollecting the resulting devcoredump. With the corrected base address,\nthe debug buffer status and wrap-around registers read back valid\nvalues and the DRAM monitor buffers in the dump are decoded correctly;\nwith the old address they are read from the wrong registers.\n\nFixes: e43b33bf8d67 (\"Bluetooth: btintel_pcie: Load IOSF debug regs by controller variant\")\nSigned-off-by: Chandrashekar Devegowda \u003cchandrashekar.devegowda@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "fd038b82c71baa8dfb80e1781e53c0dbbda84e70",
      "tree": "85676f03f15f05f80090e032cbc3ff74a7088bdc",
      "parents": [
        "4dce35adafb5d258a58788c0282a0dd43e7ccd73"
      ],
      "author": {
        "name": "Chun-Yi Lee",
        "email": "jlee@suse.com",
        "time": "Wed Nov 11 17:45:18 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:52:22 2026 -0500"
      },
      "message": "Bluetooth: SMP: Fail if local and remote public key X coords match\n\nThe commit 6d19628f539f (\"Bluetooth: SMP: Fail if remote and local public keys are identical\")\n patch be introduced since v5.13. Looks this patch can handle the\nCVE-2021-37577 issue. However, it only checks if the full 64-byte\npublic key (X and Y coordinates) is identical, which is insufficient.\n\nIn CVE-2021-37577:\nBluetooth LE and BR/EDR Secure Connections pairing and Secure Simple\nPairing using the Passkey entry protocol in Bluetooth Core\nSpecifications 2.1 through 5.3 may permit an unauthenticated\nman-in-the-middle attacker to identify the Passkey used during pairing\nby reflection of a crafted public key with the same X coordinate as the\noffered public key and by reflection of the authentication evidence of\nthe initiating device, potentially permitting this attacker to complete\nauthenticated pairing with the responding device using the correct\nPasskey for the pairing session. This is a related issue to\nCVE-2020-26558.\n\nFurthermore, according to the Bluetooth Core Specification, the remote\nand local public keys should not have the same X coordinate:\n\nBluetooth Core Specification Version: v5.4\n(7.1 PHASE 1: PUBLIC KEY EXCHANGE)\n\"If the two public keys have the same X coordinate and neither is the\ndebug key (see [Vol 4] Part E, Section 7.6.4), each device should fail\nthe pairing process.\"\n\nBluetooth Core Specification Version: v6.0\n(7.1 Phase 1: Public key exchange)\n\"If the two public keys have the same X coordinate and neither is the\ndebug key (see [Vol 4] Part E, Section 7.6.4), each device shall fail\nthe pairing process.\"\n\nTo ensure both initiator and responder roles strictly enforce this rule:\n- In smp_cmd_public_key(), restrict the check for the initiator to\n  compare only the 32-byte X coordinate of the public keys rather than\n  the full 64 bytes.\n- In sc_send_public_key(), add the corresponding check for the responder\n  to verify that the 32-byte X coordinate of remote_pk does not match\n  local_pk before transmitting its own public key.\n\nThis makes the validation compliant with the specification and mitigates\nCVE-2021-37577 across both pairing roles.\n\nFixes: 6d19628f539f (\"Bluetooth: SMP: Fail if remote and local public keys are identical\")\nLink: https://nvd.nist.gov/vuln/detail/cve-2021-37577\nSigned-off-by: Chun-Yi Lee \u003cjlee@suse.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "4dce35adafb5d258a58788c0282a0dd43e7ccd73",
      "tree": "c26eafb933150021ff5357823e569039de1b0674",
      "parents": [
        "8b1eff978e66efb5ed66b79591851203d05ab303"
      ],
      "author": {
        "name": "Weihong Guan",
        "email": "weihong.guan@gmail.com",
        "time": "Wed Nov 11 16:51:33 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:52:14 2026 -0500"
      },
      "message": "Bluetooth: hci_event: Find the owner of a terminated adv set\n\nhci_le_ext_adv_term_evt() looks the instance up by the event\u0027s handle,\nbut when the controller supports a single advertising set,\nhci_add_adv_instance() gives instance 1 handle 0x00, which is also the\nhandle of Global Advertising. For instance 1 the event then finds no\ninstance, and:\n\n - a connection from it gets hdev-\u003erandom_addr as its responder\n   address, rather than the instance\u0027s random address, which SMP then\n   checks against;\n - the connection stores handle 0x00 in conn-\u003eadv_instance, which is\n   later restored as hdev-\u003ecur_adv_instance, so after the disconnection\n   instance 0 is re-enabled rather than instance 1;\n - when the set terminates with an error, instance 0 is removed rather\n   than instance 1, so instance 1 stays with no\n   MGMT_EV_ADVERTISING_REMOVED.\n\nFind the instance owning the set: for handle 0x00 the instance enabled\non it, as hci_le_ext_adv_set_enabled() tracks, and use its instance\nnumber and random address. On an error, free the instance found with\nhci_free_adv_instance() rather than looking it up again. Global\nAdvertising, and any other handle, are handled as before.\n\nFixes: e77f43d531af (\"Bluetooth: hci_core: Fix not handling hdev-\u003ele_num_of_adv_sets\u003d1\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Weihong Guan \u003cweihong.guan@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "8b1eff978e66efb5ed66b79591851203d05ab303",
      "tree": "e1ddd0a73426ddcfe088e61f5198a7ebcc21cf68",
      "parents": [
        "e7e877bf658acd15fc7dda1bff3e66d0fa69a061"
      ],
      "author": {
        "name": "Weihong Guan",
        "email": "weihong.guan@gmail.com",
        "time": "Wed Nov 11 16:51:32 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:52:07 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Add hci_free_adv_instance()\n\nhci_remove_adv_instance() looks the instance up by its number and then\nfrees it. A caller that already holds the instance, found some other\nway, has to look it up again by number to remove it.\n\nSplit the freeing into hci_free_adv_instance(), which takes the\ninstance itself, and have hci_remove_adv_instance() call it after the\nlookup. No functional change.\n\nSuggested-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Weihong Guan \u003cweihong.guan@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "e7e877bf658acd15fc7dda1bff3e66d0fa69a061",
      "tree": "4c2e7ddd960d11045422519a61b6cd196fdf5674",
      "parents": [
        "daf949c968d485badd6c1fc5b6965ea8175e7dda"
      ],
      "author": {
        "name": "Weihong Guan",
        "email": "weihong.guan@gmail.com",
        "time": "Wed Nov 11 16:51:31 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:51:59 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Remove an advertising set by its handle\n\nWhen the controller supports a single advertising set,\nhci_add_adv_instance() gives instance 1 handle 0x00, but\nhci_remove_ext_adv_instance_sync() sends the instance number as the\nhandle of LE Remove Advertising Set, so removing instance 1 fails:\n\n  $ btmgmt rm-adv 1\n  Remove Advertising failed with status 0x03 (Failed)\n\n  \u003c HCI Command: LE Remove Advertising Set  Handle: 1\n  \u003e HCI Event: Command Complete\n        Status: Unknown Advertising Identifier (0x42)\n\nSend the instance\u0027s handle, looked up with hdev-\u003elock held. Two more\nthings follow from the instance and the handle differing:\n\n - hci_cc_le_remove_adv_set() removes the instance numbered as the\n   handle it sent, which for handle 0x00 is instance 0, so instance 1\n   would stay in hdev-\u003eadv_instances with its RPA timer running, and no\n   MGMT_EV_ADVERTISING_REMOVED. The completion can\u0027t tell instance 1\n   from instance 0, which the MGMT Set Advertising path removes on the\n   same handle, so remove instance 1 in\n   hci_remove_ext_adv_instance_sync() once the command succeeds.\n\n - While Global Advertising is on, it owns handle 0x00\n   (adv_overridden_by_global()), and the set may be enabled for it, so\n   the controller would refuse to remove it, with Command Disallowed.\n   Remove only the instance then, leaving the set to Global\n   Advertising.\n\nFixes: e77f43d531af (\"Bluetooth: hci_core: Fix not handling hdev-\u003ele_num_of_adv_sets\u003d1\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Weihong Guan \u003cweihong.guan@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "daf949c968d485badd6c1fc5b6965ea8175e7dda",
      "tree": "6c78ba611a470c3aa243e298e074868357ee3cc8",
      "parents": [
        "df33621e70363df4d6963ad5ff19a3ae740c7703"
      ],
      "author": {
        "name": "Weihong Guan",
        "email": "weihong.guan@gmail.com",
        "time": "Wed Nov 11 16:51:30 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:51:52 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Set random address on the set\u0027s handle\n\nWhen the controller supports a single advertising set,\nhci_add_adv_instance() gives instance 1 handle 0x00, and the parameters,\ndata and enable commands for an instance use adv-\u003ehandle. LE Set\nAdvertising Set Random Address, from hci_set_adv_set_random_addr_sync(),\nstill sends the instance number, 0x01, a set the controller doesn\u0027t\nhave, so an instance using a random address, such as a non-connectable\none, never starts:\n\n  $ btmgmt add-adv -d 0A09434841445654455354 1\n  Add Advertising failed with status 0x0d (Invalid Parameters)\n\n  \u003c HCI Command: LE Set Extended Advertising Parameters  Handle: 0x00\n  \u003c HCI Command: LE Set Extended Advertising Data        Handle: 0x00\n  \u003c HCI Command: LE Set Advertising Set Random Address\n        Advertising handle: 0x01\n\nSend the instance\u0027s handle, looked up with hdev-\u003elock held.\n\nhci_cc_le_set_adv_set_random_addr() records the address in the instance\nnumbered as the handle and leaves handle 0x00 alone, as that handle\u0027s\naddress is hdev-\u003erandom_addr for instance 0. Instance 1\u0027s address on\nhandle 0x00 would then go unrecorded, and its RPA timer never start, so\nrecord it in hci_set_adv_set_random_addr_sync() once the command\nsucceeds, as the completion does for the other handles.\n\nFixes: e77f43d531af (\"Bluetooth: hci_core: Fix not handling hdev-\u003ele_num_of_adv_sets\u003d1\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Weihong Guan \u003cweihong.guan@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "50932a1567d614cd7f9b8be686e2f892c8c1188a",
      "tree": "93d12beddccf513bfd741308169fd9e6a4ba871c",
      "parents": [
        "89ab6c52494c88e3c95252b4d7a017b406248e38"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Wed Nov 11 18:53:32 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:34:34 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add yoyo configuration for Hci cmd Tlvs\n\nAdd parsing of the YoYo HCI command TLV so that HCI commands can\nbe sent to the controller through the external TLV file. Each\nTLV is validated for domain, version, timepoint and command\nlength. Only the ALIVE timepoint is supported, and periodic\ncommands are skipped with a warning. Valid commands are stored\nin the HCI command list of the YoYo context and are freed when\nthe YoYo context is cleaned up.\n\nA mutex in the YoYo context serializes HCI command dispatch\nagainst btintel_pcie_yoyo_cleanup(). It is held across each\n__hci_cmd_sync() call and across the cleanup on the probe error\npath and in btintel_pcie_remove(), so the command list is not\nfreed while a command is being sent. The other YoYo lists are\nonly used during setup and are freed after the HCI device is\nreleased.\n\nThe stored commands are sent in order at the ALIVE timepoint at\nthe end of setup, once the operational firmware has booted and\nthe alive interrupt and bootup event have been received. This\nmatches the Windows driver: the commands are sent before the HCI\ninit sequence resets the controller, and they are not sent again\nafter that reset. As setup runs only once per HCI registration,\nthe commands are also not repeated on later power-ons.\n\nA command is skipped if its parameter length does not match the\nTLV payload. Sending stops if the device is halted, in recovery,\nin D3 or unregistering, or if a command fails because of a\ntimeout, a lost device or an interrupted wait. Other command\nfailures are logged as warnings and do not stop normal Bluetooth\nbring-up.\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "89ab6c52494c88e3c95252b4d7a017b406248e38",
      "tree": "7a84f22fb1552ff7db5e39ae5632cb2f340f9474",
      "parents": [
        "68e0925f16c028ad1849f4ebce9a8d8a2da5d514"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Wed Nov 11 18:53:31 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:34:26 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add yoyo configuration for debug region\n\nAdd parsing of the YoYo DEBUG_REGION TLV. A region TLV defines\na named, addressable debug region and registers it by region ID;\nit does not trigger a dump by itself. A later trigger TLV\nselects regions through a 64-bit region ID mask, and the dump\nfor each selected region is dispatched based on its stored\nregion type.\n\nA region TLV shorter than its fixed layout means the YoYo file\nis corrupted, so parsing fails and YoYo is disabled. Otherwise,\neach region TLV is validated for domain, version, region ID and\nregion type. Device memory, peripheral MAC and CSR regions must\ncarry an address list, DRAM buffer regions a valid allocation\nID, and device memory, internal buffer and special device memory\nregions a non-zero, dword-aligned size. An invalid entry is\nskipped with a warning. Other type-specific parameters are\nstored as received and checked when the region is dumped. Upper\nbounds on region size and address count are left to the dump\npath, which already caps reads at BTINTEL_PCIE_REGION_MAX_SIZE.\nValid regions are stored in the region list of the YoYo context,\nreplacing any existing entry with the same region ID, and are\nfreed when the YoYo context is cleaned up.\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "68e0925f16c028ad1849f4ebce9a8d8a2da5d514",
      "tree": "114ec00b32e34b350e6e018cfb98d5fab761b4ff",
      "parents": [
        "afafcb373fd0e3256b53e3e4f3a43cb5e1875ada"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Wed Nov 11 18:53:30 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:34:19 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add yoyo support for config set TLV\n\nAdd parsing of the YoYo CONFIG_SET TLV so that debug register\nconfiguration can be supplied through the external TLV file.\nEach CONFIG_SET TLV is validated, and its address/value pairs\nare stored in the config set list of the YoYo context.\n\nAt the configured timepoint, the stored pairs are written to\nthe target memory region, with or without target access\ndepending on the region type. Write failures are logged\nand do not stop normal Bluetooth bring-up.\n\nPeripheral MAC and device memory pairs are written through the\nindirect target access registers: the address is written to\nPRPH_DEV_ADDR_REG (0x440), which is shared by reads and writes,\nand the value to PRPH_DEV_WR_REG (0x454), under MAC access. No\nreadback is done, as reading some peripheral registers has side\neffects.\n\nbtintel_pcie_yoyo_cleanup() now frees the config set list,\nso in btintel_pcie_remove() it is moved after\nbtintel_pcie_release_hdev(); the list must stay valid until\nthe HCI device is gone. It also clears ctx-\u003ehdev, and\nbtintel_pcie_yoyo_load_and_parse() now calls it itself when\nparsing fails or a mandatory TLV is missing, so a rejected\nfile leaves no partial state.\n\nbtintel_pcie_yoyo_load_and_parse() also rejects a NULL\ndevice, and its parse failures are reported with BT_WARN\ninstead of BT_ERR, since YoYo is optional and the driver\nfalls back to the legacy DBGC defaults. The existing\nDEBUG_INFO and buffer allocation parser messages are\nreworded, and the PCI BDF is added to the YoYo status\nmessages to identify the controller.\n\nThe mandatory TLV check for the buffer allocation TLV is moved\nfrom btintel_pcie_yoyo_parse_tlv_buffer() to\nbtintel_pcie_yoyo_load_and_parse(), so that both mandatory TLVs\nare checked in one place.\n\nExisting defines and enum entries in btintel_pcie_debug.h\nare realigned; these are whitespace-only changes.\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "afafcb373fd0e3256b53e3e4f3a43cb5e1875ada",
      "tree": "b1f96f62d5dd7b922444c614c612e343a0df914f",
      "parents": [
        "05ad7f2dee07bce6fa36c5123075ada932ef0922"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linusw@kernel.org",
        "time": "Tue Nov 10 11:45:27 2026 +0100"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:34:11 2026 -0500"
      },
      "message": "Bluetooth: hci_bcm: Prefer a valid platform BD address\n\nSamsung phones with BCM4334B0 store the assigned Bluetooth address in\npersistent EFS storage. The bootloader can supply that address through\nlocal-bd-address even when the controller reports a non-default address.\n\nSigned-off-by: Linus Walleij \u003clinusw@kernel.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "05ad7f2dee07bce6fa36c5123075ada932ef0922",
      "tree": "e771347e4fad785499aa3eb9f02956b27447101b",
      "parents": [
        "df348a0d065ca989c6391f4bb122d2203f31feb6"
      ],
      "author": {
        "name": "Linus Walleij",
        "email": "linusw@kernel.org",
        "time": "Tue Nov 10 11:45:26 2026 +0100"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:34:04 2026 -0500"
      },
      "message": "dt-bindings: bluetooth: brcm: Allow a platform BD address\n\nThe bootloader can recover the device-specific Bluetooth address from\npersistent storage on Samsung phones using BCM4334B0, and pass it in\nthe Bluetooth node. The Broadcom UART binding currently rejects the\nstandard local-bd-address property.\n\nReference the common Bluetooth controller binding to accept the optional\nsix-byte, little-endian address, and illustrate it in the example.\n\nSigned-off-by: Linus Walleij \u003clinusw@kernel.org\u003e\nAcked-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "df348a0d065ca989c6391f4bb122d2203f31feb6",
      "tree": "ea8c48be60f616b92f02d3a1337e0d76c9a4e2e6",
      "parents": [
        "c21f8cff7503fa699722e8518a09f5e5d7d782d0"
      ],
      "author": {
        "name": "Frédéric Mahé",
        "email": "frederic.mahe@cirad.fr",
        "time": "Wed Nov 11 10:45:57 2026 +0100"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:33:56 2026 -0500"
      },
      "message": "riscv: dts: spacemit: enable Bluetooth on BPI-F3\n\nThe BPI-F3 has an RTL8852BS module whose Bluetooth part is on UART2,\nwith hardware flow control. GPIO 63 powers Bluetooth on and GPIO 64\nis the device wake line.\n\nThe firmware config switches the UART to 1.5 Mbaud, so take the UART2\nclock from slow_uart2, set to 48 MHz.\n\nTested with a laptop: scan, pairing, and l2ping in both directions,\nincluding incoming connections while the UART is runtime suspended.\nAn 8-hour soak (an HCI command every 20 s) showed no errors.\n\nThis patch was prepared with the help of an AI assistant (Claude),\nwhich also ran the tests.\n\nSigned-off-by: Frédéric Mahé \u003cfrederic.mahe@cirad.fr\u003e\nReviewed-by: Troy Mitchell \u003ctroy.mitchell@linux.spacemit.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "c21f8cff7503fa699722e8518a09f5e5d7d782d0",
      "tree": "8fc2cd58b0dfb7f77932aef86f459f1173684c39",
      "parents": [
        "def8a484b8883cd21d44a2a45702dcced9bf2627"
      ],
      "author": {
        "name": "Frédéric Mahé",
        "email": "frederic.mahe@cirad.fr",
        "time": "Wed Nov 11 10:45:56 2026 +0100"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 11 14:33:49 2026 -0500"
      },
      "message": "dt-bindings: net: bluetooth: realtek: Add RTL8852BS\n\nThe RTL8852BS is a Wi-Fi 6 + Bluetooth 5.2 chip with Wi-Fi on SDIO\nand Bluetooth on UART (H5). Its Bluetooth part works with the\nRTL8822CS driver data, so use realtek,rtl8822cs-bt as fallback.\n\nThis patch was prepared with the help of an AI assistant (Claude),\nwhich also ran the tests.\n\nSigned-off-by: Frédéric Mahé \u003cfrederic.mahe@cirad.fr\u003e\nAcked-by: Conor Dooley \u003cconor.dooley@microchip.com\u003e\nReviewed-by: Alistair Francis \u003calistair@alistair23.me\u003e\nReviewed-by: Troy Mitchell \u003ctroy.mitchell@linux.spacemit.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "def8a484b8883cd21d44a2a45702dcced9bf2627",
      "tree": "0f56d225ada5883029622d13c73f6428f0987dd7",
      "parents": [
        "983f3fcb1282824a945d5090210c4d19cbdcb53b",
        "df33621e70363df4d6963ad5ff19a3ae740c7703"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 11:01:03 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 11:01:03 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "df33621e70363df4d6963ad5ff19a3ae740c7703",
      "tree": "98a78e18310cc587b5e2c1b200905768ac5bbf73",
      "parents": [
        "f8ba3e2e82f06cbd469d6ee249fbf86c138247c9"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Sun Oct 25 00:35:21 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:51:20 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Protect the receive reject-list lookup\n\nReject-list entries must remain alive throughout a lookup. Management\nupdates the list under hdev-\u003elock, but l2cap_recv_frame() traverses it\nunder conn-\u003elock after l2cap_recv_acldata() has released hdev-\u003elock.\n\nAn established LE connection can still receive ACL data after its peer\nhas been added to the reject list. If a management socket unblocks that\npeer during the receive-side lookup, the following ordering is possible:\n\n  HCI receive                        Management\n  l2cap_recv_acldata()\n    release hdev-\u003elock\n    acquire conn-\u003elock\n  l2cap_recv_frame()\n    lookup selects entry\n                                     unblock_device()\n                                       acquire hdev-\u003elock\n                                       hci_bdaddr_list_del()\n                                         unlink and kfree(entry)\n    read entry-\u003ebdaddr_type\n\nManagement does not take conn-\u003elock, so deletion can free the selected\nentry before the lookup reads its fields. This causes a use-after-free\nread in hci_bdaddr_list_lookup().\n\nCompute the reject decision under the existing device lock in\nl2cap_recv_acldata() and pass only the boolean to l2cap_recv_frame().\nFor pending receive data, take the snapshot in l2cap_conn_ready() and\nl2cap_security_cfm(), which already hold hdev-\u003elock. Publish it under\nconn-\u003elock before queuing the worker on the existing device workqueue:\n\n  HCI callback                       Pending RX worker\n    hold hdev-\u003elock\n    acquire conn-\u003elock\n    lookup reject list\n    save boolean; queue work\n    release conn-\u003elock\n                                       acquire conn-\u003elock\n                                       consume boolean\n                                       drain pending frames\n\nThe snapshot belongs to the scheduled batch. A subsequent scheduling\ncallback refreshes it under both locks, including when queue_work()\ncoalesces with already pending work. No reject-list pointer survives the\nlookup, and the worker reads the boolean under conn-\u003elock.\n\nTaking the device lock in the worker would deadlock against\nl2cap_conn_del(), which holds it while cancelling the work synchronously.\nA failed trylock followed by immediate self-requeue would instead keep\nretrying without a delay and extend a concurrent workqueue drain. Keep\nthe lookup in the scheduling callbacks so the worker needs neither the\ndevice lock nor a retry. Skip scheduling when pending_rx is empty.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in hci_bdaddr_list_lookup+0x145/0x160\n    Read of size 1 at addr ffff88810cba64d6 by task kworker/u17:0/493\n\n    Workqueue: hci0 hci_rx_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_bdaddr_list_lookup+0x145/0x160\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_bdaddr_list_lookup+0x145/0x160\n     kasan_report+0xe0/0x110\n     ? hci_bdaddr_list_lookup+0x145/0x160\n     hci_bdaddr_list_lookup+0x145/0x160\n     l2cap_recv_frame+0x865/0x8830\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_lock+0x182c/0x2590\n     ? __pfx_l2cap_recv_frame+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? find_held_lock+0x2b/0x80\n     ? l2cap_recv_acldata+0x1eb/0x10e0\n     ? __pfx___mutex_lock+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_unlock_slowpath+0x147/0x920\n     ? __pfx_l2cap_conn_hold_unless_zero+0x10/0x10\n     ? __pfx_hci_conn_enter_active_mode+0x10/0x10\n     ? l2cap_recv_acldata+0x13d/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     l2cap_recv_acldata+0xe9f/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     hci_rx_work+0x5a6/0xf00\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 604:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_bdaddr_list_add+0xdf/0x2c0\n     block_device+0x112/0x260\n     hci_sock_sendmsg+0x128b/0x22e0\n     sock_write_iter+0x4c0/0x550\n     do_iter_readv_writev+0x59c/0x860\n     vfs_writev+0x30e/0xc10\n     do_writev+0x241/0x2f0\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n    Freed by task 606:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     kfree+0x307/0x580\n     hci_bdaddr_list_del+0x1a9/0x2a0\n     unblock_device+0x112/0x260\n     hci_sock_sendmsg+0x128b/0x22e0\n     sock_write_iter+0x4c0/0x550\n     do_iter_readv_writev+0x59c/0x860\n     vfs_writev+0x30e/0xc10\n     do_writev+0x241/0x2f0\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n    The buggy address belongs to the object at ffff88810cba64c0\n                                                                which\n                                belongs to the cache kmalloc-32 of size 32\n    The buggy address is located 22 bytes inside of\n                                                                freed\n                                32-byte region [ffff88810cba64c0,\n                                ffff88810cba64e0)\n\n    The buggy address belongs to the physical page:\n        page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0\n    pfn:0x10cba6\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n        raw: 0200000000000000 ffff888100042780 dead000000000100\n    dead000000000122\n        raw: 0000000000000000 0000000000400040 00000000f5000000\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88810cba6380: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n     ffff88810cba6400: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n    \u003effff88810cba6480: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n                                                     ^\n     ffff88810cba6500: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n     ffff88810cba6580: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: cc8dba2bc302 (\"Bluetooth: Block ATT connection on LE when device is blocked\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f8ba3e2e82f06cbd469d6ee249fbf86c138247c9",
      "tree": "2b237507177b604aa258c908eca299546faa7952",
      "parents": [
        "58d8a0955065fb00824865dca5b573a1becbb1ca"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Sat Oct 24 23:28:23 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:51:13 2026 -0500"
      },
      "message": "Bluetooth: vhci: Serialize packet reception with device creation\n\nThe hci_dev passed to hci_recv_frame() must stay alive until the receive\noperation finishes. __vhci_create_device() stores data-\u003ehdev before\nhci_register_dev() and frees the device if registration fails.\nvhci_get_user() checks and uses that pointer without taking the\nopen_mutex held by the creator or a device reference.\n\nAn incoming packet write can overlap the delayed default-create work\nscheduled by vhci_open(). If registration fails before acquiring the\nregistration reference, the following order is possible:\n\n  Default-create work                Packet write\n  vhci_create_device()\n    mutex_lock(open_mutex)\n    data-\u003ehdev \u003d hdev\n                                     vhci_get_user()\n                                       load data-\u003ehdev\n    hci_register_dev() fails\n    hci_free_dev(hdev)\n      bt_host_release(): kfree(hdev)\n    data-\u003ehdev \u003d NULL\n    mutex_unlock(open_mutex)\n                                     hci_recv_frame(hdev, skb)\n                                       read hdev-\u003eflags\n\nThe packet retains the pointer before the final put and reads flags\nafter the allocation is freed. The HCI_UP/HCI_INIT test therefore\naccesses freed memory before it can reject the packet.\n\nHold open_mutex from the packet-side pointer check until\nhci_recv_frame() returns. Creation and its error cleanup already hold\nthis mutex, so the writer waits until they finish and cannot retain a\nfailed device allocation. Release the mutex on the missing-device error\npath too.\n\nKASAN report as below:\n\n    BUG: KASAN: use-after-free in hci_recv_frame+0x4e/0x7e0\n    Read of size 8 at addr ffff888107034138 by task python3/500\n\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_recv_frame+0x4e/0x7e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_recv_frame+0x4e/0x7e0\n     kasan_report+0xe0/0x110\n     ? hci_recv_frame+0x4e/0x7e0\n     kasan_check_range+0x105/0x1b0\n     hci_recv_frame+0x4e/0x7e0\n     vhci_write+0x35a/0x4c0\n     vfs_write+0x637/0x1010\n     ? __pfx_vhci_write+0x10/0x10\n     ? __might_fault+0xdd/0x190\n     ? __pfx_vfs_write+0x10/0x10\n     ? __pfx_hrtimer_wakeup+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? common_nsleep_timens+0xa8/0x160\n     ksys_write+0x111/0x200\n     ? __pfx_ksys_write+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? restore_fpregs_from_fpstate+0x55/0x100\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n    The buggy address belongs to the physical page:\n        page: refcount:0 mapcount:0 mapping:0000000000000000\n    index:0xffff888107036a40 pfn:0x107034\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n        raw: 0200000000000000 ffffea00041c0308 ffff8881887bf180\n    0000000000000000\n        raw: ffff888107036a40 0000000000000000 00000000ffffffff\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff888107034000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n     ffff888107034080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n    \u003effff888107034100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n                                            ^\n     ffff888107034180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n     ffff888107034200: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: 23424c0d3169 (\"Bluetooth: Add support creating virtual AMP controllers\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nTested-by: Chad Aldreda \u003cca@modelmiser.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "58d8a0955065fb00824865dca5b573a1becbb1ca",
      "tree": "934424489a0299c282281f5905c836729035274e",
      "parents": [
        "d9a1bd14caf5d235499319f7aee9e641c12d90a9"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Sun Oct 25 00:15:17 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:51:05 2026 -0500"
      },
      "message": "Bluetooth: vhci: Flush suspend work after removing debugfs\n\nThe VHCI controller must remain alive until suspend_work finishes.\nvhci_release() flushes the work before removing the force_suspend\ndebugfs entry, so an active writer can queue work after that flush.\n\nA force_suspend write changing the suspend state can overlap the last\nclose of /dev/vhci as follows:\n\n    /dev/vhci close          Debugfs writer        Suspend worker\n    ---------------          --------------        --------------\n    vhci_release()           force_suspend_write()\n      flush_work() returns     [not queued yet]\n                               schedule_work() --\u003e\n                                                   hci_suspend_dev()\n                                                     check powered\n                                                     check !HCI_UNREGISTER\n                                                     hci_suspend_sync()\n                                                     unlock(req_lock)\n      vhci_debugfs_remove()\n        wait for writer\n      hci_unregister_dev()\n      hci_free_dev()\n        drop last reference\n        free hdev\n                                                   hci_clear_wake_reason()\n                                                     lock freed mutex\n                                                     use-after-free\n\nThe controller locks serialize state access but do not retain the\nallocation. Unregister drains HCI-owned work, but does not cover VHCI\u0027s\nsuspend_work on the system workqueue.\n\nFlush suspend_work again after removing the debugfs entries and before\nunregistering the controller. Removal waits for active writers and\nprevents new callbacks, so the second flush drains all remaining work\nwhile the controller and driver data are still alive. Retain the initial\nflush to preserve the existing teardown order.\n\nRuntime testing of this change was not performed.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: use-after-free in __mutex_lock+0x1e68/0x2590\n    Read of size 8 at addr ffff8881011b80b0 by task kworker/0:0/9\n\n    Workqueue: events vhci_suspend_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? __mutex_lock+0x1e68/0x2590\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? __mutex_lock+0x1e68/0x2590\n     kasan_report+0xe0/0x110\n     ? __mutex_lock+0x1e68/0x2590\n     __mutex_lock+0x1e68/0x2590\n     ? hci_suspend_dev+0x1ff/0x650\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? mark_held_locks+0x40/0x70\n     ? _raw_spin_unlock_irqrestore+0x44/0x60\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lockdep_hardirqs_on_prepare+0xea/0x1a0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx___mutex_lock+0x10/0x10\n     ? _raw_spin_unlock_irqrestore+0x44/0x60\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_gate_site_armed+0x31/0x1c0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_pmbd_probe_hit_cookie+0x10/0x10\n     ? hci_suspend_dev+0x1ff/0x650\n     hci_suspend_dev+0x1ff/0x650\n     vhci_suspend_work+0xa5/0x190\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    The buggy address belongs to the physical page:\n        page: refcount:0 mapcount:0 mapping:0000000000000000\n    index:0xffff8881011b9040 pfn:0x1011b8\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n        raw: 0200000000000000 ffffea0004073308 ffff88818863f180\n    0000000000000000\n        raw: ffff8881011b9040 0000000000000000 00000000ffffffff\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff8881011b7f80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n     ffff8881011b8000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n    \u003effff8881011b8080: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n                                         ^\n     ffff8881011b8100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n     ffff8881011b8180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: d16e6d19ccc6 (\"Bluetooth: hci_vhci: Fix calling hci_{suspend,resume}_dev\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nTested-by: Chad Aldreda \u003cca@modelmiser.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d9a1bd14caf5d235499319f7aee9e641c12d90a9",
      "tree": "a214e04e606684aa2eba286af37b9ad6d49d317d",
      "parents": [
        "1645edfa8c29e43239cca615cefcb19959d3aa36"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Sat Oct 24 23:27:49 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:50:58 2026 -0500"
      },
      "message": "Bluetooth: hci_conn: Initialize the device before hash insertion\n\nAn hci_conn must have an initialized embedded device before an RCU\nreader can acquire a reference to it. __hci_conn_add() instead adds\nthe connection to conn_hash before hci_conn_init_sysfs() calls\ndevice_initialize(). Holding hdev-\u003elock during creation does not\nexclude hci_disconnect_all_sync(), which looks up the connection and\ncalls hci_conn_get() under RCU without that lock.\n\nWhen a new incoming ACL request overlaps controller poweroff before\nthe connection is registered in sysfs, the separate event and request\nworkqueues can execute this sequence:\n\n1. The event worker holds hdev-\u003elock and publishes a new connection\n   in __hci_conn_add(), before device_initialize().\n2. The request worker finds that connection under RCU, calls\n   hci_conn_get() and leaves its RCU read-side critical section.\n3. The event worker runs hci_conn_init_sysfs(), sets BT_CONNECT in\n   hci_conn_request_evt() and releases hdev-\u003elock.\n4. The request worker calls hci_abort_conn_sync(), which acquires\n   hdev-\u003elock and reaches hci_conn_failed(), hci_conn_del() and\n   hci_conn_del_sysfs() to delete the pending connection.\n5. After abort returns, the request worker calls hci_conn_put().\n\ndevice_initialize() resets the kobject reference count to one,\ndiscarding the walker\u0027s premature get. If no other device references\nexist, deletion of the unregistered device drops that one reference\nand bt_link_release() frees the hci_conn. The walker\u0027s trailing put\nthen accesses the freed kobject, as shown by the KASAN report below.\nThe RCU grace period in hci_conn_hash_del() cannot preserve the walker\nafter it has left its read-side critical section.\n\nInitialize the device before hci_conn_hash_add() publishes the\nconnection. The existing RCU publication then makes the initialized\ndevice visible to readers, so the walker takes a valid reference that\nsurvives deletion until its matching put.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in kobject_put+0x4f3/0x610\n    Read of size 1 at addr ffff88811e6fcd2c by task kworker/u17:0/559\n\n    Workqueue: hci0 hci_cmd_sync_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? kobject_put+0x4f3/0x610\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? kobject_put+0x4f3/0x610\n     kasan_report+0xe0/0x110\n     ? kobject_put+0x4f3/0x610\n     ? hci_disconnect_all_sync.constprop.0+0xd8/0x520\n     kobject_put+0x4f3/0x610\n     ? hci_disconnect_all_sync.constprop.0+0xd8/0x520\n     put_device+0x24/0x30\n     hci_disconnect_all_sync.constprop.0+0x176/0x520\n     ? hci_disconnect_all_sync.constprop.0+0xcd/0x520\n     ? __pfx_hci_disconnect_all_sync.constprop.0+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     hci_set_powered_sync+0x48f/0x680\n     ? __pfx_hci_set_powered_sync+0x10/0x10\n     ? __pfx___mutex_unlock_slowpath+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     set_powered_sync+0xaa/0x150\n     hci_cmd_sync_work+0x1b3/0x450\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 561:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     __hci_conn_add+0x10c/0x1f70\n     hci_conn_add_unset+0x72/0x120\n     hci_conn_request_evt+0xb2b/0xd40\n     hci_event_packet+0x894/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    Freed by task 559:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     kfree+0x307/0x580\n     bt_link_release+0x4a/0xb0\n     device_release+0xd7/0x280\n     kobject_put+0x1ad/0x610\n     put_device+0x24/0x30\n     hci_conn_del_sysfs+0x15d/0x190\n     hci_conn_del+0x684/0x1100\n     hci_abort_conn_sync+0x7d6/0xae0\n     hci_disconnect_all_sync.constprop.0+0x164/0x520\n     hci_set_powered_sync+0x48f/0x680\n     set_powered_sync+0xaa/0x150\n     hci_cmd_sync_work+0x1b3/0x450\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    The buggy address belongs to the object at ffff88811e6fc000\n                                                                which\n                                belongs to the cache kmalloc-8k of size\n                                8192\n    The buggy address is located 3372 bytes inside of\n                                                                freed\n                                8192-byte region [ffff88811e6fc000,\n                                ffff88811e6fe000)\n\n    The buggy address belongs to the physical page:\n        page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0\n    pfn:0x11e6f8\n    head: order:3 mapcount:0 entire_mapcount:0 nr_pages_mapped:0 pincount:0\n    flags: 0x200000000000040(head|node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n        raw: 0200000000000040 ffff888100043180 dead000000000122\n    0000000000000000\n        raw: 0000000000000000 0000000000020002 00000000f5000000\n    0000000000000000\n        head: 0200000000000040 ffff888100043180 dead000000000122\n    0000000000000000\n        head: 0000000000000000 0000000000020002 00000000f5000000\n    0000000000000000\n        head: 0200000000000003 fffffffffffffe01 00000000ffffffff\n    00000000ffffffff\n        head: 0000000000000000 0000000000000000 00000000ffffffff\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88811e6fcc00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n     ffff88811e6fcc80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n    \u003effff88811e6fcd00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n                                      ^\n     ffff88811e6fcd80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n     ffff88811e6fce00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: 94d9ba9f9888 (\"Bluetooth: hci_sync: Fix UAF in hci_disconnect_all_sync\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "1645edfa8c29e43239cca615cefcb19959d3aa36",
      "tree": "6adf00708e945229453aed522cac912b44803d27",
      "parents": [
        "4728474344793dd67956e03a2cb244b71383ef7c"
      ],
      "author": {
        "name": "Joas Antonio dos Santos",
        "email": "joasantonio108@gmail.com",
        "time": "Tue Nov 10 03:26:03 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:41:16 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: validate MPS and MTU in ECRED connection response\n\nl2cap_ecred_conn_rsp() stores the MTU and MPS from the peer without\nchecking them against the minimums required for enhanced credit based\nchannels.  The other LE and ECRED handlers (l2cap_le_connect_req(),\nl2cap_le_connect_rsp(), l2cap_ecred_conn_req(), l2cap_ecred_reconf_req())\nall reject values below the minimum.\n\nWith an MPS below L2CAP_SDULEN_SIZE, the pdu_len computation in\nl2cap_segment_le_sdu() wraps:\n\n\tpdu_len \u003d chan-\u003eremote_mps - L2CAP_SDULEN_SIZE;\n\npdu_len is then clamped to the SDU length, which l2cap_chan_send() has\nalready limited to chan-\u003eomtu, so nothing is over-allocated and there is\nno memory safety issue.  The result is that the whole SDU is sent as a\nsingle PDU, larger than the MPS the peer announced, and a channel is\nestablished with parameters the specification does not allow.\n\nApply the same L2CAP_ECRED_MIN_MTU / L2CAP_ECRED_MIN_MPS checks that\nl2cap_ecred_conn_req() uses and drop the channel when the response\ncarries smaller values.\n\nFound by LLM-assisted manual code review.\n\nFixes: 15f02b910562 (\"Bluetooth: L2CAP: Add initial code for Enhanced Credit Based Mode\")\nSigned-off-by: Joas Antonio dos Santos \u003cjoasantonio108@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "4728474344793dd67956e03a2cb244b71383ef7c",
      "tree": "5ce39a7242947678652b6cf5e1f6a65b67109206",
      "parents": [
        "45e28b01e4d06282d03f08888f09722709d4b552"
      ],
      "author": {
        "name": "Xu Rao",
        "email": "raoxu@uniontech.com",
        "time": "Tue Nov 10 11:07:56 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:41:09 2026 -0500"
      },
      "message": "Bluetooth: MGMT: Fix runtime config status opcode\n\nThe Set Default Runtime Configuration command uses opcode 0x004e,\nbut set_def_runtime_config() reports its invalid-parameter status with\nthe Set Default System Configuration opcode, 0x004c.\n\nA management client that matches Command Status events to its pending\nrequest by opcode therefore cannot associate the response with the\nrequest it sent. Runtime configuration parameters are not implemented,\nso the command still returns MGMT_STATUS_INVALID_PARAMS.\n\nUse MGMT_OP_SET_DEF_RUNTIME_CONFIG for the status event so the response\nidentifies the command that was actually handled.\n\nFixes: aececa645dc7 (\"Bluetooth: mgmt: Add commands for runtime configuration\")\nSigned-off-by: Xu Rao \u003craoxu@uniontech.com\u003e\nCc: stable@vger.kernel.org\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "45e28b01e4d06282d03f08888f09722709d4b552",
      "tree": "5ba2397ddd86deeec5dba5e534bea1772e6bc66a",
      "parents": [
        "a57a255ce204b51327ac4e840a7726b0ab9a1942"
      ],
      "author": {
        "name": "Shuai Zhang",
        "email": "shuai.zhang@oss.qualcomm.com",
        "time": "Tue Nov 10 17:29:29 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:41:02 2026 -0500"
      },
      "message": "Bluetooth: hci_qca: Don\u0027t use the serdev port after a failed reopen\n\nIf serdev_device_open() fails in qca_port_reopen(), qca_regulator_init()\nor the qca_setup() retry path, the port is left closed but\nHCI_UART_PROTO_READY stays set. The error reaches qca_setup(), whose\nretry loop calls serdev_device_close() again, and hci_uart_close() or\nhci_uart_unregister_device() close it once more later. The HCI core\nalso calls hci_uart_flush() from hci_dev_close_sync() before\nhdev-\u003eclose(), which writes to the closed port.\n\nserdev_device_close() and serdev_device_write_flush() have no \"not open\"\ncheck. ttyport_open() clears serport-\u003etty when it fails, so both end up\npassing NULL to the tty layer, and the runtime PM usage count is dropped\nonce too often.\n\nKeep HCI_UART_PROTO_READY in sync with the port state in hci_qca: clear\nit when the port is closed, set it only after a successful open, and\nonly call serdev_device_close() when it was set. hci_uart_open() already\ntreats the flag as \"port is open\" and reopens the port when it is\nclear, so the next power on recovers. Make hci_uart_flush() skip the\nport flush when the flag is clear, as it already does for the proto\nflush.\n\nSigned-off-by: Shuai Zhang \u003cshuai.zhang@oss.qualcomm.com\u003e\nReviewed-by: Bartosz Golaszewski \u003cbartosz.golaszewski@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "a57a255ce204b51327ac4e840a7726b0ab9a1942",
      "tree": "4b7f3b8bafb1c7c00afe24589bd26fc69a1d6eec",
      "parents": [
        "45a25a1bfd267d9e420119a48e5291d7882395df"
      ],
      "author": {
        "name": "Shuai Zhang",
        "email": "shuai.zhang@oss.qualcomm.com",
        "time": "Tue Nov 10 17:29:28 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:40:55 2026 -0500"
      },
      "message": "Bluetooth: hci_qca: Reopen the UART after enabling QCA2066\n\nQCA2066 does not reopen the UART after the controller is enabled, which\ncauses RX/TX out-of-sync errors. The UART has to be reopened once the\ncontroller is powered on.\n\nqca_regulator_init() already enables the controller and then reopens the\nUART, but QCA2066 does not go through it. QCA2066 was added with its own\nSoC type and handled in the default case.\n\nLet QCA2066 go through qca_regulator_init() as well, and handle it in the\nother places that check the SoC type in the same way. This also applies\nthe baudrate switching, flow control, shutdown and probe handling of\nthose chips to QCA2066. btqca.c checks the SoC type in the same way, so\nthe firmware version is also shown in the log.\n\nSigned-off-by: Shuai Zhang \u003cshuai.zhang@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "45a25a1bfd267d9e420119a48e5291d7882395df",
      "tree": "9eda3a8de15f940be36643945f34a56cb3e575f8",
      "parents": [
        "1f2ac56137c51be0601e18a163d817e02a15913f"
      ],
      "author": {
        "name": "Joas Antonio dos Santos",
        "email": "joasantonio108@gmail.com",
        "time": "Tue Nov 10 03:55:41 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Tue Nov 10 10:40:48 2026 -0500"
      },
      "message": "Bluetooth: hci_qca: clear qca_memdump when discarding dump packets\n\nqca_controller_memdump() frees qca_memdump when a memdump packet with a\nnon-zero sequence number arrives while QCA_MEMDUMP_COLLECTION is not\nset, but leaves qca-\u003eqca_memdump pointing at the freed object.\n\nThe next run of the work reads the stale pointer into its local\nvariable, skips the allocation and uses the freed memory.  Another\npacket with a non-zero sequence number frees it a second time, and a\npacket with sequence number 0 writes ram_dump_size, current_seq_no and\nreceived_dump into it.\n\nThe original code cleared the pointer here; the assignment was dropped\nwhen the condition was changed to test QCA_MEMDUMP_COLLECTION.  All\nother places that free the structure clear the pointer.\n\nA controller that sends two memdump events without a leading sequence\nnumber 0 can trigger a use-after-free or double free of a kmalloc\nobject.\n\nFound by LLM-assisted source review.\n\nFixes: 06d3fdfcdf5c (\"Bluetooth: hci_qca: Add qcom devcoredump support\")\nCc: stable@vger.kernel.org\nSigned-off-by: Joas Antonio dos Santos \u003cjoasantonio108@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "983f3fcb1282824a945d5090210c4d19cbdcb53b",
      "tree": "d033bb0af56e007791f707bb057b0aa22abd07a4",
      "parents": [
        "4c684359d8e17be11c7fdace223dd1801bd0f1b1",
        "1f2ac56137c51be0601e18a163d817e02a15913f"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 17:13:44 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 17:13:44 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "1f2ac56137c51be0601e18a163d817e02a15913f",
      "tree": "2523aac814124206ab546af5545f5ad658a80e20",
      "parents": [
        "c1d50a71cdee90a0c68b7a67221d8aae96d14a0c"
      ],
      "author": {
        "name": "Zhao Li",
        "email": "enderaoelyther@gmail.com",
        "time": "Mon Nov 09 21:21:43 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 17:04:21 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Keep recvmsg from resuming a closed channel\n\nReading buffered ERTM data after ACL link loss can clear local busy and\nsend a supervisory frame after l2cap_conn_del() has destroyed the HCI\nchannel, which oopses on a NULL pointer in hci_send_acl(). The socket still\nowns its L2CAP channel, so its lifetime does not protect the underlying HCI\nchannel.\n\nRequire BT_CONNECTED before clearing local busy in recvmsg. The socket lock\nalready held here serializes this check and send with teardown, which\ncloses the socket before the HCI channel is destroyed. Continue to allow\nbuffered data to be read after disconnection.\n\nAI assistance was used.\n\nFixes: 61aa4f5b9f43 (\"Bluetooth: Use the transmit state machine for busy state changes\")\nCc: stable@vger.kernel.org # needs adjustments for 5.15\nSigned-off-by: Zhao Li \u003cenderaoelyther@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "4c684359d8e17be11c7fdace223dd1801bd0f1b1",
      "tree": "8d607008fe4cc3c070a8945e309ca0505ea4e0d4",
      "parents": [
        "ebdfe8561b5496b7eafedccd13a000a7261bc52b",
        "530e411a49f32907094c4d89ce260659781576a2"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 10:49:28 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 10:49:28 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "530e411a49f32907094c4d89ce260659781576a2",
      "tree": "09033e185738d7c057ec44194587d8a2feeb7ceb",
      "parents": [
        "c1d50a71cdee90a0c68b7a67221d8aae96d14a0c"
      ],
      "author": {
        "name": "Hex Lindqvist",
        "email": "hex@freenixos.com",
        "time": "Thu Nov 05 12:19:52 2026 -0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 09 10:24:20 2026 -0500"
      },
      "message": "Bluetooth: qca: Disable SoC debug logging for WCN3990\n\nUnless the host turns it off, the WCN3990 firmware sends debug logs to\nthe host as ACL packets on handle 0x2EDC. hci_qca passes them on as\ndiagnostic packets, which the core copies to the monitor socket and then\nfrees. On a OnePlus 6T (SoC version 0x40010214, ROM version 0x0201) that\nis a packet of about 490 bytes every seven seconds on average, for as\nlong as the controller is up.\n\nThe driver already turns this logging off after the firmware download\nfor WCN3950 and WCN3991. Do the same for WCN3990.\n\nTested on a OnePlus 6T. With the crbtfw21.tlv rampatch from the OnePlus\nfirmware, no diagnostic packets arrive any more. The controller also\naccepts the command with the crbtfw21.tlv from linux-firmware.\n\nAn AI assistant helped find and test this change and drafted this\nmessage.\n\nSigned-off-by: Hex Lindqvist \u003chex@freenixos.com\u003e\nReviewed-by: Bartosz Golaszewski \u003cbartosz.golaszewski@oss.qualcomm.com\u003e\nReviewed-by: Paul Menzel \u003cpmenzel@molgen.mpg.de\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ebdfe8561b5496b7eafedccd13a000a7261bc52b",
      "tree": "7c97278b25bef4ab72d221c216e5c061747e0e2a",
      "parents": [
        "a063a00e6cd9e354aa6d67a154a0527951d7f881",
        "c1d50a71cdee90a0c68b7a67221d8aae96d14a0c"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Fri Nov 06 15:07:17 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Fri Nov 06 15:07:17 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "c1d50a71cdee90a0c68b7a67221d8aae96d14a0c",
      "tree": "77add6d7eca66b55c49974a27529b9c25cfee9d6",
      "parents": [
        "868c886f45f7c10dc888b94c6993352702a84d04"
      ],
      "author": {
        "name": "Kyle Pepper",
        "email": "cochcoder@proton.me",
        "time": "Fri Nov 06 17:24:57 2026 +0000"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Fri Nov 06 13:49:56 2026 -0500"
      },
      "message": "Bluetooth: reject invalid LE supervision timeout relationships\n\nThe LE parameter validator calculates an unsigned maximum latency by\nsubtracting one from a truncated quotient. If the quotient is zero,\nthis wraps and accepts invalid parameters. Exact quotient boundaries\nalso accept equality where the supervision timeout must be greater.\n\nCompare the products directly after checking the field bounds. The\nvalidated interval and latency limits keep the products within int.\nThis enforces the strict timeout relationship without division or\nunsigned subtraction.\n\nSashiko identified the underflow while reviewing the soft interval\npreference RFC. The bug is already present in its unpatched base; keep\nthis common-validator fix independent of that preference policy.\n\nFixes: 8757825b128e (\"Bluetooth: hci_check_conn_params() check proper range\")\nAssisted-by: LLM\nSigned-off-by: Kyle Pepper \u003ccochcoder@proton.me\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "a063a00e6cd9e354aa6d67a154a0527951d7f881",
      "tree": "98e799c115584ec10142282edf5885bcee427bd4",
      "parents": [
        "31333770a46839e8049aabd1eddf49682d72160c",
        "868c886f45f7c10dc888b94c6993352702a84d04"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 05 11:17:47 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 05 11:17:47 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "868c886f45f7c10dc888b94c6993352702a84d04",
      "tree": "81c583664e543a549ce6b563875cec52b112af09",
      "parents": [
        "eeca795cec6d9c6c193c2c1bd0cb26cde44f9fc3"
      ],
      "author": {
        "name": "YuanZhe Liu",
        "email": "25031212351@stu.xidian.edu.cn",
        "time": "Thu Nov 05 13:56:39 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 05 11:04:13 2026 -0500"
      },
      "message": "Bluetooth: btusb: fix use-after-free in force_poll_sync\n\nThe force_poll_sync debugfs file uses the driver\u0027s struct btusb_data as\nits private data. The file is created under hdev-\u003edebugfs and is removed\nonly when the HCI device is released, while btusb_disconnect() frees\nbtusb_data unconditionally. The HCI device can outlive the driver data,\nfor example when an HCI socket still references it, so reading or\nwriting the already opened file then dereferences freed memory:\n\n  BUG: KASAN: slab-use-after-free in force_poll_sync_read+0x129/0x140\n  Read of size 1 at addr ffff88800cfb7038\n  ...\n  Freed by task ...:\n   kfree\n   btusb_disconnect\n\nRemove the debugfs file before the private data is freed.\ndebugfs_remove() waits for callers that are already inside the file\noperations, and any later access fails with -EIO instead of reaching the\ndriver, so the force_poll_sync file can no longer dereference btusb_data\nafter it is gone.\n\nFixes: 800fe5ec302e (\"Bluetooth: btusb: Add support for queuing during polling interval\")\nCc: stable@vger.kernel.org\nCo-developed-by: Bin Yu \u003cbyu@xidian.edu.cn\u003e\nSigned-off-by: Bin Yu \u003cbyu@xidian.edu.cn\u003e\nCo-developed-by: Cheng Wen \u003cwencheng@xidian.edu.cn\u003e\nSigned-off-by: Cheng Wen \u003cwencheng@xidian.edu.cn\u003e\nSigned-off-by: YuanZhe Liu \u003c25031212351@stu.xidian.edu.cn\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "eeca795cec6d9c6c193c2c1bd0cb26cde44f9fc3",
      "tree": "8a403157c7e576a1722d44b0d5c5791ae52435c9",
      "parents": [
        "e00aa1a33f81a5e25b510f569ab9cb9f97eb41b9"
      ],
      "author": {
        "name": "YuanZhe Liu",
        "email": "25031212351@stu.xidian.edu.cn",
        "time": "Thu Nov 05 13:56:45 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Nov 05 11:04:06 2026 -0500"
      },
      "message": "Bluetooth: hci_qca: fix use-after-free in ibs debugfs files\n\nqca_debugfs_init() creates an \"ibs\" directory under hdev-\u003edebugfs and\nstores pointers to fields of struct qca_data in the debugfs files.\nqca_close() frees qca_data without removing that directory, while\nhdev-\u003edebugfs is only removed when the HCI device is released. The HCI\ndevice can outlive the driver data, for example when an HCI socket still\nreferences it, so reading or writing one of the ibs files then\ndereferences freed memory.\n\nStore the directory dentry in struct qca_data and remove the directory\nwith debugfs_remove_recursive() before qca_data is freed.\ndebugfs_remove() waits for callers that are already inside the file\noperations, and any later access fails with -EIO instead of reaching the\ndebugfs helpers. This covers the two writable files as well.\n\nLink: https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261102113654.8724-1-25031212351%40stu.xidian.edu.cn\nFixes: 0ff252c1976d (\"Bluetooth: hciuart: Add support QCA chipset for UART\")\nCc: stable@vger.kernel.org\nSigned-off-by: YuanZhe Liu \u003c25031212351@stu.xidian.edu.cn\u003e\nReviewed-by: Bartosz Golaszewski \u003cbartosz.golaszewski@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "e00aa1a33f81a5e25b510f569ab9cb9f97eb41b9",
      "tree": "d377d41fe1fd0139728e5f9d63a8f87cbb8b7fda",
      "parents": [
        "d97b618b6675516d63d55b8f31ee6cb3b164bd6b"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 17:16:50 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 17:18:53 2026 -0500"
      },
      "message": "Bluetooth: Fix not updating of hdev-\u003ecommands[] after reset\n\nRead Local Supported Commands was only read once during the INIT/SETUP\nflow, but the supported commands bits may change at runtime, for\nexample after a firmware change applied with vendor commands, so update\nhdev-\u003ecommands[] every time the response is received.\n\nFixes: 6a070e6e81ad (\"Bluetooth: Store supported commands only during setup procedure\")\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "31333770a46839e8049aabd1eddf49682d72160c",
      "tree": "27c04c0f88f5703c29575dca3fe1c850c10ee91c",
      "parents": [
        "ed960ec020a7759e6df5639d90182a00adacbecf",
        "d97b618b6675516d63d55b8f31ee6cb3b164bd6b"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 17:05:43 2026 -0500"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 17:05:43 2026 -0500"
      },
      "message": "Merge branch \u0027bluetooth\u0027 into bluetooth-next\n"
    },
    {
      "commit": "d97b618b6675516d63d55b8f31ee6cb3b164bd6b",
      "tree": "34be8d5dcacaca6e52d3b8f34f0bc230c825087f",
      "parents": [
        "15a80cc8263abd50132a05d1b06824de8e28abcb"
      ],
      "author": {
        "name": "Stanislavs Nilovs",
        "email": "valorcool@gmail.com",
        "time": "Tue Nov 03 12:34:14 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 14:48:35 2026 -0500"
      },
      "message": "Bluetooth: qca: Disable SoC debug logging for WCN3950\n\nAdded WCN3950 module to the switch-case to disable SoC debug packets.\n\nFixes: 590deccf4c06 (\"Bluetooth: hci_qca: Disable SoC debug logging for WCN3991\")\nSigned-off-by: Stanislavs Nilovs \u003cvalorcool@gmail.com\u003e\nReviewed-by: Bartosz Golaszewski \u003cbartosz.golaszewski@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "15a80cc8263abd50132a05d1b06824de8e28abcb",
      "tree": "5b1dce7d7cb8eb867d21764f99bdc4aa32a52b2c",
      "parents": [
        "f50b32aa233d4687af2d241ddcb572da969e8989"
      ],
      "author": {
        "name": "Zhao Li",
        "email": "enderaoelyther@gmail.com",
        "time": "Mon Nov 02 20:47:35 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 14:48:23 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Clear request identifiers on incoming LE connections\n\nIncoming LE and ECRED channels retain the peer\u0027s request identifier\nafter an immediate response. The deferred LE response also leaves the\nidentifier set, unlike the deferred ECRED response.\n\nA later ECRED request can reuse that identifier and include an unrelated\nchannel in its shared-response handling. That walk matches on the\nidentifier alone, so an LE channel is selected too. If the old channel is\nclosing, the checks can refuse the new connection. The check at request\nreceipt rejects it with L2CAP_CR_LE_INVALID_PARAMS; the check before a\ndeferred response returns L2CAP_CR_LE_AUTHORIZATION.\n\nStore the identifier only when deferring the response, and clear it\nafter sending the deferred LE response. Keep deferred ECRED identifiers\nuntil the shared response is sent, since a partially accepted group\nstill needs them.\n\nAI assistance was used.\n\nFixes: 27e2d4c8d28b (\"Bluetooth: Add basic LE L2CAP connect request receiving support\")\nFixes: 15f02b910562 (\"Bluetooth: L2CAP: Add initial code for Enhanced Credit Based Mode\")\nSigned-off-by: Zhao Li \u003cenderaoelyther@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f50b32aa233d4687af2d241ddcb572da969e8989",
      "tree": "ef920aa3455e026dd3533c8b016e470fbcfbc151",
      "parents": [
        "3efdadae3a252b14ca1f62b16e31a9aa7c5d30cf"
      ],
      "author": {
        "name": "Zhao Li",
        "email": "enderaoelyther@gmail.com",
        "time": "Mon Nov 02 20:47:34 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 14:48:11 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Only accept LE responses to outstanding requests\n\nThe LE and ECRED response handlers match channels by identifier without\nchecking whether they sent the request. An incoming channel stores the\nidentifier chosen by the peer, so an unsolicited response can bypass\ndeferred setup, delete an established channel, or leave an unaccepted\nsocket and channel allocated after l2cap_chan_del().\n\nExtend the BR/EDR lookup from commit a518b9a9ef6e (\"Bluetooth: L2CAP:\nOnly accept connection responses to outstanding requests\") to LE.\nRequire the matching connect-request flag and add a reconfigure-request\nflag. Check reconfigure identifiers under the channel lock, since\nBT_RCVMTU can replace a request without the connection lock. Match all\nmembers of a rejected ECRED request, which share one identifier.\n\nA reconfigure request can outlive close(). Complete it even in\nBT_DISCONN, and call the close callback after deletion to release an\norphaned socket. Otherwise deletion cancels the timer and removes the\nchannel before the disconnect response or the channel timeout can close\nit.\n\nAI assistance was used.\n\nFixes: f1496dee9cbd (\"Bluetooth: Add initial code for LE L2CAP Connect Request\")\nFixes: 71fb419724fa (\"Bluetooth: Fix handling of L2CAP Command Reject over LE\")\nFixes: 15f02b910562 (\"Bluetooth: L2CAP: Add initial code for Enhanced Credit Based Mode\")\nCc: \u003cstable@vger.kernel.org\u003e # 5.7.x: a518b9a9ef6e: Bluetooth: L2CAP: Only accept connection responses to outstanding requests\nCc: \u003cstable@vger.kernel.org\u003e # 5.7.x\nSigned-off-by: Zhao Li \u003cenderaoelyther@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "3efdadae3a252b14ca1f62b16e31a9aa7c5d30cf",
      "tree": "496066804031ecd1f1d7c1244456b4cb0916d751",
      "parents": [
        "60b10121db602a43ada3dbc39792bbf93d25991b"
      ],
      "author": {
        "name": "Zijun Hu",
        "email": "zijun.hu@oss.qualcomm.com",
        "time": "Mon Nov 02 22:55:20 2026 -0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 14:34:35 2026 -0500"
      },
      "message": "Bluetooth: hci_conn: Fix SCO/eSCO Transport_Unit_Size for HCI data path\n\nCorrect (Input|Output)_Transport_Unit_Size based on Core spec v6.3,\nVol 4, Part E, 7.1.45:\n\n  \"The Host shall set the Input_Transport_Unit_Size and\n   Output_Transport_Unit_Size to be equal. For HCI Host transport\n   the Host shall set them to 0.\"\n\nFixes: b2af264ad3af (\"Bluetooth: Add support for HCI_Enhanced_Setup_Synchronous_Connection command\")\nSigned-off-by: Zijun Hu \u003czijun.hu@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ed960ec020a7759e6df5639d90182a00adacbecf",
      "tree": "dc2965fccbe7ec60e1faca998f352c12d81dae32",
      "parents": [
        "d81a15edf4ab48da586fc882e0388fce4874adef"
      ],
      "author": {
        "name": "Sai Teja Aluvala",
        "email": "aluvala.sai.teja@intel.com",
        "time": "Wed Nov 04 12:16:10 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 10:17:44 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: DBGC flush doorbell and dump rate-limit\n\nDBGC data in SMEM may not be up to date when a dump is collected. Make\nbtintel_pcie_coredump() arm USER_TRIGGERED_DUMP and ring the\nIPC_CONTROL.COLLECT_DUMP_REQ doorbell first, so the firmware flushes\nthe SMEM contents to DRAM and the dump holds valid data. The resulting\nfwTriggerDump interrupt queues the coredump with\nTRIGGER_REASON_USER_TRIGGER and skips the firmware trigger event, as\nthere is none for a host-initiated flush. Firmware-initiated triggers\nemit the diagnostic frame with TRIGGER_REASON_FW_ASSERT, except while a\ndoorbell reply is pending, as both raise the same interrupt.\n\nThe doorbell only concerns Bluetooth DBGC. When traces are routed to\nthe WiFi DBGC there is no host buffer to flush into, so skip the\nrequest. When the core is halted the firmware cannot answer, so queue\nthe dump directly. If the firmware does not answer within 1 second,\ntreat the doorbell as missed and collect the dump directly.\n\nQuiesce the doorbell path before entering D3: mask the firmware trigger\ninterrupt, drop a pending request, and wait for an in-flight timeout or\ndump to finish. Unmask it again on resume or if suspend fails; firmware\ntriggers latched while it was masked are dropped.\n\nAllow one user or firmware triggered dump per second, measured from the\nend of the last dump, and reject concurrent dumps. A rate-limited\nfirmware trigger still emits the diagnostic frame; only the dump is\nskipped.\n\nSigned-off-by: Sai Teja Aluvala \u003caluvala.sai.teja@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d81a15edf4ab48da586fc882e0388fce4874adef",
      "tree": "ac6ee2d7e463de8a7737593ea702b0f4fa4705ca",
      "parents": [
        "ac2656defdd71de8da7a22722c384b6a0e6252a9"
      ],
      "author": {
        "name": "Sai Teja Aluvala",
        "email": "aluvala.sai.teja@intel.com",
        "time": "Wed Nov 04 17:55:08 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 10:17:37 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add fatal error injection test mode\n\nAdd the FATAL_ERR_TESTMODE debug INI option to inject a firmware\nexception for testing. The INI value selects the exception type and the\ninjection context (thread, IRQ or rfkill). Whether an injected\nexception is expected to trigger recovery depends on its type.\n\nThe test mode is disabled when the OPFW API lock is set, unless the\nunlocker firmware was loaded.\n\nWhile HCI is up, the hardware rfkill button only triggers the\ninjection: an assertion injects the exception, a release is ignored,\nand normal rfkill reporting to the HCI stack is disabled. While HCI is\ndown, normal rfkill handling applies.\n\nThe exception is also injected after every successful setup, with the\nrfkill context and without sampling the rfkill state. The injection\nstays pending until HCI is up, and open() reschedules it. After a\nrecovery re-probe it is injected again, until the INI entry is removed.\n\nSigned-off-by: Sai Teja Aluvala \u003caluvala.sai.teja@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ac2656defdd71de8da7a22722c384b6a0e6252a9",
      "tree": "de3696a1e3f548a1b362e0346ae7588973ba4915",
      "parents": [
        "3f425f95ba3923d605f6a8b382e8fcdc59d479db"
      ],
      "author": {
        "name": "Sai Teja Aluvala",
        "email": "aluvala.sai.teja@intel.com",
        "time": "Wed Nov 04 17:55:07 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Nov 04 10:17:30 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Move debug INI parsing to debug file\n\nMove the debug INI parser from btintel_pcie.c to btintel_pcie_debug.c\nso that all debug INI handling lives in one file. Split it into\nbtintel_pcie_read_debug_ini() and btintel_pcie_ini_next() for reuse,\nexport btintel_pcie_load_dbg_path_from_ini(), and update the module\ndescription. An INI file that cannot be read, including an allocation\nfailure, is now logged as unavailable. DBG_PATH, ENABLE_INI and\nLOG_MASK behave as before.\n\nSigned-off-by: Sai Teja Aluvala \u003caluvala.sai.teja@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "3f425f95ba3923d605f6a8b382e8fcdc59d479db",
      "tree": "de37a25140798e789e967dcda4a15309af3e42f8",
      "parents": [
        "338150593939d88a8f62c6e0ffb1967f05197eae"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:44 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Gate mailbox logging behind LOG_MASK\n\nMove the informational mailbox messages (GP1 register contents, target\naccess mailbox, interrupt and TLV parse timestamps, TLV hex dump and\nparsed dump region summary) behind BTINTEL_PCIE_LOG_MBOX (bit 6) so\nthey no longer flood the log by default. Mailbox errors and warnings\nremain unconditional.\n\nReuse btintel_pcie_hex_dump() so the TLV dump is prefixed with the\ndevice name.\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "338150593939d88a8f62c6e0ffb1967f05197eae",
      "tree": "ea09bf2f3d5752bf021bfba923afe4d105e9255a",
      "parents": [
        "49dde1f01197bb3a06bc20e67c1ab6e5c2036004"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:43 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add target memory read logging under LOG_MASK\n\nLog the device address and length of each target memory read in\nbtintel_pcie_read_device_mem(), gated by BTINTEL_PCIE_LOG_TARGET_ACCESS\n(bit 5).\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "49dde1f01197bb3a06bc20e67c1ab6e5c2036004",
      "tree": "f2a2a5b18e5c5a24450d6d8540f28aa102bc508c",
      "parents": [
        "2069ae6af75d947af8b28e5d2539f69acba7d0f6"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:42 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add MAC access logging under LOG_MASK\n\nLog MAC access grant and release along with the FUNC_CTRL register\nvalue, gated by BTINTEL_PCIE_LOG_MAC_ACCESS (bit 4). Also report MAC\naccess timeouts unconditionally as errors since they indicate a stuck\ncontroller.\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "2069ae6af75d947af8b28e5d2539f69acba7d0f6",
      "tree": "56ac0b484c56d2ae22a7ab556ef2bccc45d29065",
      "parents": [
        "2b0203fc3987037d5070b035199718e13b0300e7"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:41 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add Sx transition logging under LOG_MASK\n\nLog suspend and resume entry with the decoded PM event and target D\nstate, the time taken to enter D3, and IPC sleep control register\nwrites, all gated by BTINTEL_PCIE_LOG_SX (bit 3). Enable this category\nby default alongside alive interrupt logging.\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "2b0203fc3987037d5070b035199718e13b0300e7",
      "tree": "cb8f1903de2b8c38c1ac51a5f864231ae3c338dc",
      "parents": [
        "6945099a7932d0dcb875b9e345c0057fd88145e7"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:40 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add alive interrupt logging under LOG_MASK\n\nPromote alive interrupt context transitions in btintel_pcie_send_sync()\nand the GP0 handler from bt_dev_dbg() to informational logs gated by\nBTINTEL_PCIE_LOG_ALIVE_INTR (bit 2), and log when the driver starts\nwaiting on the alive interrupt during MAC init.\n\nEnable this category by default.\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "6945099a7932d0dcb875b9e345c0057fd88145e7",
      "tree": "ff21216d6abf3ecbd40b1e98ce6e784669072f10",
      "parents": [
        "d751a649d75fc7cfaa835cfe4e5892bee3d58a81"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:39 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:36 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add TX/RX packet dumps under LOG_MASK\n\nLog a one-line summary (packet type, opcode/event/handle, length) and a\nhex dump of every HCI packet sent and received, gated independently by\nBTINTEL_PCIE_DUMP_TX (bit 0) and BTINTEL_PCIE_DUMP_RX (bit 1).\n\nPrefix the hex dump with the device name via a btintel_pcie_hex_dump()\nhelper, falling back to the PCI device name when hdev is not yet\nregistered so early messages do not print \"null\".\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d751a649d75fc7cfaa835cfe4e5892bee3d58a81",
      "tree": "e0dc75b464f3efa133a725c95088516813d9f5ea",
      "parents": [
        "800442f46258724a021be1c6111beb0aaee0f306"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Thu Oct 29 15:23:38 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add LOG_MASK parsing from debug INI\n\nRead an optional LOG_MASK entry from ibt_bt_dbg_cfg.ini and store it in\na new log_mask field so that diagnostic logging can be selected per\ndevice without rebuilding the driver. The mask defaults to 0 and an\ninvalid or missing entry leaves it unchanged. Preserve existing DBG_PATH\nand ENABLE_INI handling.\n\nIndividual logging categories are introduced by follow-up patches.\n\nAssisted-by: Copilot:Claude Opus 4.7\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "800442f46258724a021be1c6111beb0aaee0f306",
      "tree": "3e28a4d3c9bf0eaede0a328e0a04c8398d9a26b6",
      "parents": [
        "313c29e303e076c5c9549e0572596861849eb8cb"
      ],
      "author": {
        "name": "Kiran K",
        "email": "kiran.k@intel.com",
        "time": "Tue Oct 27 18:48:50 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btintel: check FIPS status before firmware download\n\nIntel Bluetooth controllers (PCIe and USB) from Scorpius Peak2 onwards,\nexcept BlazarIW, report bootloader self-test results (CRC, security,\nand patch) in the INTEL_TLV_FIPS_STS TLV of the Intel Read Version\nevent. Act on them before firmware download:\n\n  1. CRC failure      -\u003e abort download.\n  2. Security failure -\u003e abort on USB / HW reset and retry on PCIe.\n  3. Patch failure    -\u003e abort on USB / HW reset and retry on PCIe.\n\nSigned-off-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "313c29e303e076c5c9549e0572596861849eb8cb",
      "tree": "b2de64b45d92ef1930b08c3a9c87c1862fcffa89",
      "parents": [
        "d95c5e123f444be0d4299d956ef48899c8f4adf9"
      ],
      "author": {
        "name": "Arnaud Bonnet",
        "email": "abo@medichon.fr",
        "time": "Fri Oct 23 11:36:45 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btmtk: remove redundant memory barrier with helper\n\nThe test_and_clear_bit() call works as a full memory barrier, thus it is\nnot required to emit a barrier using smp_mb__after_atomic() before\nwake_up_bit().\n\nReplace the whole sequences with test_and_clear_wake_up_bit(), which was\nintroduced later in commit 52d633def56c (\"sched: Add\ntest_and_clear_wake_up_bit() and atomic_dec_and_wake_up()\") as a wrapper\nfor the correct sequence.\n\nSigned-off-by: Arnaud Bonnet \u003cabo@medichon.fr\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d95c5e123f444be0d4299d956ef48899c8f4adf9",
      "tree": "f6dca8cc3950a1d1033b235fc1e8835985bdea82",
      "parents": [
        "0c0c3d78564313905c90e9662db4a12f2a193aff"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Oct 22 11:37:14 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Allow COMPILE_TEST without ACPI\n\nThe driver only uses ACPI for the product reset method, so make that\ndepend on CONFIG_ACPI and allow the driver with COMPILE_TEST, so it is\nbuild tested on architectures without ACPI as well, such as User Mode\nLinux. Without ACPI the reset method reports it is not supported, as it\ndoes when the device has no ACPI handle.\n\nAssisted-by: OpenCode:claude-opus-5.5\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "0c0c3d78564313905c90e9662db4a12f2a193aff",
      "tree": "d94ed8b3071e60014fccbe3691344873330092e9",
      "parents": [
        "aafcf2bc99843104faf35da89a338d9e97f5d11d"
      ],
      "author": {
        "name": "Kevin Dewald",
        "email": "kevin@simpleble.org",
        "time": "Mon Nov 02 09:00:08 2026 -0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: MGMT: Send Connection Subrate on LE connection and update\n\nUserspace is not told the parameters of LE connections: the Connection\nSubrate event is only sent for LE Connection Rate Change, which needs\nthe Shorter Connection Interval feature, and nothing is sent when a\nconnection is established or updated with LE Connection Update\nComplete. Applications that need the connection interval, e.g. to\nestimate throughput or latency, have to read it from HCI traffic\ninstead.\n\nKeep the connection rate parameters, which the event reports, in sync\nwhen an LE connection is established and after each LE Connection\nUpdate, with the interval converted to units of 0.125 ms, and send the\nevent then. As these do not report subrating, keep the subrate factor\nand continuation number of the last connection rate change, or 1 and 0\nif there was none. Load Connection Subrate then also compares new\nparameters against the current ones rather than those of the last\nconnection rate change, and a failed connection rate change reports\nthe current parameters.\n\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Kevin Dewald \u003ckevin@simpleble.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "aafcf2bc99843104faf35da89a338d9e97f5d11d",
      "tree": "0b51a2f854210b76ec2a1df9d9cbbfc0d986053b",
      "parents": [
        "c8d35b42cd8e428f9815d04e1e0158372d779f09"
      ],
      "author": {
        "name": "Eric Dumazet",
        "email": "edumazet@kernel.org",
        "time": "Fri Oct 16 17:03:14 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: hci_nokia: use skb_put_padto()\n\nskb_pad() does not change skb-\u003elen, callers have to follow it\nwith skb_put(), which is error prone.\n\nUse skb_put_padto() instead of the open-coded sequence in\nnokia_enqueue().\n\nSigned-off-by: Eric Dumazet \u003cedumazet@kernel.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "c8d35b42cd8e428f9815d04e1e0158372d779f09",
      "tree": "5418ac9a7305391b6c4e2c683389fc70869c1c4b",
      "parents": [
        "a483854c7a4a56f9ff2ee833b20833c0cb645078"
      ],
      "author": {
        "name": "Sai Teja Aluvala",
        "email": "aluvala.sai.teja@intel.com",
        "time": "Fri Oct 16 08:29:21 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: add HW rfkill interrupt/doorbell flow\n\nAdd host-driven HW rfkill handling for Intel PCIe Bluetooth\ncontrollers and report state changes to the Bluetooth stack through\nhci_rfkill_set_hw_state(). The GP2 and HW_RFKILL MSI-X hardware\ncauses are enabled so that the host can detect a HW rfkill assertion\nand hand its acknowledgment back to firmware.\n\nOn a HW_RFKILL interrupt, a delayed worker reads the FUNC_CTRL and\nIPC_CONTROL registers to determine whether the switch is asserted or\nreleased. On assertion, the worker marks HW rfkill as active and\nreports a blocked state directly. On release, it clears the\nIPC_CONTROL HW rfkill doorbell bit, waits for the firmware\u0027s GP2\nacknowledgment that matches the requested transition, and reports\nan unblocked state to the stack only once that acknowledgment\narrives. A release is only handled once FUNC_CTRL shows the switch\nreleased, as IPC_CONTROL may still hold the acknowledgment sent by\nshutdown while the switch is asserted. IPC_CONTROL register\nread-modify-write updates and the wait state/done flags are\nserialized with a new ipc_lock, which the GP2 handler also takes, so\na late acknowledgment of a timed-out doorbell cannot complete the\nnext one. A new rfkill_doorbell_lock serializes the doorbell\ntransitions of the worker and shutdown.\n\nThe worker does nothing until setup has completed, as firmware is\nnot ready for the handshake before then. After a successful setup\nor resume, an initial state check is scheduled. That check reports\nan already-asserted HW rfkill state, and also reports a release if\nrfkill was asserted before suspend and cleared while the controller\nwas asleep; otherwise it is a no-op so it cannot suppress a later\ngenuine transition.\n\nThe HW_RFKILL MSI-X cause is masked before synchronizing interrupts\nand canceling or draining the worker across reset, probe failure,\nremove, and suspend, and is unmasked again after setup and resume\nsucceed. GP2 is left enabled throughout.\n\nMonitoring stays enabled across shutdown, so HW rfkill events are\nstill reported while HCI is down. On an active assertion, shutdown\nsets the doorbell bit and waits for the GP2 acknowledgment right\nbefore the HCI reset, since firmware accepts no other command after\nit. An assertion while HCI is down needs no doorbell, as the\ncontroller is already off. Firmware accepts HCI reset in any HW\nrfkill state, so shutdown relies on the cached state; an assertion\nthe worker has not seen yet is handled like one while HCI is down.\n\nSince a masked cause still latches, the MSI-X handler only queues the\nworker while HW_RFKILL is unmasked, and remove and probe failure\ndisable the worker so it cannot be requeued after data is freed.\n\nSigned-off-by: Sai Teja Aluvala \u003caluvala.sai.teja@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "a483854c7a4a56f9ff2ee833b20833c0cb645078",
      "tree": "787543f6b41d610998ab292068869ca5ee4f4251",
      "parents": [
        "88397423671f2b54119a6162a1834d207dcf1a81"
      ],
      "author": {
        "name": "Sai Teja Aluvala",
        "email": "aluvala.sai.teja@intel.com",
        "time": "Fri Oct 16 08:29:20 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: Add HCI interface for HW rfkill events\n\nAdd hci_rfkill_set_hw_state() so that transport drivers can report\nhardware rfkill switch changes to the HCI stack through the same\npath used for software rfkill.\n\nhci_rfkill_set_hw_state() checks HCI_UNREGISTER under\nhdev-\u003eunregister_lock and schedules a new hdev-\u003erfkill_block work\nitem while still holding that lock, so hci_unregister_dev() cannot\ndestroy hdev-\u003erfkill before the work runs. The hardware state is\nenforced even when no rfkill device exists (e.g. CONFIG_RFKILL\u003dn).\nOn release, if not soft blocked, HCI_RFKILLED is cleared before\nrfkill core sends its async event, so a userspace power-on triggered\nby that event does not observe a stale flag.\n\nA new hdev-\u003erfkill_lock serializes hci_rfkill_set_hw_state(),\nhdev-\u003erfkill_block and the rfkill core\u0027s set_block callback. The\nrfkill state is read and HCI_RFKILLED updated under that lock, so a\nhardware rfkill event and a concurrent userspace soft block/unblock\ncannot leave a stale state applied. The reported hardware state is\ntracked in a new HCI_HW_RFKILLED flag, and a soft unblock keeps\nHCI_RFKILLED set while it is set, so the controller cannot be\npowered on under a hard block. The soft state accepted by set_block\nis tracked in a new HCI_SW_RFKILLED flag, and hdev-\u003erfkill_block\ncombines the two. The rfkill core state is not read, as around\nset_block it may still hold a change that is about to be reverted.\n\nWhile a user channel is open, the set_block callback still refuses\nsoft rfkill with -EBUSY. A HW rfkill block cannot be refused, so\nhdev-\u003erfkill_block sets HCI_RFKILLED but leaves the device up for the\nuser channel; once it is closed, the flag blocks the next power on.\n\nSigned-off-by: Sai Teja Aluvala \u003caluvala.sai.teja@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "88397423671f2b54119a6162a1834d207dcf1a81",
      "tree": "34077a7a0e5cc1f2ebb24084148d4d630c4bbe02",
      "parents": [
        "19a13d870f040e2f4bd8485abe6b5dc7c94f1134"
      ],
      "author": {
        "name": "Ton Sharp",
        "email": "66ton99@gmail.com",
        "time": "Thu Oct 15 14:49:01 2026 +0300"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: hci_event: strip Broadcom vendor bits from legacy adv report type\n\nBroadcom controllers running ROM firmware on Apple T2 Macs (where no\nRAM patchram exists, e.g. BCM4364B3 on MacBookPro16,1) set vendor bits\n0x10/0x20/0x80 in the legacy LE Advertising Report Event_Type.\n\nAs a result, directed advertisements (ADV_DIRECT_IND) arrive as\n0x81/0x91/0xa1 instead of 0x01. Because process_adv_report() drops any\nlegacy report with type \u003e LE_ADV_SCAN_RSP (0x04) as an unknown advertising\npacket type, bonded LE peripherals (such as Apple Magic Mouse/Keyboard)\nand Chrome passkey proximity scans fail to discover or reliably reconnect\nto the host.\n\nThe valid legacy type is always located in the low nibble. Mask the type\nfield for Broadcom controllers (manufacturer 15) when it is out of range.\nValid legacy reports (0x00-0x04) remain untouched, low nibbles \u003e\u003d 5 remain\nout of range and will continue to be dropped, and controllers from other\nmanufacturers are unaffected.\n\nThe fix is based on the initial t2linux patch from Jose Miguel Ochoa.\n\nLink: https://lore.kernel.org/r/3352A23E-EA42-4366-BBAA-459CEAE6F51B@live.com\nSuggested-by: Jose Miguel Ochoa \u003cjosemiguelo.ochoa@gmail.com\u003e\nSigned-off-by: Ton Sharp \u003c66ton99@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "19a13d870f040e2f4bd8485abe6b5dc7c94f1134",
      "tree": "ce235aad95c5053145fb2093c28833a8fc965c83",
      "parents": [
        "fc18843f7abcc17ba1fc7e1031368e5019e2a7c4"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Thu Oct 15 14:54:31 2026 +0300"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:35 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Configure YoYo DBGC buffer allocations\n\nParse DBGC buffer allocation TLVs for DBGC1 through DBGC3. Validate the\nallocation ID, DRAM location, fragment count, requested size, and\nminimum fragment size before storing each allocation.\n\nUse configured fragment counts and sizes for DMA buffers, firmware\ncontext descriptors, and coredump collection. On MDBGC devices, omit\nunconfigured buffer IDs when YoYo is enabled; retain legacy allocations\nwhen YoYo configuration is absent or invalid. Single-DBGC devices use\nDBGC1.\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "fc18843f7abcc17ba1fc7e1031368e5019e2a7c4",
      "tree": "23b1b69844779d498815167705bc0cf5ffd90984",
      "parents": [
        "8bb9a261e8566ef172d6157a4fc5fab1edd9bb03"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Thu Oct 15 14:54:30 2026 +0300"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:34 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Validate the YoYo DEBUG_INFO TLV\n\nRequire a DEBUG_INFO TLV in the YoYo firmware configuration. Validate\nits payload length, version, Bluetooth domain, external image type,\nand Bluetooth core type before accepting the configuration.\n\nReject missing or invalid metadata so the driver keeps legacy DBGC\ndefaults instead of enabling an incompatible configuration.\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "8bb9a261e8566ef172d6157a4fc5fab1edd9bb03",
      "tree": "b2c706034b29321d95606c72b4a8448efa202d52",
      "parents": [
        "60b10121db602a43ada3dbc39792bbf93d25991b"
      ],
      "author": {
        "name": "Ajaykv",
        "email": "ajay.k.v@intel.com",
        "time": "Thu Oct 15 14:54:29 2026 +0300"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:34 2026 -0500"
      },
      "message": "Bluetooth: btintel_pcie: Add initial YoYo debug support\n\nAdd an optional YoYo firmware configuration path to the Intel PCIe\nBluetooth driver. Read DBG_PATH and ENABLE_INI from\nibt_bt_dbg_cfg.ini, and load intel/ibt_debug_yoyo.bin only when YoYo\nis enabled and host DRAM routing is selected.\n\nIntroduce a runtime context and bounded TLV-stream validation helper.\nInitialize and clean up the context with PCI probe and removal, while\nfalling back to legacy debug behavior if optional YoYo data is missing\nor invalid.\n\nRuntime validation of the complete P1-P3 series produced:\n[    3.286504] Bluetooth: Core ver 2.22\n[    3.297359] Bluetooth: HCI device and connection manager initialized\n[    3.297373] Bluetooth: HCI socket layer initialized\n[    3.297376] Bluetooth: L2CAP socket layer initialized\n[    3.297384] Bluetooth: SCO socket layer initialized\n[    3.332848] Bluetooth: YoYo: configuration loaded and validated\n[3.360857-3.361712] Bluetooth: DBGC1-3: each 16 x 256 KiB (4 MiB)\n[3.361715] Bluetooth: MDBGC DBGC1-3: each 16 x 256 KiB\n[    3.397439] Bluetooth: hci0: Device revision is 0\n[    3.397442] Bluetooth: hci0: Secure boot is enabled\n[    3.397443] Bluetooth: hci0: OTP lock is disabled\n[    3.397444] Bluetooth: hci0: API lock is enabled\n[    3.397444] Bluetooth: hci0: Debug lock is disabled\n\nSigned-off-by: Ajaykv \u003cajay.k.v@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "60b10121db602a43ada3dbc39792bbf93d25991b",
      "tree": "71f7fbabaad586e1b5f9e557c5d225e01bf5f170",
      "parents": [
        "ed4d302af778b9e2ead28134a2196c09a4ad248a"
      ],
      "author": {
        "name": "Kevin Dewald",
        "email": "kevin@simpleble.org",
        "time": "Mon Nov 02 09:00:00 2026 -0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: MGMT: Fix discovery stuck after a failed Stop Discovery\n\nStop Discovery moves the discovery to DISCOVERY_STOPPING, and\nstop_discovery_complete() only moves it on to DISCOVERY_STOPPED when\nstopping succeeded. When it fails, for example because LE Set Scan\nEnable times out, nothing moves the discovery out of\nDISCOVERY_STOPPING: Stop Discovery is rejected, as the discovery is not\nactive anymore, and the LE scan timeout was cancelled before the scan\nwas disabled. Until the controller is powered off, every Start\nDiscovery then fails with Busy, and hci_update_passive_scan_sync()\nskips background scanning, so devices set to auto-connect are not\nconnected anymore.\n\nMove the discovery back to DISCOVERY_FINDING when stopping it failed\nwhile its inquiry or active LE scan is still running, so that it can be\nstopped again. Only change the state while the discovery is still\nstopping, as Inquiry Cancel may already have stopped it, for example\nwhen only the passive scan could not be disabled, and a new Start\nDiscovery may have followed. Do this under hci_dev_lock(), like the\ncommand completions that change these flags, and before replying, so\nthat a client acting on the reply sees the new state. Only cancel the\nLE scan timeout once the scan is disabled, so that the discovery still\nends on its own, except when suspending, where it is still cancelled\nfirst.\n\nA timed out LE Set Scan Enable can still complete afterwards, which\ncancels the timeout as well, so also stop the discovery when its scan\nis disabled while the timeout is pending, or while the timeout work\nwaits for the lock.\n\nFixes: 0e05bba6f6f8 (\"Bluetooth: Update stop_discovery to use HCI request\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Kevin Dewald \u003ckevin@simpleble.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ed4d302af778b9e2ead28134a2196c09a4ad248a",
      "tree": "c39a5f484f65bc5f0460484db5a41d9a3954b994",
      "parents": [
        "1eb52f35fc8fb06ab7f2973fff29cba81f96b947"
      ],
      "author": {
        "name": "Yifan Zhang",
        "email": "yfzhang23@stu.pku.edu.cn",
        "time": "Mon Nov 02 19:58:37 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: validate retained LE Set CIG Parameters command length\n\nhci_cc_le_set_cig_params() validates the controller response but not the\nparameters of the previously sent command.  A short command can claim a\nlarge num_cis without containing the corresponding cis[] array.  A\ncomplete successful response then makes the handler read beyond the\ncommand skb while looking up each CIS ID.\n\nKASAN reports:\n\n  BUG: KASAN: slab-out-of-bounds in hci_cc_le_set_cig_params\n  Read of size 1\n  hci_cc_le_set_cig_params\n  hci_cmd_complete_evt\n  hci_event_packet\n\nObtain the retained parameter length and require both the fixed header and\nthe complete CIS array before using the command data.\n\nThe reproducer no longer triggers a KASAN report with this change.\n\nFixes: 71e9588435c3 (\"Bluetooth: ISO: use correct CIS order in Set CIG Parameters event\")\nCloses: https://lore.kernel.org/linux-bluetooth/179317463153.87610.8996555110609321376@stu.pku.edu.cn/\nSigned-off-by: Yifan Zhang \u003cyfzhang23@stu.pku.edu.cn\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "1eb52f35fc8fb06ab7f2973fff29cba81f96b947",
      "tree": "c2e847bfc78c955f52a942c52c6da030f7b89a84",
      "parents": [
        "a7c5c18b7cc30dcd2a9ae5a0fb38378d3998417e"
      ],
      "author": {
        "name": "Yifan Zhang",
        "email": "yfzhang23@stu.pku.edu.cn",
        "time": "Mon Nov 02 19:58:37 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: validate retained LE Create CIS command length\n\nhci_cs_le_create_cis() retrieves the parameters of the previously sent\ncommand without their length.  It then trusts num_cis and walks the\nflexible cis[] array when a controller reports a failed command.\n\nA five-byte HCI command containing only num_cis can therefore make the\nhandler read beyond the command skb.  KASAN reports:\n\n  BUG: KASAN: slab-out-of-bounds in hci_cs_le_create_cis\n  Read of size 2\n  hci_cs_le_create_cis\n  hci_cmd_status_evt\n  hci_event_packet\n\nAdd a length-returning saved-command helper and require the fixed header\nand complete CIS array before walking it.\n\nThe reproducer no longer triggers a KASAN report with this change.\n\nFixes: 26afbd826ee3 (\"Bluetooth: Add initial implementation of CIS connections\")\nCloses: https://lore.kernel.org/linux-bluetooth/179317462624.87574.6271582002629080499@stu.pku.edu.cn/\nSigned-off-by: Yifan Zhang \u003cyfzhang23@stu.pku.edu.cn\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "a7c5c18b7cc30dcd2a9ae5a0fb38378d3998417e",
      "tree": "5eb31ec76e57d98a3a737da1ea100c1566fea38f",
      "parents": [
        "a9f9eeb5344fc7dc625e5700ccf09891bc2603b5"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Fri Oct 30 22:27:45 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Initialize advertising RPA work only once\n\nhci_add_adv_instance() also updates existing instances and calls\nINIT_DELAYED_WORK() on their rpa_expired_cb every time, even when the\nwork is pending or running. cancel_delayed_work_sync() then no longer\nfinds the work, so hci_remove_adv_instance() can free the instance\nunder it:\n\n  hdev-\u003eworkqueue                 MGMT_OP_ADD_EXT_ADV_PARAMS\n  adv_instance_rpa_expired()\n                                  hci_dev_lock(hdev)\n                                  hci_add_adv_instance()\n                                    INIT_DELAYED_WORK()\n                                  mgmt_pending_new() fails\n                                  hci_remove_adv_instance()\n                                    cancel_delayed_work_sync()\n                                      returns without waiting\n                                    kfree(adv)\n                                  hci_dev_unlock(hdev)\n    adv-\u003erpa_expired \u003d true\n\nThe work has been initialized on every update since it was added.\nInitialize it only when the instance is allocated.\n\nKASAN report as below:\n\n    BUG: KASAN: slab-use-after-free in adv_instance_rpa_expired+0x139/0x160\n    Write of size 1 at addr ffff888108d84b2e by task kworker/u17:0/504\n\n    Workqueue: hci0 adv_instance_rpa_expired\n    Call Trace:\n     adv_instance_rpa_expired+0x139/0x160\n\n    Allocated by task 560:\n     hci_add_adv_instance+0x68d/0x9d0\n     add_ext_adv_params+0x4d4/0xb60\n     hci_sock_sendmsg+0x128b/0x22e0\n\n    Freed by task 594:\n     kfree+0x307/0x580\n     hci_remove_adv_instance+0x230/0x540\n     add_ext_adv_params+0xa43/0xb60\n     hci_sock_sendmsg+0x128b/0x22e0\n\n    Last potentially related work creation:\n     insert_work+0x37/0x210\n     __queue_work+0xaba/0x1270\n     call_timer_fn+0x171/0x500\n\n    The buggy address belongs to the object at ffff888108d84800\n     which belongs to the cache kmalloc-1k of size 1024\n    The buggy address is located 814 bytes inside of\n     freed 1024-byte region [ffff888108d84800, ffff888108d84c00)\n\nFixes: a73c046a2869 (\"Bluetooth: Implement Set ADV set random address\")\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "a9f9eeb5344fc7dc625e5700ccf09891bc2603b5",
      "tree": "b773290f251e704ace8070693e600a68e4f632a8",
      "parents": [
        "d90f24dc389b9a7524aaac109021d1530fa180f0"
      ],
      "author": {
        "name": "Jinwang Li",
        "email": "jinwang.li@oss.qualcomm.com",
        "time": "Thu Oct 29 17:41:04 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Ignore connection responses with wrong ident\n\nL2CAP/COS/CED/BI-28-C requires the IUT to ignore a Connection Response\nthat carries an invalid Identifier.\n\nl2cap_connect_create_rsp() only checks that a connection request is\noutstanding, not that the response answers it. Add an ident check\nagainst the pending request so that a mismatched response is dropped.\n\nFixes: 1da177e4c3f4 (\"Linux-2.6.12-rc2\")\nSigned-off-by: Jinwang Li \u003cjinwang.li@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d90f24dc389b9a7524aaac109021d1530fa180f0",
      "tree": "767778319e37294c81cd8d141fd2a324cfbbed63",
      "parents": [
        "9ff737119177a6c1ce6083ef8c0fc06355f11869"
      ],
      "author": {
        "name": "Kevin Dewald",
        "email": "kevin@simpleble.org",
        "time": "Thu Oct 29 13:28:32 2026 -0700"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:03 2026 -0500"
      },
      "message": "Bluetooth: MGMT: Clear disabled connection parameters when loading none\n\nLoad Connection Parameters only clears the disabled connection\nparameters when it loads more than one entry, so that loading a single\nentry can update the parameters of one device without dropping the\nothers. Loading no entries does not clear them either, though, which is\nwhat bluetoothd does when it starts without stored connection\nparameters.\n\nPair Device adds disabled connection parameters for the device it pairs\nwith, so these now survive bluetoothd restarts, and new connections to\nthe device keep using the parameters they were created with instead of\nthe defaults set since, e.g. the connection interval from main.conf.\n\nClear the disabled connection parameters unless a single entry is\nloaded, as was done for any number of entries before.\n\nFixes: 0ece498c27d8 (\"Bluetooth: MGMT: Make MGMT_OP_LOAD_CONN_PARAM update existing connection\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Kevin Dewald \u003ckevin@simpleble.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "9ff737119177a6c1ce6083ef8c0fc06355f11869",
      "tree": "88a24f1569640e7117605f8d8bf12048a62aaf9a",
      "parents": [
        "add463a65802bb117e4a17b8c00d747fa70399fc"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 29 21:12:29 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Copy the resolving-list IRK under RCU\n\nhci_le_add_resolve_list_sync() copies the peer IRK into the LE Add\nDevice To Resolving List command after hci_find_irk_by_addr() has\nreturned. The finder ends its RCU read-side section before returning\nthe borrowed entry, and neither the request worker nor\ninterleave_scan_work() holds hdev-\u003elock here. The resolving-list\nmembership check between the lookup and the copy takes hdev-\u003elock and\nmay sleep on it, which widens the window.\n\nWhen LL privacy programs a peer with address resolution enabled,\nMGMT_OP_LOAD_IRKS can free its IRK before the copy:\n\n  Request worker                   Management / RCU reclamation\n  hci_le_add_resolve_list_sync()\n    irk \u003d hci_find_irk_by_addr()\n                                   load_irks()\n                                     hci_dev_lock(hdev)\n                                     hci_smp_irks_clear(hdev)\n                                       list_del_rcu(), kfree_rcu()\n                                     hci_dev_unlock(hdev)\n                                   grace period ends, irk is freed\n    resolving-list membership check\n    memcpy(cp.peer_irk, irk-\u003eval, 16)\n\nCopy the IRK value in an RCU read-side section right after the lookup,\nas hci_le_set_privacy_mode_sync() does for the identity address. The\nsection ends before hdev-\u003elock is taken and before the synchronous HCI\ncommand is sent.\n\nKASAN reported this on a test kernel with scheduling hooks, whose\nframes appear in the trace. The report predates the hdev-\u003elock taken\nby the membership check.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in hci_le_add_resolve_list_sync+0x8d9/0x910\n    Read of size 16 at addr ffff88810d21452d by task kworker/u17:0/504\n\n    CPU: 2 UID: 0 PID: 504 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #2 PREEMPT(lazy)\n    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n    Workqueue: hci0 interleave_scan_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_le_add_resolve_list_sync+0x8d9/0x910\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_le_add_resolve_list_sync+0x8d9/0x910\n     kasan_report+0xe0/0x110\n     ? hci_le_add_resolve_list_sync+0x8d9/0x910\n     hci_le_add_resolve_list_sync+0x8d9/0x910\n     ? __pfx_hci_le_add_resolve_list_sync+0x10/0x10\n     ? pmbd_probe_hit_cookie+0xe7/0x1c0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_probe_hit_cookie+0xee/0x1c0\n     ? __pfx_pmbd_probe_hit_cookie+0x10/0x10\n     hci_le_add_accept_list_sync+0x18e/0x820\n     ? conn_params_copy+0x36e/0x650\n     ? __pfx_hci_le_add_accept_list_sync+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? conn_params_copy+0x3a0/0x650\n     hci_passive_scan_sync+0x95f/0x1f10\n     ? __pfx_hci_passive_scan_sync+0x10/0x10\n     ? debug_object_deactivate+0x2f8/0x3c0\n     ? pwq_dec_nr_in_flight+0x880/0xdf0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_acquire+0x17b/0x2f0\n     ? process_one_work+0x895/0x19c0\n     interleave_scan_work+0x11b/0x470\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 535:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_add_irk+0xb6/0x220\n     load_irks+0x5f9/0x840\n     hci_sock_sendmsg+0x128b/0x22e0\n     __sys_sendto+0x425/0x470\n     __x64_sys_sendto+0xe5/0x1c0\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n    Freed by task 0:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     __rcu_free_sheaf_prepare+0x65/0x2a0\n     rcu_free_sheaf+0x1f/0xe0\n     rcu_core+0x661/0x1d10\n     handle_softirqs+0x201/0x930\n     __irq_exit_rcu+0x110/0x1e0\n     irq_exit_rcu+0xe/0x20\n     sysvec_apic_timer_interrupt+0x6c/0x80\n     asm_sysvec_apic_timer_interrupt+0x1a/0x20\n\n    The buggy address belongs to the object at ffff88810d214500\n     which belongs to the cache kmalloc-64 of size 64\n    The buggy address is located 45 bytes inside of\n     freed 64-byte region [ffff88810d214500, ffff88810d214540)\n\n    The buggy address belongs to the physical page:\n    page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10d214\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n    raw: 0200000000000000 ffff8881000428c0 dead000000000100 dead000000000122\n    raw: 0000000000000000 0000000000200020 00000000f5000000 0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88810d214400: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810d214480: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003effff88810d214500: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n                                      ^\n     ffff88810d214580: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810d214600: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: e8907f76544f (\"Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 3\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "add463a65802bb117e4a17b8c00d747fa70399fc",
      "tree": "951b964cd88d8468f830504302086bbf01ea9ddf",
      "parents": [
        "ebc4f217c1fbe8364b5ef2ad8e3a8e9a1b2701a7"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 29 21:12:28 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: SMP: Protect LTK encryption with RCU\n\nsmp_ltk_encrypt() checks the security level of the LTK returned by\nhci_find_ltk() and then starts encryption with its EDIV, Rand, value\nand key size. The finder ends its RCU read-side section before\nreturning the borrowed entry, and neither caller holds hdev-\u003elock: the\nSMP Security Request handler runs from the receive path, and\nsetsockopt(BT_SECURITY) reaches smp_conn_security() with only the\nsocket and channel locks held.\n\nMGMT_OP_LOAD_LONG_TERM_KEYS can therefore free the LTK in between:\n\n  Socket security request          Management / RCU reclamation\n  smp_ltk_encrypt()\n    key \u003d hci_find_ltk()\n                                   load_long_term_keys()\n                                     hci_dev_lock(hdev)\n                                     hci_smp_ltks_clear(hdev)\n                                       list_del_rcu(), kfree_rcu()\n                                     hci_dev_unlock(hdev)\n                                   grace period ends, key is freed\n    smp_ltk_sec_level(key)\n    hci_le_start_enc(hcon, key-\u003eediv, key-\u003erand, key-\u003eval, ...)\n\nKeep an RCU read-side section across the lookup and every use of the\nkey. hci_le_start_enc() copies the key into the command and queues it\nwith a GFP_ATOMIC allocation, so the whole sequence can stay inside the\nsection.\n\nKFENCE reported this on a test kernel where the socket thread was\npaused after the lookup until the RCU callback had freed the key.\n\nKFENCE report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KFENCE: use-after-free read in smp_ltk_encrypt.isra.0+0xf3/0x370\n\n    Use-after-free read at 0x00000000c45332eb (in kfence-#128):\n     smp_ltk_encrypt.isra.0+0xf3/0x370\n     smp_conn_security+0x489/0x9d0\n     l2cap_sock_setsockopt+0x1bbe/0x2300\n     do_sock_setsockopt+0x1fb/0x430\n     __sys_setsockopt+0x106/0x180\n     __x64_sys_setsockopt+0xc2/0x160\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n    kfence-#128: 0x00000000d45af9b0-0x0000000053c1365e, size\u003d72, cache\u003dkmalloc-96\n\n    allocated by task 533 on cpu 0 at 50.484258s (0.449177s ago):\n     hci_add_ltk+0x1f5/0x3a0\n     load_long_term_keys+0x6ea/0x930\n     hci_sock_sendmsg+0x128b/0x22e0\n     sock_write_iter+0x4c0/0x550\n     vfs_write+0x637/0x1010\n     ksys_write+0x1b7/0x200\n     do_syscall_64+0x115/0x6a0\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\n    freed by task 0 on cpu 0 at 50.846944s (0.093664s ago):\n     __rcu_free_sheaf_prepare+0x261/0x2a0\n     rcu_free_sheaf_nobarn+0x1d/0x50\n     rcu_core+0x661/0x1d10\n     handle_softirqs+0x201/0x930\n     __irq_exit_rcu+0x110/0x1e0\n     irq_exit_rcu+0xe/0x20\n     sysvec_apic_timer_interrupt+0x6c/0x80\n     asm_sysvec_apic_timer_interrupt+0x1a/0x20\n     pv_native_safe_halt+0xf/0x20\n     default_idle+0x9/0x10\n     default_idle_call+0x6c/0xb0\n     do_idle+0x3a7/0x650\n     cpu_startup_entry+0x54/0x60\n     rest_init+0x15e/0x2b0\n     start_kernel+0x412/0x4b0\n     x86_64_start_reservations+0x18/0x30\n     x86_64_start_kernel+0x111/0x120\n     common_startup_64+0x13e/0x158\n\n    CPU: 2 UID: 0 PID: 534 Comm: l2cap-ltk-actor Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #5 PREEMPT(lazy)\n    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: 988c5997d320 (\"Bluetooth: Use the LTK after receiving a LE Security Request\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ebc4f217c1fbe8364b5ef2ad8e3a8e9a1b2701a7",
      "tree": "059f0465077ca4fee0a02f32beb0ee00a87ef5ce",
      "parents": [
        "281ddc4e01ab54cab07995f2a1b72cf81bf90eb5"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 29 21:12:27 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: SMP: Protect link keys during LTK derivation\n\nsc_generate_ltk() reads the type and value of the peer link key after\nhci_find_link_key() has returned. The finder ends its RCU read-side\nsection before returning the borrowed entry, and the SMP receive path\ndoes not hold hdev-\u003elock: l2cap_recv_acldata() releases it before the\nPDU is dispatched. The L2CAP connection and channel locks held by SMP\ndo not serialize with management link-key removal.\n\nWhen BR/EDR Secure Connections pairing derives an LTK from the stored\nlink key, MGMT_OP_LOAD_LINK_KEYS can free that key mid-derivation:\n\n  HCI RX worker (SMP)              Management / RCU reclamation\n  sc_generate_ltk()\n    key \u003d hci_find_link_key()\n                                   load_link_keys()\n                                     hci_dev_lock(hdev)\n                                     hci_link_keys_clear(hdev)\n                                       list_del_rcu(), kfree_rcu()\n                                     hci_dev_unlock(hdev)\n                                   grace period ends, key is freed\n    read key-\u003etype\n    smp_h6() or smp_h7() reads key-\u003eval\n\nHold an RCU read-side section from the lookup until the type and value\nhave been consumed. smp_h6() and smp_h7() only run the synchronous\nAES-CMAC library code, which neither sleeps nor allocates. Release the\nsection before sc_add_ltk(), which allocates with GFP_KERNEL.\n\nKASAN reported this on a test kernel whose scheduling hook paused the\nreceive worker after the lookup; the hook frames appear in the trace.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in smp_distribute_keys+0x2983/0x2b70\n    Read of size 1 at addr ffff88810618e9a6 by task kworker/u17:0/500\n\n    CPU: 0 UID: 0 PID: 500 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #1 PREEMPT(lazy)\n    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n    Workqueue: hci1 hci_rx_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? smp_distribute_keys+0x2983/0x2b70\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? smp_distribute_keys+0x2983/0x2b70\n     kasan_report+0xe0/0x110\n     ? smp_distribute_keys+0x2983/0x2b70\n     smp_distribute_keys+0x2983/0x2b70\n     ? __pfx_smp_distribute_keys+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_gate_maybe+0x47/0x60\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_probe_hit_cookie+0xe7/0x1c0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_probe_hit_cookie+0xee/0x1c0\n     ? __pfx_pmbd_probe_hit_cookie+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __asan_memset+0x23/0x50\n     ? smp_recv_cb+0x12e2/0x8f30\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     smp_recv_cb+0x12e2/0x8f30\n     ? __pfx_smp_recv_cb+0x10/0x10\n     ? __pfx___might_resched+0x10/0x10\n     ? __pfx_sched_balance_find_src_group+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_lock+0x182c/0x2590\n     ? l2cap_recv_frame+0x9ef/0x8830\n     ? __pfx___mutex_lock+0x10/0x10\n     ? __lock_acquire+0x466/0x2260\n     ? __pfx_l2cap_chan_hold_unless_zero+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? l2cap_recv_frame+0x13cc/0x8830\n     ? __pfx_smp_recv_cb+0x10/0x10\n     l2cap_recv_frame+0x13cc/0x8830\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_lock+0x182c/0x2590\n     ? __pfx_l2cap_recv_frame+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? find_held_lock+0x2b/0x80\n     ? l2cap_recv_acldata+0x1eb/0x10e0\n     ? __pfx___mutex_lock+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_unlock_slowpath+0x147/0x920\n     ? __pfx_l2cap_conn_hold_unless_zero+0x10/0x10\n     ? __pfx_hci_conn_enter_active_mode+0x10/0x10\n     ? l2cap_recv_acldata+0x13d/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     l2cap_recv_acldata+0xe9f/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     hci_rx_work+0x5a6/0xf00\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 500:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_add_link_key+0x474/0x840\n     hci_link_key_notify_evt+0x492/0xce0\n     hci_event_packet+0x894/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    Freed by task 0:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     __rcu_free_sheaf_prepare+0x65/0x2a0\n     rcu_free_sheaf+0x1f/0xe0\n     rcu_core+0x661/0x1d10\n     handle_softirqs+0x201/0x930\n     __irq_exit_rcu+0x110/0x1e0\n     irq_exit_rcu+0xe/0x20\n     sysvec_apic_timer_interrupt+0x6c/0x80\n     asm_sysvec_apic_timer_interrupt+0x1a/0x20\n\n    The buggy address belongs to the object at ffff88810618e980\n     which belongs to the cache kmalloc-64 of size 64\n    The buggy address is located 38 bytes inside of\n     freed 64-byte region [ffff88810618e980, ffff88810618e9c0)\n\n    The buggy address belongs to the physical page:\n    page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10618e\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n    raw: 0200000000000000 ffff8881000428c0 dead000000000122 0000000000000000\n    raw: 0000000000000000 0000000000200020 00000000f5000000 0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88810618e880: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810618e900: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003effff88810618e980: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n                                   ^\n     ffff88810618ea00: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810618ea80: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: b5ae344d4c0f (\"Bluetooth: Add full SMP BR/EDR support\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "281ddc4e01ab54cab07995f2a1b72cf81bf90eb5",
      "tree": "940e4d54e1a9a7c1581b38b8499256bf529dfe3c",
      "parents": [
        "3b70dd827b27bfadd89e7b1a2d422b04da38797c"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 29 21:12:26 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Keep link-key filtering inside RCU\n\nhci_find_link_key() must keep the matching link key allocated while it\nchecks the key against the blocked-key list. It currently leaves the\nkey-list RCU read-side section before passing k-\u003eval to\nhci_is_blocked_key(). That helper\u0027s own RCU section protects the\nblocked-key list, but it cannot keep an unlinked link key from being\nreclaimed.\n\nThe SMP receive path calls the finder without hdev-\u003elock: Secure\nConnections key distribution over BR/EDR reaches it through\nsmp_distribute_keys() and sc_generate_ltk(). With a stored peer link\nkey and a link-key entry in the blocked-key list,\nMGMT_OP_LOAD_LINK_KEYS can free the selected key before the comparison:\n\n  HCI RX worker (SMP)              Management / RCU reclamation\n  hci_find_link_key()\n    rcu_read_lock()\n    select k\n    rcu_read_unlock()\n                                   load_link_keys()\n                                     hci_dev_lock(hdev)\n                                     hci_link_keys_clear(hdev)\n                                       list_del_rcu(), kfree_rcu()\n                                     hci_dev_unlock(hdev)\n                                   grace period ends, k is freed\n    hci_is_blocked_key(hdev, ..., k-\u003eval)\n      memcmp() reads the freed key\n\nKeep the RCU read-side section active through the blocked-key\ncomparison and the warning that prints k-\u003ebdaddr, and release it before\nreturning on both matched-key paths. hci_find_ltk() already handles its\nblocked-key check this way.\n\nKASAN reported this on a test kernel whose scheduling hook paused the\nreceive worker after the lookup until the key had been freed.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in hci_is_blocked_key+0x2db/0x300\n    Read of size 1 at addr ffff88810b5f89a7 by task kworker/u17:0/502\n\n    CPU: 1 UID: 0 PID: 502 Comm: kworker/u17:0 Not tainted 7.2.0-rc6-pmb-bt-functional-v1+ #5 PREEMPT(lazy)\n    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n    Workqueue: hci1 hci_rx_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_is_blocked_key+0x2db/0x300\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_is_blocked_key+0x2db/0x300\n     kasan_report+0xe0/0x110\n     ? hci_is_blocked_key+0x2db/0x300\n     hci_is_blocked_key+0x2db/0x300\n     hci_find_link_key+0x12e/0x400\n     smp_distribute_keys+0x1830/0x2950\n     ? trace_hardirqs_on+0x18/0x160\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? queue_delayed_work_on+0xb3/0xf0\n     ? __pfx_smp_distribute_keys+0x10/0x10\n     ? __pfx_smp_send_cmd.isra.0+0x10/0x10\n     ? __cancel_work+0x1b0/0x290\n     ? __entry_text_end+0x1020f7/0x1020f9\n     ? lockdep_hardirqs_on_prepare+0xea/0x1a0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __asan_memset+0x23/0x50\n     ? smp_recv_cb+0x12c7/0x8d80\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     smp_recv_cb+0x12c7/0x8d80\n     ? __pfx_smp_recv_cb+0x10/0x10\n     ? __pfx___might_resched+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? stack_depot_save_flags+0x29/0x9a0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_lock+0x182c/0x2590\n     ? kasan_save_stack+0x42/0x60\n     ? l2cap_recv_frame+0x9ef/0x8830\n     ? __kasan_slab_free+0x5f/0x80\n     ? kmem_cache_free+0x242/0x580\n     ? kfree_skbmem+0x15e/0x1d0\n     ? sk_skb_reason_drop+0x12f/0x490\n     ? hci_event_packet+0x556/0xc70\n     ? hci_rx_work+0x367/0xf00\n     ? process_one_work+0x908/0x19c0\n     ? worker_thread+0x65c/0xe40\n     ? __pfx___mutex_lock+0x10/0x10\n     ? __lock_acquire+0x466/0x2260\n     ? __pfx_l2cap_chan_hold_unless_zero+0x10/0x10\n     ? l2cap_recv_frame+0x13cc/0x8830\n     ? __pfx_smp_recv_cb+0x10/0x10\n     l2cap_recv_frame+0x13cc/0x8830\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_lock+0x182c/0x2590\n     ? __pfx_l2cap_recv_frame+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? find_held_lock+0x2b/0x80\n     ? l2cap_recv_acldata+0x1eb/0x10e0\n     ? __pfx___mutex_lock+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __mutex_unlock_slowpath+0x147/0x920\n     ? __pfx_l2cap_conn_hold_unless_zero+0x10/0x10\n     ? __pfx_hci_conn_enter_active_mode+0x10/0x10\n     ? l2cap_recv_acldata+0x13d/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     l2cap_recv_acldata+0xe9f/0x10e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     hci_rx_work+0x5a6/0xf00\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 504:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_add_link_key+0x474/0x840\n     hci_link_key_notify_evt+0x492/0xce0\n     hci_event_packet+0x894/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    Freed by task 29:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     __rcu_free_sheaf_prepare+0x65/0x2a0\n     rcu_free_sheaf_nobarn+0x1d/0x50\n     rcu_core+0x661/0x1d10\n     handle_softirqs+0x201/0x930\n     run_ksoftirqd+0x33/0x60\n     smpboot_thread_fn+0x3bd/0x9a0\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    The buggy address belongs to the object at ffff88810b5f8980\n     which belongs to the cache kmalloc-64 of size 64\n    The buggy address is located 39 bytes inside of\n     freed 64-byte region [ffff88810b5f8980, ffff88810b5f89c0)\n\n    The buggy address belongs to the physical page:\n    page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x10b5f8\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n    raw: 0200000000000000 ffff8881000428c0 dead000000000100 dead000000000122\n    raw: 0000000000000000 0000000000200020 00000000f5000000 0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88810b5f8880: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810b5f8900: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n    \u003effff88810b5f8980: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n                                   ^\n     ffff88810b5f8a00: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810b5f8a80: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: 600a87490ff9 (\"Bluetooth: Implementation of MGMT_OP_SET_BLOCKED_KEYS.\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "3b70dd827b27bfadd89e7b1a2d422b04da38797c",
      "tree": "bcd78b6aed4c90ae7127c160536d35ef256858e6",
      "parents": [
        "5b7d0386a4e75c85479da0fbd9fd66a3e9201375"
      ],
      "author": {
        "name": "Ismail Tarim",
        "email": "ismailtarim7@gmail.com",
        "time": "Fri Oct 30 01:40:15 2026 +0300"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: btmtk: fix error handling in btmtk_usb_isointf_init()\n\nbtmtk_usb_isointf_init() submits the ISO interrupt IN URB and then\nsends the vendor command 0xfd98. If that command fails, the function\nreturns an error without killing the URB it has just submitted. The\ncaller then leaves BTMTK_ISOPKT_RUNNING clear, so the driver treats the\nISO path as inactive while its RX URB is still in flight, and\nbtmtk_usb_suspend() skips killing it. Kill the anchored URBs on this\npath, as the URB submission failure path already does.\n\nThe return value of __set_mtk_intr_interface() is also ignored: a\nfailure to select the ISO alternate setting or to find its endpoints\nis logged, but the function goes on to submit the URB. Return the\nerror instead.\n\nFixes: ceac1cb0259d (\"Bluetooth: btusb: mediatek: add ISO data transmission functions\")\nSigned-off-by: Ismail Tarim \u003cismailtarim7@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "5b7d0386a4e75c85479da0fbd9fd66a3e9201375",
      "tree": "8cb3557741268b475c81a6d6a523408cdf6b8255",
      "parents": [
        "7eac80614300563470cffabf4df2b63616787ee7"
      ],
      "author": {
        "name": "Michael McAllister",
        "email": "me@michaelmcallister.org",
        "time": "Wed Oct 21 20:51:12 2026 +0100"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: qca: Fix the WCN3950 NVM baud rate offset\n\nWCN3950 uses the HCI transport tag layout that stores the UART baud rate\nat byte 1, like WCN3991. However, QCA_WCN3950 precedes QCA_WCN3991 in\nqca_btsoc_type, so qca_tlv_check_data() writes the baud rate to byte 2\ninstead.\n\nOn a Motorola Moto G10 with WCN3950 and cmnv12.bin, configuring a 3 Mbps\nUART therefore leaves the NVM baud rate at its default 3.2 Mbps and\noverwrites the following byte. Firmware download completes, but the\nsubsequent HCI_RESET times out and Bluetooth initialization fails.\n\nInclude WCN3950 in the byte-1 case so the NVM baud rate matches the host\nUART without altering the following transport parameter.\n\nFixes: d5712c511cb3 (\"Bluetooth: qca: add WCN3950 support\")\nCc: stable@vger.kernel.org\nAssisted-by: LLM\nSigned-off-by: Michael McAllister \u003cme@michaelmcallister.org\u003e\nReviewed-by: Bartosz Golaszewski \u003cbartosz.golaszewski@oss.qualcomm.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "7eac80614300563470cffabf4df2b63616787ee7",
      "tree": "073798d716053f166ecd0a5fca565497eb91e09d",
      "parents": [
        "f05bd61a3213613de7848c8df2865492d5225023"
      ],
      "author": {
        "name": "Tobias Wilken",
        "email": "tooangel@tooangel.de",
        "time": "Wed Oct 21 08:58:33 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller\n\nSince MGMT_OP_SET_POWERED runs through hci_cmd_sync, powering on a\ncontroller that is blocked by rfkill fails with -ERFKILL from\nhci_dev_open_sync(), and mgmt_set_powered_complete() reports it with\nmgmt_status(err). mgmt_errno_status() has no case for -ERFKILL, so\nuserspace gets MGMT_STATUS_FAILED instead of MGMT_STATUS_RFKILLED.\n\nBefore that conversion, power on went through hci_power_on(), whose\nerror path mgmt_set_powered_failed() still maps -ERFKILL to\nMGMT_STATUS_RFKILLED. bluetoothd relies on that status: for\nRFKILLED it sets the adapter PowerState to \"off-blocked\" and returns\norg.bluez.Error.Blocked for the Powered property, for any other status\nit returns org.bluez.Error.Failed.\n\nWith the controller soft blocked, \"bluetoothctl power on\" printed\n\"Failed to set power on: org.bluez.Error.Failed\" and btmon showed\n\"Set Powered (0x0005) Status: Failed (0x03)\". With this change it\nprints org.bluez.Error.Blocked and btmon shows \"Status: RFKilled\n(0x12)\".\n\nMap -ERFKILL to MGMT_STATUS_RFKILLED in mgmt_errno_status().\n\nFixes: cf75ad8b41d2 (\"Bluetooth: hci_sync: Convert MGMT_SET_POWERED\")\nAssisted-by: LLM\nSigned-off-by: Tobias Wilken \u003ctooangel@tooangel.de\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f05bd61a3213613de7848c8df2865492d5225023",
      "tree": "83989bf1bdf8ce6555fa2ad106b872523c4f1064",
      "parents": [
        "674006912777747170ad70d7727804ad4f2d047f"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 22 20:05:56 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Protect resolving-list lookups\n\nThe host resolving list is updated under hdev-\u003elock, and each\nbdaddr_list_with_irk entry must remain alive throughout a lookup.\nhci_le_del_resolve_list_sync() and hci_le_add_resolve_list_sync()\ntraverse that list without taking the lock.\n\nOn an LE privacy-capable controller with a programmed entry, passive\nscan reconciliation can reach hci_le_del_resolve_list_sync() while a\nprivileged HCI_RAW client sends LE Clear Resolving List. The raw\ncommand does not take req_lock, and its successful completion runs\non the controller workqueue independently of request work:\n\n  Request work                     Raw HCI / event work\n  hci_le_del_resolve_list_sync()\n    lookup loads a list node\n                                   hci_sock_sendmsg()\n                                     queue LE Clear Resolving List\n                                   hci_cc_le_clear_resolv_list()\n                                     take hdev-\u003elock\n                                     unlink and free the node\n                                     release hdev-\u003elock\n    read the node\u0027s address/type\n\nThe clear can free the node after the lookup loads it and before its\naddress/type read, causing a use-after-free. The report below shows\nthis access with the delete helper on the faulting stack. The add\nhelper uses the same unprotected lookup.\n\nTake hdev-\u003elock around each resolving-list membership lookup and\nretain only a boolean result. This serializes traversal with clear\ncompletion and keeps entry pointers inside the protected section.\nRelease the lock before issuing a synchronous HCI command, whose\ncompletion also needs the lock.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in\n    hci_bdaddr_list_lookup_with_irk+0x106/0x120\n    Read of size 1 at addr ffff88810b036e16 by task kworker/u17:0/495\n\n    CPU: 2 UID: 0 PID: 495 Comm: kworker/u17:0 Not tainted\n    7.2.0-rc6-pmb-bt-functional-v1+ #3 PREEMPT(lazy)\n    Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix,\n    1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n    Workqueue: hci0 hci_cmd_sync_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_bdaddr_list_lookup_with_irk+0x106/0x120\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_bdaddr_list_lookup_with_irk+0x106/0x120\n     kasan_report+0xe0/0x110\n     ? hci_bdaddr_list_lookup_with_irk+0x106/0x120\n     hci_bdaddr_list_lookup_with_irk+0x106/0x120\n     hci_le_del_resolve_list_sync.isra.0+0xd6/0x3f0\n     ? __pfx_hci_le_del_resolve_list_sync.isra.0+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     hci_le_del_accept_list_sync.isra.0+0x11c/0x290\n     ? __pfx_hci_le_del_accept_list_sync.isra.0+0x10/0x10\n     ? hci_passive_scan_sync+0x551/0x1e80\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_release+0xc8/0x280\n     hci_passive_scan_sync+0x71c/0x1e80\n     ? __pfx_hci_passive_scan_sync+0x10/0x10\n     ? find_held_lock+0x2b/0x80\n     ? hci_lookup_le_connect+0xe1/0x3c0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? find_held_lock+0x2b/0x80\n     ? hci_update_passive_scan_sync+0x437/0x950\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_release+0xc8/0x280\n     hci_update_passive_scan_sync+0x461/0x950\n     hci_cmd_sync_work+0x1b3/0x450\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 495:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_bdaddr_list_add_with_irk+0x183/0x3e0\n     hci_cc_le_add_to_resolv_list+0x18c/0x240\n     hci_cmd_complete_evt+0x373/0xab0\n     hci_event_packet+0x4e8/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    Freed by task 497:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     kfree+0x307/0x580\n     hci_bdaddr_list_clear+0x134/0x230\n     hci_cc_le_clear_resolv_list+0x13d/0x240\n     hci_cmd_complete_evt+0x373/0xab0\n     hci_event_packet+0x4e8/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    The buggy address belongs to the object at ffff88810b036e00\n    which belongs to the cache kmalloc-64 of size 64\n    The buggy address is located 22 bytes inside of\n    freed 64-byte region [ffff88810b036e00, ffff88810b036e40)\n\n    The buggy address belongs to the physical page:\n    page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0\n    pfn:0x10b036\n    flags: 0x200000000000000(node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n    raw: 0200000000000000 ffff8881000428c0 dead000000000100\n    dead000000000122\n    raw: 0000000000000000 0000000000200020 00000000f5000000\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff88810b036d00: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n     ffff88810b036d80: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003effff88810b036e00: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n                             ^\n     ffff88810b036e80: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n     ffff88810b036f00: fa fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    Disabling lock debugging due to kernel taint\n\nFixes: e8907f76544f (\"Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 3\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "674006912777747170ad70d7727804ad4f2d047f",
      "tree": "ef8aec0b852558a98b22ba24657ca091371d08e8",
      "parents": [
        "855c9a54608f1e94f4c52afe3790def30534155a"
      ],
      "author": {
        "name": "Cen Zhang",
        "email": "zzzccc427@gmail.com",
        "time": "Thu Oct 22 20:16:36 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Copy the LE accept list under hdev-\u003elock\n\nThe LE accept-list mirror consists of bdaddr_list entries that are\nadded, removed and freed under hdev-\u003elock. The ordinary branch of\nhci_update_accept_list_sync() traverses this list without that lock.\nThe request worker\u0027s req_lock does not serialize raw HCI completions,\nand the RCU sections protect connection and pending-action lookups,\nnot the accept-list nodes.\n\nChanging connectability can reach this iterator through\nset_connectable_sync(), hci_update_connectable_sync(),\nhci_update_passive_scan_sync() and hci_passive_scan_sync(). With a\npopulated mirror, a privileged raw HCI sender can issue\nHCI_OP_LE_CLEAR_ACCEPT_LIST while request work is reconciling it:\n\n  Request work                    HCI event work\n  select b and successor t\n                                  hci_cc_le_clear_accept_list()\n                                    hci_dev_lock(hdev)\n                                    hci_bdaddr_list_clear()\n                                      unlink nodes and kfree(b)\n                                    hci_dev_unlock(hdev)\n  read b-\u003ebdaddr_type\n\nThe clear completion can therefore free the selected node before its\nfield read, or the saved successor before the iterator advances.\nKASAN reported a one-byte read of bdaddr_type from the freed node.\n\nCopy each entry\u0027s address and type under hdev-\u003elock and reconcile the\nprivate array instead. Release the mutex before issuing synchronous\ncommands, since their completion handlers also acquire it. Free the\ncopy after iteration and use the existing error path to disable\naccept-list filtering if allocation fails.\n\nThis change has not been runtime-tested.\n\nKASAN report as below:\n\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n    BUG: KASAN: slab-use-after-free in hci_passive_scan_sync+0x1cc4/0x1f80\n    Read of size 1 at addr ffff888105ee6c56 by task kworker/u17:1/499\n\n    Workqueue: hci0 hci_cmd_sync_work\n    Call Trace:\n     \u003cTASK\u003e\n     dump_stack_lvl+0x93/0xd0\n     print_report+0xce/0x630\n     ? hci_passive_scan_sync+0x1cc4/0x1f80\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __virt_addr_valid+0x20d/0x410\n     ? hci_passive_scan_sync+0x1cc4/0x1f80\n     kasan_report+0xe0/0x110\n     ? hci_passive_scan_sync+0x1cc4/0x1f80\n     hci_passive_scan_sync+0x1cc4/0x1f80\n     ? pmbd_gate_site_armed+0x31/0x1c0\n     ? __pfx_hci_passive_scan_sync+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? pmbd_probe_hit_cookie+0x10/0x1c0\n     ? __pfx_pmbd_probe_hit_cookie+0x10/0x10\n     ? hci_update_passive_scan_sync+0x43f/0x9e0\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_release+0xc8/0x280\n     hci_update_passive_scan_sync+0x473/0x9e0\n     hci_update_connectable_sync+0x13c/0x250\n     set_connectable_sync+0x39/0xb0\n     hci_cmd_sync_work+0x1b3/0x450\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     process_one_work+0x908/0x19c0\n     ? __pfx_process_one_work+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? lock_is_held_type+0x8f/0x100\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     worker_thread+0x65c/0xe40\n     ? __pfx_worker_thread+0x10/0x10\n     kthread+0x34f/0x460\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork+0x659/0x940\n     ? __pfx_ret_from_fork+0x10/0x10\n     ? srso_alias_return_thunk+0x5/0xfbef5\n     ? __switch_to+0x74f/0xf80\n     ? __pfx_kthread+0x10/0x10\n     ret_from_fork_asm+0x1a/0x30\n     \u003c/TASK\u003e\n\n    Allocated by task 511:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     __kasan_kmalloc+0xaa/0xb0\n     __kmalloc_cache_noprof+0x251/0x610\n     hci_bdaddr_list_add+0x179/0x390\n     hci_cc_le_add_to_accept_list+0x189/0x2d0\n     hci_cmd_complete_evt+0x373/0xab0\n     hci_event_packet+0x4e8/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    Freed by task 511:\n     kasan_save_stack+0x33/0x60\n     kasan_save_track+0x14/0x30\n     kasan_save_free_info+0x3b/0x60\n     __kasan_slab_free+0x5f/0x80\n     kfree+0x307/0x580\n     hci_bdaddr_list_clear+0x134/0x230\n     hci_cc_le_clear_accept_list+0x80/0x1f0\n     hci_cmd_complete_evt+0x373/0xab0\n     hci_event_packet+0x4e8/0xc70\n     hci_rx_work+0x367/0xf00\n     process_one_work+0x908/0x19c0\n     worker_thread+0x65c/0xe40\n     kthread+0x34f/0x460\n     ret_from_fork+0x659/0x940\n     ret_from_fork_asm+0x1a/0x30\n\n    The buggy address belongs to the object at ffff888105ee6c40\n                                                                which\n                                belongs to the cache kmalloc-32 of size 32\n    The buggy address is located 22 bytes inside of\n                                                                freed\n                                32-byte region [ffff888105ee6c40,\n                                ffff888105ee6c60)\n\n    The buggy address belongs to the physical page:\n        page: refcount:0 mapcount:0 mapping:0000000000000000\n    index:0xffff888105ee69c0 pfn:0x105ee6\n    flags: 0x200000000000200(workingset|node\u003d0|zone\u003d2)\n    page_type: f5(slab)\n        raw: 0200000000000200 ffff888100042780 ffffea0004187150\n    ffffea00042534d0\n        raw: ffff888105ee69c0 000000000040003f 00000000f5000000\n    0000000000000000\n    page dumped because: kasan: bad access detected\n\n    Memory state around the buggy address:\n     ffff888105ee6b00: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n     ffff888105ee6b80: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n    \u003effff888105ee6c00: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n                                                     ^\n     ffff888105ee6c80: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n     ffff888105ee6d00: fa fb fb fb fc fc fc fc fa fb fb fb fc fc fc fc\n    \u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nFixes: e8907f76544f (\"Bluetooth: hci_sync: Make use of hci_cmd_sync_queue set 3\")\nAssisted-by: LLM\nSigned-off-by: Cen Zhang \u003czzzccc427@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "855c9a54608f1e94f4c52afe3790def30534155a",
      "tree": "980a7b0470de17a243ad1d33cb5188af691fca90",
      "parents": [
        "d015faf684129a276f2137ad2e11c6c985294648"
      ],
      "author": {
        "name": "Chris Lu",
        "email": "chris.lu@mediatek.com",
        "time": "Thu Oct 22 11:21:50 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:02 2026 -0500"
      },
      "message": "Bluetooth: btmtk: derive the firmware ISO setting from MTK_ISO_THRESHOLD\n\nThe ISO data transfer size is spelled out twice: as a raw byte pair in the\nvendor command sent by btmtk_usb_isointf_init(), and as MTK_ISO_THRESHOLD\nfor the padding in btmtk_isopkt_pad(). Build the command payload from the\nmacro so the size is stated once, and update the setting for current\nMediaTek controllers.\n\nFixes: ceac1cb0259d (\"Bluetooth: btusb: mediatek: add ISO data transmission functions\")\nSigned-off-by: Chris Lu \u003cchris.lu@mediatek.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "d015faf684129a276f2137ad2e11c6c985294648",
      "tree": "86335d962b6cd83931b8fcf1e2c549e1444438c7",
      "parents": [
        "8524c3588fbb9d5c1b876e6f908c42926845650d"
      ],
      "author": {
        "name": "Chris Lu",
        "email": "chris.lu@mediatek.com",
        "time": "Thu Oct 22 11:21:49 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: btmtk: bound the ISO payload length by the controller\u0027s MTU\n\nbtmtk_recv_isopkt() bounds the Data_Total_Length reported by the\ncontroller with skb_tailroom(skb) \u003c hci_skb_expect(skb). That keeps the\nreassembly inside the skb, but it enforces no protocol limit: the head\nallocation is rounded up to the next kmalloc bucket and skb_tailroom()\nreports what the bucket can hold rather than what was requested, which is\nseveral hundred bytes more. An oversized length therefore passes, and the\nparser keeps pulling bytes out of the following transfers to fill it,\nswallowing the real ISO packets they carry until the frame is handed to\nhci_recv_frame().\n\nThe controller reports the largest ISO_Data_Packet_Length it will send in\nLE Read Buffer Size [v2], which hci_cc_le_read_buffer_size_v2() keeps in\nhdev-\u003eiso_mtu. Once that is available, bound the length by it and size the\nreceive skb to hold that much plus the 4-byte header. HCI_MAX_ISO_SIZE is\nkept only as a fallback for the window before the command completes.\n\nKeep the skb_tailroom() test as well, because a fragment started before\nhdev-\u003eiso_mtu was populated sits in an skb sized for the fallback.\n\nFixes: ceac1cb0259d (\"Bluetooth: btusb: mediatek: add ISO data transmission functions\")\nCo-developed-by: Hao Qin \u003chao.qin@mediatek.com\u003e\nSigned-off-by: Hao Qin \u003chao.qin@mediatek.com\u003e\nCo-developed-by: Wenlong Tian \u003cot_wenlong.tian@mediatek.com\u003e\nSigned-off-by: Wenlong Tian \u003cot_wenlong.tian@mediatek.com\u003e\nSigned-off-by: Chris Lu \u003cchris.lu@mediatek.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "8524c3588fbb9d5c1b876e6f908c42926845650d",
      "tree": "3d1730a304697f2b6cd17b39457152171ef8b950",
      "parents": [
        "e24bfbc5e20711dafa0cdc2b3325c69de1cff068"
      ],
      "author": {
        "name": "Chris Lu",
        "email": "chris.lu@mediatek.com",
        "time": "Thu Oct 22 11:21:48 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: btmtk: drop zero-length ISO packets from endpoint padding\n\nThe ISO interrupt IN endpoint delivers a fixed-size transfer that holds\none HCI ISO packet and zero-fills the remainder. That padding belongs to\nthe transfer rather than to the stream, so it has to be dropped instead of\nreported to the host.\n\nbtmtk_recv_isopkt() keeps parsing it: the zero bytes read as an ISO header\nwith handle 0 and a Data_Total_Length of zero, and each one is passed to\nhci_recv_frame() as a complete frame. A single transfer yields a long run\nof them, which is what fills the HCI log with malformed ISO packets, and\niso_recv() drops the SDU it is reassembling whenever handle 0 belongs to a\nlive CIS/BIS.\n\nA zero Data_Total_Length carries no ISO Data Load, so such a packet is\nnever part of the stream. Check for the zero-filled remainder before\nstarting to parse the next frame, rather than after assembling a 4-byte\nheader: a remainder shorter than HCI_ISO_HDR_SIZE would otherwise be held\nacross calls as a partial header, corrupting the next transfer\u0027s framing.\nThis also means a fully zero-filled remainder no longer costs an skb\nallocation that gets immediately freed. Reaching a zero Data_Total_Length\nany other way is then a genuine error, not padding.\n\nThis was observed on MT7925, but btmtk_recv_isopkt() is shared by every\nMediaTek USB controller that supports ISO data.\n\nFixes: ceac1cb0259d (\"Bluetooth: btusb: mediatek: add ISO data transmission functions\")\nCo-developed-by: Hao Qin \u003chao.qin@mediatek.com\u003e\nSigned-off-by: Hao Qin \u003chao.qin@mediatek.com\u003e\nCo-developed-by: Wenlong Tian \u003cot_wenlong.tian@mediatek.com\u003e\nSigned-off-by: Wenlong Tian \u003cot_wenlong.tian@mediatek.com\u003e\nSigned-off-by: Chris Lu \u003cchris.lu@mediatek.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "e24bfbc5e20711dafa0cdc2b3325c69de1cff068",
      "tree": "bffdf8bee0a4b7a76e8a2d89c0518431d845a748",
      "parents": [
        "5d005ded2cb14531c4d4ab5d02383407c75dbee6"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Oct 22 17:03:37 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Update the CIS host feature when enabling LE\n\nThe Connected Isochronous Stream (Host Support) feature bit is only set\nduring init, based on LE being enabled at that time. If LE is enabled\nafterwards without the init being repeated, as happens when the\ncontroller is still auto powered on after registration, the bit stays\ncleared and controllers enforcing it reject LE Create CIS with Command\nDisallowed.\n\nUpdate the bit whenever LE Host Supported is written, so it follows the\nLE state.\n\nFixes: 709788b154ca (\"Bluetooth: hci_core: Fix using {cis,bis}_capable for current settings\")\nAssisted-by: OpenCode:claude-opus-5.5\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "5d005ded2cb14531c4d4ab5d02383407c75dbee6",
      "tree": "5e6615723e1cccf129211a63e4400e351f28883a",
      "parents": [
        "1eebde8ecede18e351ccf438f17b53d3b62a75a9"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Wed Oct 21 13:49:35 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: L2CAP: Hold incoming data until encryption key size is known\n\nOnce encryption is enabled on an ACL link, the encryption key size is\nread from the controller, using hdev-\u003emin_enc_key_size in the meantime.\nData received before the reply is processed with that key size, so a\npeer starting SMP over BR/EDR right after encryption, which it may do,\ngets its Pairing Request rejected with \"Encryption Key Size\" whenever\nthe pending security level is FIPS, as that requires a 16 octet key:\n\n  \u003e HCI Event: Encryption Change (0x08) plen 4\n  \u003e ACL Data RX: Handle 1 flags 0x02 dlen 11\n        BR/EDR SMP: Pairing Request (0x01) len 6\n  @ MGMT Event: Authentication Failed (0x0011) plen 8\n        Status: Authentication Failed (0x05)\n  \u003c HCI Command: Read Encryption Key Size (0x05|0x0008) plen 2\n  \u003e HCI Event: Command Complete (0x0e) plen 7\n        Key size: 16\n  \u003c ACL Data TX: Handle 1 flags 0x00 dlen 6\n        BR/EDR SMP: Pairing Failed (0x05) len 1\n        Reason: Encryption key size (0x06)\n\nMark the connection with HCI_CONN_ENC_KEY_SIZE_PEND while the key size\nis read and hold incoming L2CAP data back in pending_rx meanwhile,\nprocessing it once the reply is handled.\n\nFound with mgmt-tester \"Pairing Acceptor - SMP over BR/EDR 2\" under User\nMode Linux time travel, where the emulated peer always replies before\nthe key size is read.\n\nFixes: e3f6a257a73d (\"Bluetooth: Use actual encryption key size for SMP over BR/EDR\")\nAssisted-by: OpenCode:claude-opus-5.5\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "1eebde8ecede18e351ccf438f17b53d3b62a75a9",
      "tree": "52813f5fbf3ac5f922e9109297bfebb790fe413d",
      "parents": [
        "f5cd268af1c6f87fb3847e98274e22b8c6324aa4"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Fri Oct 23 17:19:10 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Convert hci_conn flags to a bitmap\n\nstruct hci_conn stores its flags in a single unsigned long, but the\nHCI_CONN_* enum already has 33 entries (up to HCI_CONN_PA_SYNC_FAILED\n\u003d 32), so on 32-bit architectures set_bit()/test_bit() on the highest\nflags access memory past the flags field, aliasing the adjacent\nconn_reason field.\n\nFix this by declaring flags with DECLARE_BITMAP() sized by a new\n__HCI_CONN_NUM_FLAGS terminator so it can accommodate any number of\nflags.\n\nAssisted-by: OpenCode:claude-opus-5.5\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f5cd268af1c6f87fb3847e98274e22b8c6324aa4",
      "tree": "a39d16dec222229b1464b6a2391e9e0d6db255db",
      "parents": [
        "f92b7bca985205082c86140d0bd7c86c5be00efc"
      ],
      "author": {
        "name": "Kevin Dewald",
        "email": "kevin@simpleble.org",
        "time": "Fri Oct 23 12:14:37 2026 -0700"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_event: Clear explicit connect state on LE connection\n\nSince commit 6cd29ec6ae5e (\"Bluetooth: hci_sync: Wait for proper events\nwhen connecting LE\"), create_le_conn_complete() only runs once the LE\nConnection Complete event has been handled, and le_conn_complete_evt()\nhas already removed the connection parameters from pend_le_conns by\nthen. hci_connect_le_scan_cleanup() looks the parameters up in\npend_le_conns, so after a successful connection it no longer clears\nexplicit_connect, nor deletes the parameters that were only created for\nthe explicit connect.\n\nThe parameters of every device connected through an explicit connect,\nsuch as an L2CAP or ATT connect or MGMT Pair Device, are thus left with\nexplicit_connect set. MGMT Remove Device for all devices then keeps\nthem as HCI_AUTO_CONN_EXPLICIT instead of freeing them, and if the\ndevice was set to auto-connect and is disconnected, they also stay on\npend_le_conns: the kernel keeps scanning for the device and connects to\nit as soon as it advertises, although no one asked for it any more.\n\nDo the cleanup in le_conn_complete_evt() instead, where the explicit\nconnect request is fulfilled: clear explicit_connect, delete the\nparameters if they only existed for it, and put report parameters back\non pend_le_reports. Auto-connect parameters are added back to\npend_le_conns on disconnection, as before. Update the comment in\nhci_explicit_conn_params_set() that names hci_connect_le_scan_cleanup()\nas the only place deleting them.\n\nFixes: 6cd29ec6ae5e (\"Bluetooth: hci_sync: Wait for proper events when connecting LE\")\nAssisted-by: Claude:claude-opus-5.5\nSigned-off-by: Kevin Dewald \u003ckevin@simpleble.org\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f92b7bca985205082c86140d0bd7c86c5be00efc",
      "tree": "6ec160179a5193c90b13b5aa72d70ca9321ad69b",
      "parents": [
        "19b4e5701712f74d005cc66a36374559e8dfd281"
      ],
      "author": {
        "name": "Catherine L",
        "email": "catherine.l@intel.com",
        "time": "Fri Oct 23 11:30:26 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: btintel: fix buffer over-read in fw payload\n\nThe firmware decoder cast fw_ptr + frag_len to struct\nhci_command_hdr and read cmd-\u003eplen before confirming the\nheader and payload still fit in the remaining firmware\nbuffer.\n\nAdd explicit bounds checks before each dereference:\n1. Reject if the command header is not fully contained\n   in remain.\n2. Reject if the full command including payload exceeds\n   remain.\n3. Log the offending fragment length and remaining size\n   before returning -EINVAL.\n\nFixes: fbbe83c52bc0d (\"Bluetooth: btintel: Create common function for firmware download\")\nSigned-off-by: Catherine L \u003ccatherine.l@intel.com\u003e\nTested-by: Kiran K \u003ckiran.k@intel.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "19b4e5701712f74d005cc66a36374559e8dfd281",
      "tree": "54849b64d99d596757ea2a958c74af078ef7178f",
      "parents": [
        "56ed6b127a27c418dc2daa3fd076539d8fe69c4c"
      ],
      "author": {
        "name": "Akhil Arul",
        "email": "akhilarul324@gmail.com",
        "time": "Fri Oct 23 21:46:09 2026 +0530"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Fix queuing rx_work while workqueue is drained\n\nhci_recv_frame() drops a frame unless HCI_UP or HCI_INIT is set, but the\ncheck is not synchronized with hci_dev_close_sync().  A driver can pass\nthe check, then close clears HCI_UP, flushes rx_work and starts\ndrain_workqueue(), and the late queue_work() of rx_work hits the\ndraining workqueue:\n\n  workqueue: cannot queue hci_rx_work on wq hci0\n  WARNING: kernel/workqueue.c:2352 at __queue_work+0x2c0/0x780\n  Call Trace:\n   queue_work_on+0xb2/0xc0\n   hci_recv_frame+0x18f/0x330\n   vhci_write+0x174/0x240\n   vfs_write+0x271/0x680\n   ksys_write+0x7c/0x110\n\nSkipping the queue_work() while HCI_CMD_DRAIN_WORKQUEUE is set, as done\nfor tx_work, does not work for rx_work: the flag covers the whole close,\nand events still have to be received in that window, for the commands\nsent by hdev-\u003eshutdown() and for the reset done with\nHCI_QUIRK_RESET_ON_CLOSE.\n\nRun hci_recv_frame() under rcu_read_lock() and wait with\nsynchronize_rcu() once HCI_UP has been cleared, so that every caller\nwhich still saw HCI_UP has queued its work before the workqueue is\ndrained, and later callers drop the frame.\n\nHCI_INIT does not reopen that window.  Apart from the\nHCI_QUIRK_RESET_ON_CLOSE reset, which runs after drain_workqueue() has\nreturned, it is only set by hci_dev_init_sync() during open, and open\nand close are serialized by hci_req_sync_lock.  So once the grace period\nhas ended, nothing can pass the check and queue rx_work until the drain\nis over.\n\nTested in qemu with the syzbot C reproducer, one run per boot: the\nwarning showed up on 12 of 30 boots before and on none of 42 boots after.\nBringing a vhci controller up and down 50 times behaves the same with\nand without this change.\n\nFixes: 76727c02c1e1 (\"Bluetooth: Call drain_workqueue() before resetting state\")\nReported-by: syzbot+2344fb8002f3ef5b1712@syzkaller.appspotmail.com\nCloses: https://syzkaller.appspot.com/bug?extid\u003d2344fb8002f3ef5b1712\nSigned-off-by: Akhil Arul \u003cakhilarul324@gmail.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "56ed6b127a27c418dc2daa3fd076539d8fe69c4c",
      "tree": "3e85245256db11c4ca667e9b7177f4bfd8d60cd1",
      "parents": [
        "737139f4157d302292a6b937d96922879ecabfa3"
      ],
      "author": {
        "name": "Valentin Kindschi",
        "email": "valentin.kindschi@fiveco.ch",
        "time": "Tue Oct 20 12:51:50 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: pause advertising for the scan address update\n\nhci_active_scan_sync() programs a non-resolvable private address with LE\nSet Random Address on every active scan start.\n\nBLUETOOTH CORE SPECIFICATION Vol 4, Part E, 7.8.4 says the controller\nshall return Command Disallowed (0x0C) for that command while legacy\nadvertising or scanning is enabled. hci_pause_addr_resolution(), called\njust above, only stops advertising when LL privacy is in use, so on a\ncontroller without it the command is issued while advertising is still\non:\n\n  Bluetooth: hci0: Opcode 0x2005 failed: -16\n\nIt does not converge either. hdev-\u003erandom_addr is only set on a\nsuccessful command complete, so it stays BDADDR_ANY, and the deferral\nadded by commit c2994b008492 (\"Bluetooth: hci_sync: Fix not setting\nRandom Address when required\") requires it to be set. Unlike the\nresolvable address a few lines above, which is reused while rpa_valid(),\nthe non-resolvable one is regenerated and rewritten on every call, so a\ncontroller that refuses the write is asked again at the scan restart\nperiod of about 10 s, for as long as discovery keeps restarting.\nObserved on a BCM43455, which has no LL privacy and no extended\nadvertising, 190 rejections in one capture, every one retrying the same\naddress:\n\n  \u003c LE Set Random Address  Address: 02:16:91:90:F1:D4 (Non-Resolvable)\n  \u003e Command Complete       LE Set Random Address, Command Disallowed\n  \u003c LE Set Random Address  Address: 26:90:57:96:9A:3E (Non-Resolvable)\n  \u003e Command Complete       LE Set Random Address, Command Disallowed\n\nPause advertising for the address update, and resume it once the update\nis done and before the scan is started. The pause does not outlive the\nfunction: it is taken only when nothing else holds it, and every exit\nresumes advertising, which also releases the pause taken by\nhci_pause_addr_resolution(). A failed pause returns before marking\nanything paused, so the error path is a no-op.\n\nThe resume in the error path is no longer guarded by ll_privacy_capable().\nThat guard matched a pause taken only under LL privacy; the pause added\nhere is unconditional, and hci_resume_advertising_sync() returns early\nwhen nothing was paused.\n\nOne caveat this widens, raised on the previous posting. When\nHCI_ADVERTISING is set, hci_pause_advertising_sync() also clears\nHCI_DISCOVERABLE and HCI_LIMITED_DISCOVERABLE and zeroes discov_timeout,\nand hci_resume_advertising_sync() restores only HCI_ADVERTISING, so the\ndiscoverable state is lost. It reproduces today on an LL privacy\ncontroller through hci_pause_addr_resolution(); the unconditional pause\nmakes it reachable without LL privacy as well. hci_suspend_sync() also\npauses unconditionally, so a device that suspends loses the same state\non any controller today. That asymmetry is pre-existing and is left\nalone here rather than folded into a scan path fix.\n\nLegacy controllers have one random address register, shared by the\nscanner and the advertiser. Restoring the advertiser here can reprogram\nit when the advertiser is non-connectable, so the scan then uses that\naddress rather than the one generated for it. Both are non-resolvable\nand neither is linkable to the identity address. With privacy enabled\nboth roles already share one resolvable address the same way.\n\nWith the patch, on the same hardware:\n\n  \u003c LE Set Advertising Enable    Enable: 0x00              Success\n  \u003c LE Set Random Address                                  Success\n  \u003c LE Set Advertising Parameters                          Success\n  \u003c LE Set Advertising Enable    Enable: 0x01              Success\n  \u003c LE Set Scan Parameters                                 Success\n  \u003c LE Set Scan Enable           Enable: 0x01              Success\n\nThe address write is accepted, and advertising is restored before the\nscan is started.\n\nOver 119369 btmon records and about 12 minutes of the normal workload of\nthat device, alternating active and passive scanning with ten outgoing\nconnection attempts, every LE Set Random Address succeeded and there were\nno Command Disallowed responses of any opcode, against one per scan\nrestart before.\n\nPatch 1 is required: without it the resume added here returns -EPERM on\nthe controllers this fixes and leaves advertising disabled.\n\nFixes: 3c44a431d62b (\"Bluetooth: hci_sync: Resume adv with no RPA when active scan\")\nCc: stable@vger.kernel.org\nAssisted-by: Claude:claude-opus-5.5 btmon\nSigned-off-by: Valentin Kindschi \u003cvalentin.kindschi@fiveco.ch\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "737139f4157d302292a6b937d96922879ecabfa3",
      "tree": "77b08d2f5776b495da892ff1d32d70c7a1cd18fa",
      "parents": [
        "4335849380aa1081ee9a1c2b934cbdda0961fa57"
      ],
      "author": {
        "name": "Valentin Kindschi",
        "email": "valentin.kindschi@fiveco.ch",
        "time": "Tue Oct 20 12:51:49 2026 +0200"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:01 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: re-enable legacy advertising on resume\n\nhci_resume_advertising_sync() never re-enables advertising on a\ncontroller without extended advertising.\n\nIt restores HCI_ADVERTISING from advertising_old_state, then calls\nhci_schedule_adv_instance_sync(), which starts with:\n\n  if (hci_dev_test_flag(hdev, HCI_ADVERTISING) \u0026\u0026 !ext_adv_capable(hdev))\n          return -EPERM;\n\nThe flag it tests was set a few lines earlier by the resume itself, so\nthe call returns -EPERM without sending anything. The return value is\ndiscarded by every caller, so the failure is silent: advertising_paused\nis cleared, HCI_ADVERTISING is set, and the controller is not\nadvertising.\n\nObserved on a BCM43455 (no extended advertising) after an active scan:\nbtmon shows the pause disabling advertising and no re-enable in the ten\nseconds that follow, the device does not appear in another controller\u0027s\nscan, and btmgmt info still reports \"advertising\" in current settings.\n\nEnable instance 0x00 directly in that case, the way reenable_adv_sync()\nalready does for the same situation. Instances continue to go through\nhci_schedule_adv_instance_sync() so the software rotation loop is\nrearmed.\n\nThis affects every caller of hci_resume_advertising_sync(), not only the\nscan path: address resolution changes, accept list updates, discovery\nstop, suspend/resume and the end of an LE connection attempt all leave\nadvertising disabled on such a controller today.\n\nThe resume does nothing when the controller is already advertising, as\nit is after directed advertising was started for a peripheral\nconnection, so it does not replace that advertising.\n\nerr is initialised because the extended branch leaves it unset when\nadv_instances is empty and HCI_LE_ADV_0 is clear.\n\nFixes: ad383c2c65a5 (\"Bluetooth: hci_sync: Enable advertising when LL privacy is enabled\")\nCc: stable@vger.kernel.org\nAssisted-by: Claude:claude-opus-5.5 btmon\nSigned-off-by: Valentin Kindschi \u003cvalentin.kindschi@fiveco.ch\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "4335849380aa1081ee9a1c2b934cbdda0961fa57",
      "tree": "5f3a7a6668a5d5010a2111628e138b7b7b72805f",
      "parents": [
        "ae9c8df1ffb84560ac01cbdc26cfb19027f4d25f"
      ],
      "author": {
        "name": "Binbin Deng",
        "email": "18983559317@163.com",
        "time": "Mon Oct 19 18:56:24 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:00 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Initialize LTK before publication\n\nhci_add_ltk() publishes a newly allocated LTK on hdev-\u003elong_term_keys\nbefore initializing its address, type, value, authentication state,\nencryption size, EDIV, and random value.  hci_find_ltk() and the debugfs\nlong_term_keys_show() traverse this list under RCU and can therefore see\na zero or partially initialized key before those stores complete.\n\nThe race is reachable by racing an LTK addition with another CPU looking\nup or dumping long-term keys.  For example, userspace can issue\nMGMT_OP_LOAD_LONG_TERM_KEYS while another process reads the corresponding\ndebugfs file.\n\nInitialize all fields of a new LTK before list_add_rcu() makes it visible\nto RCU readers.  Existing LTKs remain published and continue to be updated\nin place.\n\nFound during a static-analysis-assisted audit: candidate sites were\nsurfaced by a Coccinelle rule, and the reader/writer paths were\nconfirmed by LLM-assisted (GLM-5.3) code inspection.  The issue was\nnot observed at runtime; it is identified by code inspection only.\n\nFixes: 970d0f1b2803 (\"Bluetooth: Convert LTK list to RCU\")\nAssisted-by: GLM-5.3 coccinelle\nSigned-off-by: Binbin Deng \u003c18983559317@163.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "ae9c8df1ffb84560ac01cbdc26cfb19027f4d25f",
      "tree": "263105a11f49348faac23d5a43e13de7fef14c37",
      "parents": [
        "f0cf5a24cefeb629876bd15d668ff062c8655e28"
      ],
      "author": {
        "name": "Binbin Deng",
        "email": "18983559317@163.com",
        "time": "Mon Oct 19 16:17:11 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:00 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Initialize link key before publication\n\nhci_add_link_key() allocates a new link key with kzalloc(), inserts it into\nhdev-\u003elink_keys with list_add_rcu(), and only then initializes its address,\nvalue, type, and PIN length.  RCU readers such as hci_find_link_key()\nand the debugfs link_keys_show() do not take hci_dev_lock, so they can\ntraverse the new entry during that initialization window and observe\na zero or partially initialized key.\n\nThis can be triggered by racing a link-key update with another CPU looking\nup or dumping keys.  In particular, userspace can issue\nMGMT_OP_LOAD_LINK_KEYS while another process reads the corresponding\ndebugfs file.\n\nComplete all fields of a newly allocated key before publishing it with\nlist_add_rcu().  Existing keys remain visible and keep their current\nin-place update behavior.\n\nFound during a static-analysis-assisted audit: candidate sites were\nsurfaced by a Coccinelle rule, and the reader/writer paths were\nconfirmed by LLM-assisted (GLM-5.3) code inspection.  The issue was\nnot observed at runtime; it is identified by code inspection only.\n\nFixes: 0378b5977013 (\"Bluetooth: Convert link keys list to use RCU\")\nSigned-off-by: Binbin Deng \u003c18983559317@163.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "f0cf5a24cefeb629876bd15d668ff062c8655e28",
      "tree": "e4e7b2aadbb59cf95025a75c6a14d8fe3ed3605e",
      "parents": [
        "fb1baa000d7a0b597ab9eb29b179b03e70e5f6ee"
      ],
      "author": {
        "name": "Binbin Deng",
        "email": "18983559317@163.com",
        "time": "Mon Oct 19 19:16:11 2026 +0800"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:00 2026 -0500"
      },
      "message": "Bluetooth: hci_core: Initialize IRK before publication\n\nhci_add_irk() initializes the identity address and address type of a newly\nallocated IRK, publishes it on hdev-\u003eidentity_resolving_keys, and only then\ninitializes its value and RPA.  RCU readers such as hci_find_irk_by_rpa()\nand the debugfs identity_resolving_keys_show() can traverse the new entry\nduring that window and see a zero or partially initialized IRK.\n\nThe race is reachable by racing an IRK addition with another CPU resolving\nor dumping IRKs.  In particular, userspace can issue MGMT_OP_LOAD_IRKS\nwhile another process reads the corresponding debugfs file or triggers RPA\nresolution.\n\nInitialize the IRK value and RPA before publishing a newly allocated IRK.\nExisting IRKs remain published and continue to be updated in place.\n\nFound during a static-analysis-assisted audit: candidate sites were\nsurfaced by a Coccinelle rule, and the reader/writer paths were\nconfirmed by LLM-assisted (GLM-5.3) code inspection.  The issue was\nnot observed at runtime; it is identified by code inspection only.\n\nFixes: adae20cb2d20 (\"Bluetooth: Convert IRK list to RCU\")\nAssisted-by: GLM-5.3 coccinelle\nSigned-off-by: Binbin Deng \u003c18983559317@163.com\u003e\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    },
    {
      "commit": "fb1baa000d7a0b597ab9eb29b179b03e70e5f6ee",
      "tree": "11b59404bc8b1177524bd207a2be0228260b07c9",
      "parents": [
        "c3e67bd82b9b9b1a5118f09a429ccefe2aab0741"
      ],
      "author": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Thu Oct 15 11:37:52 2026 -0400"
      },
      "committer": {
        "name": "Luiz Augusto von Dentz",
        "email": "luiz.von.dentz@intel.com",
        "time": "Mon Nov 02 17:09:00 2026 -0500"
      },
      "message": "Bluetooth: hci_sync: Fix invalid Supervision_Timeout in LE Set Default Rate\n\nThe LE Set Default Rate Parameters command is rejected with Invalid HCI\nCommand Parameters (0x12) because the Supervision_Timeout of 120 ms is\nexactly the minimum recommended by HOGP v1.2:\n\n  Greater than or equal to (1 + Peripheral Latency) x Subrate max x\n  Connection Interval max x 2\n\nBut the Core spec treats the equality as invalid:\n\nBLUETOOTH CORE SPECIFICATION Version 6.3 | Vol 4, Part E\n7.8.158. LE Set Default Rate Parameters command\n\n  If Connection_Interval_Max x Subrate_Max x (Max_Latency + 1) is\n  greater than or equal to Supervision_Timeout x 40, the Controller\n  shall return the error code Invalid HCI Command Parameters (0x12).\n\nWith the current values 0x78 x 4 x 1 \u003d 480 \u003e\u003d 0x0c x 40 \u003d 480.\n\nFix this by using 2 s as the default Supervision_Timeout, which is 10x\nlower than the 20 s used for non-SCI connections while still well above\nthe minimum required, and make sure it remains above the minimum in\ncase interval_max is raised to match the controller\u0027s minimum supported\nconnection interval.\n\nFixes: 2f8784cfe8a9 (\"Bluetooth: Add support for Shorter Connection Interval (SCI) feature\")\nAssisted-by: OpenCode:claude-opus-5.5\nSigned-off-by: Luiz Augusto von Dentz \u003cluiz.von.dentz@intel.com\u003e\n"
    }
  ],
  "next": "c3e67bd82b9b9b1a5118f09a429ccefe2aab0741"
}
