In the Linux kernel, the following vulnerability has been resolved:
idpf: Fix RSS LUT NULL ptr issue after soft reset
During soft reset, the RSS LUT is freed and not restored unless the
interface is up. If an ethtool command that accesses the rss lut is
attempted immediately after reset, it will result in NULL ptr
dereference. Also, there is no need to reset the rss lut if the soft reset
does not involve queue count change.
After soft reset, set the RSS LUT to default values based on the updated
queue count only if the reset was a result of a queue count change and
the LUT was not configured by the user. In all other cases, don't touch
the LUT.
Steps to reproduce:
** Bring the interface down (if up)
ifconfig eth1 down
** update the queue count (eg., 27->20)
ethtool -L eth1 combined 20
** display the RSS LUT
ethtool -x eth1
[82375.558338] BUG: kernel NULL pointer dereference, address: 0000000000000000
[82375.558373] #PF: supervisor read access in kernel mode
[82375.558391] #PF: error_code(0x0000) - not-present page
[82375.558408] PGD 0 P4D 0
[82375.558421] Oops: Oops: 0000 [#1] SMP NOPTI
<snip>
[82375.558516] RIP: 0010:idpf_get_rxfh+0x108/0x150 [idpf]
[82375.558786] Call Trace:
[82375.558793] <TASK>
[82375.558804] rss_prepare.isra.0+0x187/0x2a0
[82375.558827] rss_prepare_data+0x3a/0x50
[82375.558845] ethnl_default_doit+0x13d/0x3e0
[82375.558863] genl_family_rcv_msg_doit+0x11f/0x180
[82375.558886] genl_rcv_msg+0x1ad/0x2b0
[82375.558902] ? __pfx_ethnl_default_doit+0x10/0x10
[82375.558920] ? __pfx_genl_rcv_msg+0x10/0x10
[82375.558937] netlink_rcv_skb+0x58/0x100
[82375.558957] genl_rcv+0x2c/0x50
[82375.558971] netlink_unicast+0x289/0x3e0
[82375.558988] netlink_sendmsg+0x215/0x440
[82375.559005] __sys_sendto+0x234/0x240
[82375.559555] __x64_sys_sendto+0x28/0x30
[82375.560068] x64_sys_call+0x1909/0x1da0
[82375.560576] do_syscall_64+0x7a/0xfa0
[82375.561076] ? clear_bhb_loop+0x60/0xb0
[82375.561567] entry_SYSCALL_64_after_hwframe+0x76/0x7e
<snip>
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel crash bug in the idpf network driver. After a soft reset tied to queue-count changes, the driver can leave its RSS lookup table unset. A later RSS query can dereference a null pointer and crash the kernel path handling the request.
Executive priority
Treat as a targeted availability risk for affected Linux network hosts, not a broad internet-facing compromise signal. Patch through normal kernel maintenance, faster for systems where idpf configuration is actively automated or operationally critical.
Technical view
The flaw is a NULL pointer dereference in idpf_get_rxfh after soft reset. The RSS LUT may be freed and not restored when the interface is down, then accessed through ethtool RSS handling. The upstream fix preserves or reinitializes the LUT only when appropriate after queue-count changes.
Likely exposure
Exposure appears limited to Linux systems using the idpf driver where administrators or management tooling change queue counts and query RSS state around soft resets. The source data lists affected Linux kernel versions but does not provide full distribution package mapping.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The reproduced impact is a kernel NULL pointer dereference triggered through local network-management operations, consistent with denial of service rather than data theft.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. The affected-version data is incomplete and somewhat ambiguous, so distribution-specific validation is required. Do not assume exploitability beyond the documented local crash scenario.
Mitigation direction
Apply Linux kernel updates that include the referenced stable fixes.
Check distribution vendor advisories for affected package versions and backports.
Avoid queue-count changes followed by RSS queries on down idpf interfaces until patched.
Prioritize hosts where automated network tooling manages idpf queue or RSS settings.
Validation and detection
Inventory Linux hosts using the idpf network driver.
Check running kernel versions against vendor advisories and stable fix inclusion.
Review automation for queue-count and RSS inspection workflows on idpf interfaces.
Confirm patched kernels include one of the referenced upstream 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-22993 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.