From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-72058: net: ixp4xx_hss: fix duplicate HDLC netdev allocation
Date: Sat, 15 Aug 2026 15:02:17 +0900 [thread overview]
Message-ID: <2026081516-CVE-2026-72058-c750@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: ixp4xx_hss: fix duplicate HDLC netdev allocation
ixp4xx_hss_probe() allocates two HDLC netdevs. The first one is stored
in ndev, initialized, and registered with register_hdlc_device(). The
second one is stored in port->netdev and later used by the remove path
for unregister_hdlc_device() and free_netdev().
This means that the registered netdev is not the same object that is
unregistered and freed on remove. It also leaks the first allocation if
the second alloc_hdlcdev() call fails, and the first allocation is not
checked before ndev is used.
Older code allocated the HDLC netdev only once and stored the same object
in both the local variable and port->netdev. The buggy conversion split
this into two alloc_hdlcdev() calls. A later rename changed the local
variable name to ndev, but the underlying mismatch remained.
Fix this by allocating the HDLC netdev only once and assigning the same
object to port->netdev.
The Linux kernel CVE team has assigned CVE-2026-72058 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 6.1.178 with commit 8f4c3c384092becbf4835a3f8ed8a3df1f544578
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 6.6.145 with commit fd0b939ebd1eee29945a539c5ed65c35dddac8d6
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 6.12.97 with commit ffba16e6f55948d94b7f16aa113d587c1c4c0643
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 6.18.40 with commit 3f85fcd520aa703824b1958f35169925ddae2558
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 7.1.5 with commit 91850f582783098415a334f8bd0a84c87ff15a8c
Issue introduced in 5.14 with commit 99ebe65eb9c0ada015931d239d9f2d1dc8897fee and fixed in 7.2-rc1 with commit db818b0e8af7bac16860116a19c341a63d6677b4
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-72058
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/wan/ixp4xx_hss.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/8f4c3c384092becbf4835a3f8ed8a3df1f544578
https://git.kernel.org/stable/c/fd0b939ebd1eee29945a539c5ed65c35dddac8d6
https://git.kernel.org/stable/c/ffba16e6f55948d94b7f16aa113d587c1c4c0643
https://git.kernel.org/stable/c/3f85fcd520aa703824b1958f35169925ddae2558
https://git.kernel.org/stable/c/91850f582783098415a334f8bd0a84c87ff15a8c
https://git.kernel.org/stable/c/db818b0e8af7bac16860116a19c341a63d6677b4
reply other threads:[~2026-08-15 6:09 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=2026081516-CVE-2026-72058-c750@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 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.