Unspecified impact via stale blocking notifier registration
Published Aug 15, 2026 · Updated Aug 15, 2026
Improper cleanup in Linux 5.14 allows attackers to cause unspecified impact via failed Sparx5 workqueue allocation. sparx5_register_notifier_blocks() registers the switchdev blocking notifier before allocating its ordered workqueue, but the failure path omits that notifier's unregistration. Public sources identify neither an attacker-controlled way to force allocation failure nor the consequence of invoking the stale notifier after initialization unwinds.
Summary
What happened
Improper cleanup in Linux 5.14 allows attackers to cause unspecified impact via failed Sparx5 workqueue allocation. sparx5_register_notifier_blocks() registers the switchdev blocking notifier before allocating its ordered workqueue, but the failure path omits that notifier's unregistration. Public sources identify neither an attacker-controlled way to force allocation failure nor the consequence of invoking the stale notifier after initialization unwinds.
The record
- CVE
- CVE-2026-72109
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 15, 2026CVE publishedPublication date reported by the CVE source.
- Aug 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.14
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <17f113e7b622dc850992ade540181717de6a8561
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <483be61b4a9a6df3b7cb277e8f189e082dee4cb8
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <8a3c44a003176282ee4306b7c96e5a536c6f0707
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <cf419c869e0d03aad4b6f4ecf0a813851930dfe7
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <d6084c47389fd6978a5d66b0d58206a548c792a9
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <e5afc6d3fabdf1f605d63c4b34a3df6c359e81f3
- Affected versionversion=d6fce5141929697a27f029c633433d487f6f62cb <fbc65b17508ed5464b7106e7fa5f15251ca1b603
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo