In the Linux kernel, the following vulnerability has been resolved:
virtio_net: Fix misalignment bug in struct virtnet_info
Use the new TRAILING_OVERLAP() helper to fix a misalignment bug along with the following warning:
drivers/net/virtio_net.c:429:46: warning: structure containing a flexible array member is not at the end of another structure [-Wflex-array-member-not-at-end]
This helper creates a union between a flexible-array member (FAM) and a set of members that would otherwise follow it (in this case `u8 rss_hash_key_data[VIRTIO_NET_RSS_MAX_KEY_SIZE];`). This overlays the trailing members (rss_hash_key_data) onto the FAM (hash_key_data) while keeping the FAM and the start of MEMBERS aligned. The static_assert() ensures this alignment remains.
Notice that due to tail padding in flexible `struct virtio_net_rss_config_trailer`, `rss_trailer.hash_key_data` (at offset 83 in struct virtnet_info) and `rss_hash_key_data` (at offset 84 in struct virtnet_info) are misaligned by one byte. See below:
struct virtio_net_rss_config_trailer { __le16 max_tx_vq; /* 0 2 */ __u8 hash_key_length; /* 2 1 */ __u8 hash_key_data[]; /* 3 0 */
/* size: 4, cachelines: 1, members: 3 */ /* padding: 1 */ /* last cacheline: 4 bytes */ };
struct virtnet_info { ... struct virtio_net_rss_config_trailer rss_trailer; /* 80 4 */
/* XXX last struct has 1 byte of padding */
u8 rss_hash_key_data[40]; /* 84 40 */ ... /* size: 832, cachelines: 13, members: 48 */ /* sum members: 801, holes: 8, sum holes: 31 */ /* paddings: 2, sum paddings: 5 */ };
After changes, those members are correctly aligned at offset 795:
struct virtnet_info { ... union { struct virtio_net_rss_config_trailer rss_trailer; /* 792 4 */ struct { unsigned char __offset_to_hash_key_data[3]; /* 792 3 */ u8 rss_hash_key_data[40]; /* 795 40 */ }; /* 792 43 */ }; /* 792 44 */ ... /* size: 840, cachelines: 14, members: 47 */ /* sum members: 801, holes: 8, sum holes: 35 */ /* padding: 4 */ /* paddings: 1, sum paddings: 4 */ /* last cacheline: 8 bytes */ };
As a result, the RSS key passed to the device is shifted by 1 byte: the last byte is cut off, and instead a (possibly uninitialized) byte is added at the beginning.
As a last note `struct virtio_net_rss_config_hdr *rss_hdr;` is also moved to the end, since it seems those three members should stick around together. :)
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Redhat_linux | — | No solution exists | Jul 17, 2026 | Feb 14, 2026 |
| Ubuntu | — | Upgrade linux-image-gcpUpgrade linux-image-realtime-hwe-24.04Upgrade linux-image-azure-6.17Upgrade linux-image-oem-24.04bUpgrade linux-image-6.17.0-1019-oracle-64kUpgrade linux-image-oem-24.04dUpgrade linux-image-azure-fdeUpgrade linux-image-nvidia-hwe-24.04Upgrade linux-image-6.17.0-1031-nvidiaUpgrade linux-image-6.17.0-1018-azure-fdeUpgrade linux-image-6.17.0-1021-azureUpgrade linux-image-6.17.0-1030-oemUpgrade linux-image-nvidia-64k-hwe-24.04Upgrade linux-image-azure-fde-6.17Upgrade linux-image-oem-24.04Upgrade linux-image-nvidia-6.17Upgrade linux-image-gcp-6.17Upgrade linux-image-oem-24.04aUpgrade linux-image-oracleUpgrade linux-image-6.17.0-1021-gcpUpgrade linux-image-oracle-6.17Upgrade linux-image-oem-24.04cUpgrade linux-image-gcp-64k-6.17Upgrade linux-image-6.17.0-1021-gcp-64kUpgrade linux-image-oem-6.17Upgrade linux-image-realtime-6.17Upgrade linux-image-oracle-64k-6.17Upgrade linux-image-gcp-64kUpgrade linux-image-6.17.0-1031-nvidia-64kUpgrade linux-image-nvidia-64k-6.17Upgrade linux-image-azureUpgrade linux-image-6.17.0-1018-realtimeUpgrade linux-image-oracle-64kUpgrade linux-image-6.17.0-1019-oracle | Jul 21, 2026 | Jul 20, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub