CVE-2026-68301

net: hsr: fix memory leak on slave unregistration by removing synced VLANs

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: net: hsr: fix memory leak on slave unregistration by removing synced VLANs When an HSR master device is brought UP, it auto-adds VLAN 0 via vlan_vid0_add(), which propagates VID 0 to its slave devices (slave A and B). If a slave device is later unregistered while HSR is active (e.g., during netns cleanup or interface destruction), hsr_del_port() is called to detach the slave port from the HSR master. However, hsr_del_port() currently does not delete the VLAN IDs that were synced to the slave device by HSR. As a result, the slave device retains a refcount on VID 0 (and any other synced VLANs). When the slave device is destroyed, its vlan_info / vlan_vid_info structure remains allocated, leading to a memory leak. Fix this by calling vlan_vids_del_by_dev(port->dev, master->dev) in hsr_del_port() before unlinking slave A or slave B ports, matching the propagation logic in hsr_ndo_vlan_rx_add_vid() / hsr_ndo_vlan_rx_kill_vid() and the cleanup behavior in bonding and team drivers.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.194 ≤ v < 5.15.2166.1.153 ≤ v < 6.1.1836.12.48 ≤ v < 6.12.1016.13 ≤ v < 6.18.426.13 ≤ v < 7.1.66.13 ≤ v < 7.26.6.107 ≤ v < 6.6.1481100242709d5644856131a9dd25d32672ebe73571a8a63a5305e95519de6f941922dfcd8179f82e55.15.1946.1.1536.12.486.136.6.10772dbae1f2f2159395089405c6c54632f2613f1bea2accc07bdcfb0c7ab2cacdca6a1fe8267816efac707d2c5541d2bb94131968ad5dfeb06427a1dba
Vendor states this is fixed in 21d48408479a17eb65568a765930adea37e4d804 (fixed)
Vendor states this is fixed in 79ff0547676acdeceda445c3fce4071b0a887b70 (fixed)
Vendor states this is fixed in ae995b8002d3af134560a706c0e111a89e26317c (fixed)
Vendor states this is fixed in b5ded444621b6180df9f3d4e07045fc1fc1e8cd9 (fixed)
Vendor states this is fixed in ccc822e9e4f09a6c2ca73ad5334570441947f94f (fixed)
Vendor states this is fixed in dcf15eaf5641812f1cfc5e96537380132a7da89d (fixed)
Vendor states this is fixed in f72c312af6c7897ab0f8a2b5a63f917a207a4143 (fixed)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card