From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-58016: safesetid: check size of policy writes
Date: Wed, 26 Feb 2025 18:11:10 -0800 [thread overview]
Message-ID: <2025022657-CVE-2024-58016-115b@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
safesetid: check size of policy writes
syzbot attempts to write a buffer with a large size to a sysfs entry
with writes handled by handle_policy_update(), triggering a warning
in kmalloc.
Check the size specified for write buffers before allocating.
[PM: subject tweak]
The Linux kernel CVE team has assigned CVE-2024-58016 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.129 with commit a0dec65f88c8d9290dfa1d2ca1e897abe54c5881
Fixed in 6.6.78 with commit 96fae5bd1589731592d30b3953a90a77ef3928a6
Fixed in 6.12.14 with commit 36b385d0f2b4c0bf41d491e19075ecd990d2bf94
Fixed in 6.13.3 with commit c71d35676d46090c891b6419f253fb92a1a9f4eb
Fixed in 6.14-rc1 with commit f09ff307c7299392f1c88f763299e24bc99811c7
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-58016
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:
security/safesetid/securityfs.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/a0dec65f88c8d9290dfa1d2ca1e897abe54c5881
https://git.kernel.org/stable/c/96fae5bd1589731592d30b3953a90a77ef3928a6
https://git.kernel.org/stable/c/36b385d0f2b4c0bf41d491e19075ecd990d2bf94
https://git.kernel.org/stable/c/c71d35676d46090c891b6419f253fb92a1a9f4eb
https://git.kernel.org/stable/c/f09ff307c7299392f1c88f763299e24bc99811c7
reply other threads:[~2025-02-27 2:13 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=2025022657-CVE-2024-58016-115b@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.