CVE-2026-68301: net: hsr: fix memory leak on slave unregistration by removing synced VLANs
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 21d48408479a17eb65568a765930adea37e4d804, 5.15.216, 6.1.183; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 21d48408479a17eb65568a765930adea37e4d804, 5.15.216, 6.1.183; azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 6.6.150.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 10, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.13affected
- 1100242709d5644856131a9dd25d32672ebe7357 and later · before ccc822e9e4f09a6c2ca73ad5334570441947f94faffected · git
- a2accc07bdcfb0c7ab2cacdca6a1fe8267816efa and later · before 79ff0547676acdeceda445c3fce4071b0a887b70affected · git
- 72dbae1f2f2159395089405c6c54632f2613f1be and later · before f72c312af6c7897ab0f8a2b5a63f917a207a4143affected · git
- c707d2c5541d2bb94131968ad5dfeb06427a1dba and later · before 21d48408479a17eb65568a765930adea37e4d804affected · git
- 1a8a63a5305e95519de6f941922dfcd8179f82e5 and later · before b5ded444621b6180df9f3d4e07045fc1fc1e8cd9affected · git
- 1a8a63a5305e95519de6f941922dfcd8179f82e5 and later · before ae995b8002d3af134560a706c0e111a89e26317caffected · git
- 1a8a63a5305e95519de6f941922dfcd8179f82e5 and later · before dcf15eaf5641812f1cfc5e96537380132a7da89daffected · git
- 5.15.194 and later · before 5.15.216affected · semver
- 6.1.153 and later · before 6.1.183affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-1 |
| Debian:14 | linux | before 7.1.6-1 | 7.1.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-68299Aug 10, 2026 · vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets30Monitor
- ← EarlierCVE-2026-68300Aug 10, 2026 · sctp: auth: verify auth requirement when auth_chunk is NULL39Monitor
- Later →CVE-2026-68303Aug 10, 2026 · drm/vc4: hvs/v3d: Fix null dereference in unbind0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 21d48408479a17eb65568a765930adea37e4d804 | Vendor (CNA) |
| Linux Linux | 5.15.216 | Vendor (CNA) |
| Linux Linux | 6.1.183 | Vendor (CNA) |
| Linux Linux | 6.12.101 | Vendor (CNA) |
| Linux Linux | 6.6.148 | Vendor (CNA) |
| Linux Linux | 79ff0547676acdeceda445c3fce4071b0a887b70 | Vendor (CNA) |
| Linux Linux | ae995b8002d3af134560a706c0e111a89e26317c | Vendor (CNA) |
| Linux Linux | b5ded444621b6180df9f3d4e07045fc1fc1e8cd9 | Vendor (CNA) |
| Linux Linux | ccc822e9e4f09a6c2ca73ad5334570441947f94f | Vendor (CNA) |
| Linux Linux | dcf15eaf5641812f1cfc5e96537380132a7da89d | Vendor (CNA) |
| Linux Linux | f72c312af6c7897ab0f8a2b5a63f917a207a4143 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/79ff0547676acdeceda445c3fce4071b0a887b70
- git.kernel.org/stable/c/ae995b8002d3af134560a706c0e111a89e26317c
- git.kernel.org/stable/c/b5ded444621b6180df9f3d4e07045fc1fc1e8cd9
- git.kernel.org/stable/c/ccc822e9e4f09a6c2ca73ad5334570441947f94f
- git.kernel.org/stable/c/dcf15eaf5641812f1cfc5e96537380132a7da89d
- git.kernel.org/stable/c/f72c312af6c7897ab0f8a2b5a63f917a207a4143
Vendor advisories and official records. Exploit/PoC links are deliberately left out.