From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-53203: usb: typec: fix potential array underflow in ucsi_ccg_sync_control()
Date: Fri, 27 Dec 2024 14:52:49 +0100 [thread overview]
Message-ID: <2024122727-CVE-2024-53203-80fc@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
usb: typec: fix potential array underflow in ucsi_ccg_sync_control()
The "command" variable can be controlled by the user via debugfs. The
worry is that if con_index is zero then "&uc->ucsi->connector[con_index
- 1]" would be an array underflow.
The Linux kernel CVE team has assigned CVE-2024-53203 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.6 with commit 170a6726d0e266f2c8f306e3d61715c32f4ee41e and fixed in 6.11.11 with commit ef92cd55289a282910575c5b9d87f646f2d39b38
Issue introduced in 5.6 with commit 170a6726d0e266f2c8f306e3d61715c32f4ee41e and fixed in 6.12.2 with commit 56971710cd541f2f05160a84b3183477d34a1be9
Issue introduced in 5.6 with commit 170a6726d0e266f2c8f306e3d61715c32f4ee41e and fixed in 6.13-rc1 with commit e56aac6e5a25630645607b6856d4b2a17b2311a5
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-53203
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/usb/typec/ucsi/ucsi_ccg.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/ef92cd55289a282910575c5b9d87f646f2d39b38
https://git.kernel.org/stable/c/56971710cd541f2f05160a84b3183477d34a1be9
https://git.kernel.org/stable/c/e56aac6e5a25630645607b6856d4b2a17b2311a5
reply other threads:[~2024-12-27 13:54 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=2024122727-CVE-2024-53203-80fc@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.