CVE-2026-22985: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations
In the Linux kernel, the following vulnerability has been resolved:
idpf: Fix RSS LUT NULL pointer crash on early ethtool operations
The RSS LUT is not initialized until the interface comes up, causing
the following NULL pointer crash when ethtool operations like rxhash on/off
are performed before the interface is brought up for the first time.
Move RSS LUT initialization from ndo_open to vport creation to ensure LUT
is always available. This enables RSS configuration via ethtool before
bringing the interface up. Simplify LUT management by maintaining all
changes in the driver's soft copy and programming zeros to the indirection
table when rxhash is disabled. Defer HW programming until the interface
comes up if it is down during rxhash and LUT configuration changes.
Steps to reproduce:
** Load idpf driver; interfaces will be created
modprobe idpf
** Before bringing the interfaces up, turn rxhash off
ethtool -K eth2 rxhash off
[89408.371875] BUG: kernel NULL pointer dereference, address: 0000000000000000
[89408.371908] #PF: supervisor read access in kernel mode
[89408.371924] #PF: error_code(0x0000) - not-present page
[89408.371940] PGD 0 P4D 0
[89408.371953] Oops: Oops: 0000 [#1] SMP NOPTI
<snip>
[89408.372052] RIP: 0010:memcpy_orig+0x16/0x130
[89408.372310] Call Trace:
[89408.372317] <TASK>
[89408.372326] ? idpf_set_features+0xfc/0x180 [idpf]
[89408.372363] __netdev_update_features+0x295/0xde0
[89408.372384] ethnl_set_features+0x15e/0x460
[89408.372406] genl_family_rcv_msg_doit+0x11f/0x180
[89408.372429] genl_rcv_msg+0x1ad/0x2b0
[89408.372446] ? __pfx_ethnl_set_features+0x10/0x10
[89408.372465] ? __pfx_genl_rcv_msg+0x10/0x10
[89408.372482] netlink_rcv_skb+0x58/0x100
[89408.372502] genl_rcv+0x2c/0x50
[89408.372516] netlink_unicast+0x289/0x3e0
[89408.372533] netlink_sendmsg+0x215/0x440
[89408.372551] __sys_sendto+0x234/0x240
[89408.372571] __x64_sys_sendto+0x28/0x30
[89408.372585] x64_sys_call+0x1909/0x1da0
[89408.372604] do_syscall_64+0x7a/0xfa0
[89408.373140] ? clear_bhb_loop+0x60/0xb0
[89408.373647] entry_SYSCALL_64_after_hwframe+0x76/0x7e
[89408.378887] </TASK>
<snip>
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a system using the idpf network driver when an early network feature change is made before the interface is first brought up. The business impact is mainly availability: affected hosts may suffer a kernel crash, but the sources do not show remote exploitation or active exploitation.
Executive priority
Prioritize patching on production hosts that use idpf network devices, especially where a kernel crash would affect critical services. This is not presented as internet-exploitable in the provided sources, so urgency should be driven by host criticality and exposure to local network administration actions.
Technical view
In the idpf driver, the RSS lookup table was initialized during interface open. ethtool feature changes such as disabling rxhash before first interface up could dereference a NULL RSS LUT and trigger a kernel oops. The fix moves LUT initialization to vport creation and defers hardware programming when the interface is down.
Likely exposure
Exposure appears limited to Linux systems running affected kernels with the idpf driver loaded and idpf interfaces created. The trigger involves ethtool feature changes before first interface activation. Source version data is incomplete and should be mapped to vendor or distribution kernel packages.
Exploitation context
The source bundle provides a local reproduction path through ethtool and marks CISA KEV status as false. It does not cite active exploitation, remote exploitation, public exploit tooling, or privilege requirements. Treat this as a stability and local availability concern unless vendor guidance says otherwise.
Researcher notes
The affected version data in the bundle is sparse and partly ambiguous. The clearest root cause and fix details come from the kernel description and stable commit references. Do not infer broader driver families, remote reachability, or exploit maturity from this record alone.
Mitigation direction
Apply kernel updates containing the referenced stable idpf fixes.
Check Linux distribution advisories for package-specific fixed versions.
Avoid pre-up ethtool rxhash changes on idpf interfaces until patched.
If patching is delayed, restrict who can change network device features.
Validation and detection
Inventory hosts using the idpf driver and affected kernel builds.
Confirm whether idpf interfaces are created before first activation.
Review operational scripts for early ethtool rxhash or RSS changes.
Verify deployed kernels include one of the referenced stable commits.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-22985 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
4Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jan 23, 2026, 15:24 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.