CVE-2026-74410

Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source

AV:AAttack vector, adjacent network

The bug is in rtw_pci_rx_napi() on the rtw88 PCIe WiFi RX path, reached when firmware DMAs received 802.11 frames and raises IMR_ROK; exploitation requires transmitting crafted or maximum-size WiFi frames within radio range, which is an adjacent wireless attack per kernel CVSS guidance.

AC:LAttack complexity, low

An adjacent attacker can reliably trigger the bug by sending WiFi traffic that causes firmware to populate RX descriptors with pkt_len (up to 16383) plus pkt_offset (drv_info_sz+shift); sums above RTK_PCI_RX_BUF_SIZE (11478) are possible even with max VHT MPDUs (~11454 bytes), and the PCIe path lacked the USB driver's length validation.

PR:NPrivileges required, none

No local account, capabilities, or namespace privileges on the victim are required; any unauthenticated attacker in WiFi range can cause the device to receive frames and invoke the driver RX interrupt/NAPI handler without victim credentials or association to the attacker's network.

UI:NUser interaction, none

Exploitation requires only that the rtw88 PCIe interface is active and receiving frames, which is the default on laptops, desktops, and many embedded systems with WiFi enabled; no additional victim actions such as opening files or mounting filesystems are needed.

S:UScope, unchanged

The vulnerability is confined to kernel memory accessed by the rtw88 host driver during RX processing on the same system; it does not cross a VM, container, or IOMMU security boundary to impact a separate security authority.

C:HConfidentiality impact, high

skb_put_data() copies new_len bytes from a 11478-byte DMA RX skb without bounds checking, performing an out-of-bounds kernel heap read of up to thousands of bytes of adjacent slab memory that may contain pointers, keys, or other sensitive data subsequently embedded in the RX skb.

I:NIntegrity impact, none

The flaw is an out-of-bounds read via memcpy from the undersized RX buffer into a separately allocated skb; it does not directly overwrite kernel memory or provide an arbitrary write primitive, though leaked data could aid separate exploitation.

A:HAvailability impact, high

Reading substantially beyond the mapped 11478-byte RX DMA buffer can access unmapped pages or slab redzones and provoke a kernel fault/oops during interrupt/NAPI processing, and repeated malicious frames can disrupt WiFi RX availability on affected rtw88 PCIe devices.