From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Subject: TESTING_NOT_REAL_ID_YET: USB: gadget: bRequestType is a bitfield, not a enum - test 4
Date: Mon, 12 Feb 2024 19:54:31 +0100 [thread overview]
Message-ID: <2024021231-outer-underdog-9f41@gregkh> (raw)
Description
===========
USB: gadget: bRequestType is a bitfield, not a enum
Szymon rightly pointed out that the previous check for the endpoint
direction in bRequestType was not looking at only the bit involved, but
rather the whole value. Normally this is ok, but for some request
types, bits other than bit 8 could be set and the check for the endpoint
length could not stall correctly.
Fix that up by only checking the single bit.
The Linux kernel CVE team has assigned TESTING_NOT_REAL_ID_YET to this issue.
Affected versions
=================
Issue introduced in 4.4.295 and fixed in 4.4.296
Issue introduced in 4.9.293 and fixed in 4.9.294
Issue introduced in 4.14.258 and fixed in 4.14.259
Issue introduced in 4.19.221 and fixed in 4.19.222
Issue introduced in 5.4.165 and fixed in 5.4.168
Issue introduced in 5.10.85 and fixed in 5.10.88
Issue introduced in 5.15.8 and fixed in 5.15.11
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 change to resolve this
issue can be found at:
https://git.kernel.org/stable/linux/c/f08adf5add9a071160c68bb2a61d697f39ab0758
reply other threads:[~2024-02-12 18: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=2024021231-outer-underdog-9f41@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@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.