Unauthorized TIPC state changes via ungated mutators
Published Aug 15, 2026 · Updated Aug 15, 2026
Improper authorization in the Linux kernel TIPC component allows local users to alter TIPC state through TIPCv2 generic netlink. TIPCv2 mutating operations omit generic-netlink admin-permission flags, so the kernel performs no CAP_NET_ADMIN check before accepting network, key, and bearer changes. Any local process with no effective capabilities can change node identity, key material, or UDP bearer state, disrupting or compromising TIPC communications.
Summary
What happened
Improper authorization in the Linux kernel TIPC component allows local users to alter TIPC state through TIPCv2 generic netlink. TIPCv2 mutating operations omit generic-netlink admin-permission flags, so the kernel performs no CAP_NET_ADMIN check before accepting network, key, and bearer changes. Any local process with no effective capabilities can change node identity, key material, or UDP bearer state, disrupting or compromising TIPC communications.
The record
- CVE
- CVE-2026-74283
- Published
- Aug 15, 2026
- Updated
- Aug 15, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-266
- Attack vector
- local
- Privileges
- authenticated
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=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <52864c6c13dcc292481eabfeb3c31a86c3ec06f2
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <56f0a2e0a1d004e025cd031c3a801ab73959269f
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <86b0c540e2ea397cde021eecd24145f7c16a3d4e
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <9b937de4b3ded62a24da6e8d9d623cdb2748fa74
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <b06fb5f78a9af0929aaa47c92d0b7bca0617fb25
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <c9668a4adb2264625daeeabc7466b783badd4614
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <cebaefe1aceb650d5c99a4c0e1a4dde09e211818
- Affected versionversion=0655f6a8635b1b66f2434d5556b1044c14b1ccaf <e87dcc1a644d087de0bb6c94c6dd28c29b89597f
- Affected versionversion=3.19
What conditions does exploitation require?
What is affected?
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
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