From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-56590: Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet
Date: Fri, 27 Dec 2024 15:50:57 +0100 [thread overview]
Message-ID: <2024122759-CVE-2024-56590-d4ba@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_core: Fix not checking skb length on hci_acldata_packet
This fixes not checking if skb really contains an ACL header otherwise
the code may attempt to access some uninitilized/invalid memory past the
valid skb->data.
The Linux kernel CVE team has assigned CVE-2024-56590 to this issue.
Affected and fixed versions
===========================
Fixed in 5.15.174 with commit 219960a48771b35a3857a491b955c31d6c33d581
Fixed in 6.1.120 with commit 559b1c7ac2e212a23b3833d3baf3bd957771d02e
Fixed in 6.6.66 with commit 5e50d12cc6e95e1fde08f5db6992b616f714b0fb
Fixed in 6.12.5 with commit 93a6160dc198ffe5786da8bd8588cfd17f53b29a
Fixed in 6.13-rc1 with commit 3fe288a8214e7dd784d1f9b7c9e448244d316b47
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-2024-56590
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:
net/bluetooth/hci_core.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/219960a48771b35a3857a491b955c31d6c33d581
https://git.kernel.org/stable/c/559b1c7ac2e212a23b3833d3baf3bd957771d02e
https://git.kernel.org/stable/c/5e50d12cc6e95e1fde08f5db6992b616f714b0fb
https://git.kernel.org/stable/c/93a6160dc198ffe5786da8bd8588cfd17f53b29a
https://git.kernel.org/stable/c/3fe288a8214e7dd784d1f9b7c9e448244d316b47
reply other threads:[~2024-12-27 15:00 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=2024122759-CVE-2024-56590-d4ba@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@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.