CVE-2026-43208
Analyzed Analyzed - Analysis Complete
Linux Kernel RPS Flow ID Handling Remote Code Execution

Publication date: 2026-05-06

Last updated on: 2026-05-11

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: net: do not pass flow_id to set_rps_cpu() Blamed commit made the assumption that the RPS table for each receive queue would have the same size, and that it would not change. Compute flow_id in set_rps_cpu(), do not assume we can use the value computed by get_rps_cpu(). Otherwise we risk out-of-bound access and/or crashes.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-11
Generated
2026-06-16
AI Q&A
2026-05-06
EPSS Evaluated
2026-06-15
NVD
CVE-2026-43208
EUVD
EUVD-2026-27771
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel 7.0
linux linux_kernel From 6.19 (inc) to 6.19.6 (exc)
linux linux_kernel From 6.18 (inc) to 6.18.16 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves improper handling of the flow_id parameter in the set_rps_cpu() function. The original code assumed that the RPS (Receive Packet Steering) table for each receive queue would have the same size and remain unchanged. However, this assumption was incorrect. The vulnerability arises because the code used a flow_id value computed by get_rps_cpu() without recalculating it in set_rps_cpu(), which could lead to out-of-bound memory access or crashes.

Impact Analysis

This vulnerability can cause out-of-bound memory access or crashes in the Linux kernel's network stack. Such crashes can lead to denial of service conditions, potentially disrupting network communications or system stability.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-43208. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart