CVE-2026-63858

netfilter: nf_tables: add hook transactions for device deletions

HIGH
7.8
CVSS Score
Published: July 19, 2026 at 02:04 PM UTC
Updated: October 26, 2026 at 04:27 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.1%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: add hook transactions for device deletions Restore the flag that indicates that the hook is going away, ie. NFT_HOOK_REMOVE, but add a new transaction object to track deletion of hooks without altering the basechain/flowtable hook_list during the preparation phase. The existing approach that moves the hook from the basechain/flowtable hook_list to transaction hook_list breaks netlink dump path readers of this RCU-protected list. It should be possible use an array for nft_trans_hook to store the deleted hooks to compact the representation but I am not expecting many hook object, specially now that wildcard support for devices is in place. Note that the nft_trans_chain_hooks() list contains a list of struct nft_trans_hook objects for DELCHAIN and DELFLOWTABLE commands, while this list stores struct nft_hook objects for NEWCHAIN and NEWFLOWTABLE. Note that new commands can be updated to use nft_trans_hook for consistency. This patch also adapts the event notification path to deal with the list of hook transactions.

Affected

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

5.10.122 ≤ v < 5.115.15.47 ≤ v < 5.165.17.15 ≤ v < 5.185.18.4 ≤ v < 5.195.19.1 ≤ v < 6.18.576.19 ≤ v < 7.0.105.10.1225.15.475.17.155.18.45.1962d91062058b42bf70b2c3446aec397bb0ce15ee7.17a248f9c74f9f62799718c12efd9e9e391d60b6f99180dec5ae582227219d1fdd0dd5ccf53ec7491b6d9014a3335194590abdd2a2471ef5147a67645f275989ad04159dbfc62cefb65ba9c5ba1d7c34f
Vendor states this is fixed in 10f79dbd7719d1da9f5884d13060322d8729f091 (fixed)
Vendor states this is fixed in 4e69bfb32b2db323d9205fdb30e284481b37817c (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.18, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.18.57 (unaffected)
Vendor states this is fixed in 7.0.10 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

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

StatusANALYZED
CWE
CWE-362

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