From: "Ivan T. Ivanov" <iivanov@suse.de>
To: gregkh@linuxfoundation.org
Cc: cve@kernel.org, linux-cve-announce@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: pwm: Fix double shift bug
Date: Wed, 5 Jun 2024 17:43:05 +0300 [thread overview]
Message-ID: <20240605144305.78002-1-iivanov@suse.de> (raw)
In-Reply-To: <2024052146-CVE-2023-52756-f694@gregkh>
Hi,
I could argue that this is not CVE at all. It changes just bit positions.
- PWMF_REQUESTED = 1 << 0,
- PWMF_EXPORTED = 1 << 1,
+ PWMF_REQUESTED = 0,
+ PWMF_EXPORTED = 1,
ie. before fix they 1 and 2 and after the fix 0, 1.
All call sites are using set/test_bit() on unsigned long flags.
Yes, double shift do not look right, but I don't see how
this could lead to malfunction, let alone a CVE.
Regards,
Ivan
next parent reply other threads:[~2024-06-05 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2024052146-CVE-2023-52756-f694@gregkh>
2024-06-05 14:43 ` Ivan T. Ivanov [this message]
2024-06-08 11:37 ` Greg KH
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=20240605144305.78002-1-iivanov@suse.de \
--to=iivanov@suse.de \
--cc=cve@kernel.org \
--cc=gregkh@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®