From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-98633: Bluetooth: btnxpuart: Fix skb leak in nxp_process_fw_dump()
Date: Sun, 18 Oct 2026 17:18:17 +0200 [thread overview]
Message-ID: <2026101844-CVE-2026-98633-da37@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: btnxpuart: Fix skb leak in nxp_process_fw_dump()
When CONFIG_DEV_COREDUMP=n, hci_devcd_append() returns -EOPNOTSUPP
without freeing its skb argument. This leaks the cloned skb and also
prevents nxp_set_ind_reset() from being called to perform recovery.
Fix by guarding the hci_devcd_append(hdev, skb_clone(skb, GFP_ATOMIC))
call with IS_ENABLED(CONFIG_DEV_COREDUMP).
The Linux kernel CVE team has assigned CVE-2026-98633 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.15 with commit 998e447f443f138c90faa6ff3845082af419070e and fixed in 6.18.55 with commit 8a36598050cd1e5abb1d5ed42cc224cfcb538c4f
Issue introduced in 6.15 with commit 998e447f443f138c90faa6ff3845082af419070e and fixed in 7.2.9 with commit edcb84ee607a9ddfc6f2771a7f399115f0b0f19d
Issue introduced in 6.15 with commit 998e447f443f138c90faa6ff3845082af419070e and fixed in 7.3-rc5 with commit f2bbb36426581045a8bf7793da5419b9375e4348
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-98633
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/bluetooth/btnxpuart.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8a36598050cd1e5abb1d5ed42cc224cfcb538c4f
https://git.kernel.org/stable/c/edcb84ee607a9ddfc6f2771a7f399115f0b0f19d
https://git.kernel.org/stable/c/f2bbb36426581045a8bf7793da5419b9375e4348
reply other threads:[~2026-10-18 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026101844-CVE-2026-98633-da37@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.