net: ixp4xx_hss: fix duplicate HDLC netdev allocation
Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.
cve-program · CVE-2026-72058
PublishedIn 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-72058 · CVE overview and exploitation status
cve-program · CVE-2026-72058
- https://git.kernel.org/stable/c/77d925b948ee594a79afe66f85bb94b67940140b
- 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
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.