CVE-2026-74283

tipc: require net admin for TIPCv2 netlink mutators

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:57 AM UTC
Updated: October 16, 2026 at 07:17 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
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: tipc: require net admin for TIPCv2 netlink mutators TIPCv2 registers mutating generic-netlink operations without admin permission flags. Generic netlink only checks CAP_NET_ADMIN when an operation sets GENL_ADMIN_PERM or GENL_UNS_ADMIN_PERM, so a local unprivileged process can currently change TIPC state through commands such as TIPC_NL_NET_SET, TIPC_NL_KEY_SET, TIPC_NL_KEY_FLUSH, and bearer enable/disable. The legacy TIPC netlink API already checks netlink_net_capable(..., CAP_NET_ADMIN) for administrative commands. Give the TIPCv2 mutators the equivalent generic-netlink gate. Use GENL_UNS_ADMIN_PERM, which maps to the same namespace-aware CAP_NET_ADMIN check that netlink_net_capable() performs, so the behaviour matches the legacy path and keeps working for CAP_NET_ADMIN holders in a non-initial user namespace (containers). A QEMU/KASAN repro run as uid/gid 65534 with zero effective capabilities previously succeeded in changing the network id and node identity, setting and flushing key material, and enabling/disabling a UDP bearer. With this patch applied the same operations fail with -EPERM.

Affected

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

0655f6a8635b1b66f2434d5556b1044c14b1ccaf3.19655f6a8635b1b66f2434d5556b1044c14b1ccaf
Vendor states this is fixed in 52864c6c13dcc292481eabfeb3c31a86c3ec06f2 (fixed)
Vendor states this is fixed in 56f0a2e0a1d004e025cd031c3a801ab73959269f (fixed)
Vendor states this is fixed in 86b0c540e2ea397cde021eecd24145f7c16a3d4e (fixed)
Vendor states this is fixed in 9b937de4b3ded62a24da6e8d9d623cdb2748fa74 (fixed)
Vendor states this is fixed in b06fb5f78a9af0929aaa47c92d0b7bca0617fb25 (fixed)
Vendor states this is fixed in c9668a4adb2264625daeeabc7466b783badd4614 (fixed)
Vendor states this is fixed in cebaefe1aceb650d5c99a4c0e1a4dde09e211818 (fixed)
Vendor states this is fixed in e87dcc1a644d087de0bb6c94c6dd28c29b89597f (fixed)
Vendor states this is fixed in 3.19 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (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.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

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