CVE-2026-43208

net: do not pass flow_id to set_rps_cpu()

Published May 6, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Linux kernel contains a flaw where the commit that handles receive packet steering incorrectly reuses a flow identifier computed elsewhere. This incorrect reuse allows the kernel to access memory beyond the bounds of the RPS table, potentially leading to a crash or loss of data integrity. The vulnerability is a classic out-of-bounds memory access (CWE-787) that can cause the operating system to become unstable or unusable.

Affected Systems

All Linux kernel builds that do not include the commit that corrects the flow-ID handling are affected. The issue does not appear to be tied to a specific kernel version; any distribution that has not applied the patch will be vulnerable.

Risk and Exploitability

The CVSS score of 9.8 indicates critical severity, as a process that can craft network packets to trigger the flawed logic could cause a kernel fault. The EPSS score is low at <1%, and the vulnerability is not listed in CISA KEV, so the publicly known exploitation probability is uncertain. The likely attack vector involves manipulating network traffic that is processed by the receive queue, which could be local or remote depending on the system configuration. System administrators should assume that any exploitation could result in a denial of service and should act quickly to mitigate.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel version that includes the RPS table size check fix (commit 5455a232e or later).
  • If a distribution update is unavailable, obtain the patch from the kernel Git repository, apply it to the source tree, and rebuild the kernel.
  • Temporarily disable receive packet steering by setting the appropriate sysctl parameters (e.g., echo 0 > /sys/module/rps/parameters/rps_enabled).

Generated by OpenCVE AI on May 11, 2026 at 22:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-787
CPEs cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-119
Type Values Removed Values Added
Weaknesses CWE-805
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Important

Type Values Removed Values Added
Weaknesses CWE-119
Type Values Removed Values Added
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.
Title net: do not pass flow_id to set_rps_cpu()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses
  • CWE-787

    Out-of-bounds Write

  • CWE-805

    Buffer Access with Incorrect Length Value

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Aug 5, 2026, 12:26 PM
Reserved
May 1, 2026, 2:12 PM
Status
Analyzed
Published
May 6, 2026, 12:16 PM
Modified
Nov 11, 2026, 8:10 PM
Severity
Important
Public date
May 6, 2026, 12:00 AM