From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-26824: crypto: algif_hash - Remove bogus SGL free on zero-length error path
Date: Wed, 17 Apr 2024 11:44:07 +0200 [thread overview]
Message-ID: <2024041702-CVE-2024-26824-98e1@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
crypto: algif_hash - Remove bogus SGL free on zero-length error path
When a zero-length message is hashed by algif_hash, and an error
is triggered, it tries to free an SG list that was never allocated
in the first place. Fix this by not freeing the SG list on the
zero-length error path.
The Linux kernel CVE team has assigned CVE-2024-26824 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.5 with commit b6d972f68983 and fixed in 6.6.18 with commit 9c82920359b7
Issue introduced in 6.5 with commit b6d972f68983 and fixed in 6.7.6 with commit 775f3c1882a4
Issue introduced in 6.5 with commit b6d972f68983 and fixed in 6.8 with commit 24c890dd712f
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-26824
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:
crypto/algif_hash.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/9c82920359b7c1eddaf72069bcfe0ffddf088cd0
https://git.kernel.org/stable/c/775f3c1882a493168e08fdb8cde0865c8f3a8a29
https://git.kernel.org/stable/c/24c890dd712f6345e382256cae8c97abb0406b70
reply other threads:[~2024-04-17 9:44 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=2024041702-CVE-2024-26824-98e1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).