From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43462: net: spacemit: Fix error handling in emac_tx_mem_map()
Date: Fri, 8 May 2026 16:23:11 +0200 [thread overview]
Message-ID: <2026050801-CVE-2026-43462-aca6@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: spacemit: Fix error handling in emac_tx_mem_map()
The DMA mappings were leaked on mapping error. Free them with the
existing emac_free_tx_buf() function.
The Linux kernel CVE team has assigned CVE-2026-43462 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.18 with commit bfec6d7f2001c7470c3cd261ae65a3ba8737f226 and fixed in 6.18.19 with commit c34ebd7b24ea70be3c6fdb6936f79f593f37df60
Issue introduced in 6.18 with commit bfec6d7f2001c7470c3cd261ae65a3ba8737f226 and fixed in 6.19.9 with commit edeaba385318f60ec1b32470da4d5eb800294d16
Issue introduced in 6.18 with commit bfec6d7f2001c7470c3cd261ae65a3ba8737f226 and fixed in 7.0 with commit 86292155bea578ebab0ca3b65d4d87ecd8a0e9ea
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-2026-43462
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/ethernet/spacemit/k1_emac.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/c34ebd7b24ea70be3c6fdb6936f79f593f37df60
https://git.kernel.org/stable/c/edeaba385318f60ec1b32470da4d5eb800294d16
https://git.kernel.org/stable/c/86292155bea578ebab0ca3b65d4d87ecd8a0e9ea
reply other threads:[~2026-05-08 14:26 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=2026050801-CVE-2026-43462-aca6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@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