From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-22017: devlink: fix xa_alloc_cyclic() error handling
Date: Tue, 8 Apr 2025 10:16:51 +0200 [thread overview]
Message-ID: <2025040844-CVE-2025-22017-a66e@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
devlink: fix xa_alloc_cyclic() error handling
In case of returning 1 from xa_alloc_cyclic() (wrapping) ERR_PTR(1) will
be returned, which will cause IS_ERR() to be false. Which can lead to
dereference not allocated pointer (rel).
Fix it by checking if err is lower than zero.
This wasn't found in real usecase, only noticed. Credit to Pierre.
The Linux kernel CVE team has assigned CVE-2025-22017 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit c137743bce02b18c1537d4681aa515f7b80bf0a8 and fixed in 6.12.21 with commit f8aaa38cfaf6f20afa4db36b6529032fb69165dc
Issue introduced in 6.7 with commit c137743bce02b18c1537d4681aa515f7b80bf0a8 and fixed in 6.13.9 with commit 466132f6d28a7e47a82501fe1c46b8f90487412e
Issue introduced in 6.7 with commit c137743bce02b18c1537d4681aa515f7b80bf0a8 and fixed in 6.14 with commit f3b97b7d4bf316c3991e5634c9f4847c2df35478
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-2025-22017
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:
net/devlink/core.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/f8aaa38cfaf6f20afa4db36b6529032fb69165dc
https://git.kernel.org/stable/c/466132f6d28a7e47a82501fe1c46b8f90487412e
https://git.kernel.org/stable/c/f3b97b7d4bf316c3991e5634c9f4847c2df35478
reply other threads:[~2025-04-08 8:18 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=2025040844-CVE-2025-22017-a66e@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.