From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2025-21773: can: etas_es58x: fix potential NULL pointer dereference on udev->serial
Date: Wed, 26 Feb 2025 18:17:29 -0800 [thread overview]
Message-ID: <2025022606-CVE-2025-21773-2ee7@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
can: etas_es58x: fix potential NULL pointer dereference on udev->serial
The driver assumed that es58x_dev->udev->serial could never be NULL.
While this is true on commercially available devices, an attacker
could spoof the device identity providing a NULL USB serial number.
That would trigger a NULL pointer dereference.
Add a check on es58x_dev->udev->serial before accessing it.
The Linux kernel CVE team has assigned CVE-2025-21773 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.2 with commit 9f06631c3f1f0f298536443df85a6837ba4c5f5c and fixed in 6.6.79 with commit 1590667a60753ee5a54871f2840ceefd4a7831fa
Issue introduced in 6.2 with commit 9f06631c3f1f0f298536443df85a6837ba4c5f5c and fixed in 6.12.16 with commit 722e8e1219c8b6ac2865011fe339315d6a8d0721
Issue introduced in 6.2 with commit 9f06631c3f1f0f298536443df85a6837ba4c5f5c and fixed in 6.13.4 with commit 5059ea98d7bc133903d3e47ab36df6ed11d0c95f
Issue introduced in 6.2 with commit 9f06631c3f1f0f298536443df85a6837ba4c5f5c and fixed in 6.14-rc3 with commit a1ad2109ce41c9e3912dadd07ad8a9c640064ffb
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-21773
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:
drivers/net/can/usb/etas_es58x/es58x_devlink.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/1590667a60753ee5a54871f2840ceefd4a7831fa
https://git.kernel.org/stable/c/722e8e1219c8b6ac2865011fe339315d6a8d0721
https://git.kernel.org/stable/c/5059ea98d7bc133903d3e47ab36df6ed11d0c95f
https://git.kernel.org/stable/c/a1ad2109ce41c9e3912dadd07ad8a9c640064ffb
reply other threads:[~2025-02-27 2: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=2025022606-CVE-2025-21773-2ee7@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.