CVE-2026-100071
What it is
In the Linux kernel, the following vulnerability has been resolved: net: hsr: free learned nodes on device setup failure hsr_dev_finalize() can fail after a lower-device RX handler has already been registered (slave A is added before the failable slave B and interlink adds). RX handlers run in softirq regardless of the master's state, so frames received in that window can learn dynamic nodes into node_db, and the error unwind never releases them. Free both owned dynamic databases in the unwind, mirroring hsr_dellink(). proxy_node_db is provably empty on every current error exit (only interlink RX feeds it, and the interlink add is the last failable step) and is freed for symmetry. The order is safe: hsr_del_port() unregisters each RX handler with synchronize_net() before hsr_del_nodes() runs, which removes remaining entries with list_del_rcu() and defers their release with call_rcu() for readers already under RCU.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 6.1.188
- Linux Kernel < 6.6.157
- Linux Kernel < 6.12.110
- Linux Kernel < 6.18.52
- Linux Kernel < 7.2.6
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-100071.md and follow it. Check whether this project is affected by CVE-2026-100071. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/0a340ffd96943a49a78e367efac9517ca767d99b
- https://git.kernel.org/stable/c/49b01f2939abc676a6f9a118f07a10110ee5f683
- https://git.kernel.org/stable/c/65702339b3e9fd792f65d4b740928798194d86ce
- https://git.kernel.org/stable/c/7f16289b91eb316f170a6bd22d32e6c632f6a5b6
- https://git.kernel.org/stable/c/e691eee886871b933d772ffc76d66c80b4c0a25e
- https://git.kernel.org/stable/c/f7289e3492f2694dccd3d79287e0e31879b58650
References
- https://git.kernel.org/stable/c/0a340ffd96943a49a78e367efac9517ca767d99b
- https://git.kernel.org/stable/c/49b01f2939abc676a6f9a118f07a10110ee5f683
- https://git.kernel.org/stable/c/65702339b3e9fd792f65d4b740928798194d86ce
- https://git.kernel.org/stable/c/7f16289b91eb316f170a6bd22d32e6c632f6a5b6
- https://git.kernel.org/stable/c/e691eee886871b933d772ffc76d66c80b4c0a25e
- https://git.kernel.org/stable/c/f7289e3492f2694dccd3d79287e0e31879b58650