CVE-2021-3490: Linux kernel eBPF bitwise ops ALU32 bounds tracking

Published Jun 4, 2021
·
Updated

Last updated 4 July 2026

Other sources

The eBPF ALU32 bounds tracking for bitwise ops (AND, OR and XOR) in the Linux kernel did not properly update 32-bit bounds, which could be turned into out of bounds reads and writes in the Linux kernel and therefore, arbitrary code execution. This issue was fixed via commit 049c4e13714e ("bpf: Fix alu32 const subreg bound tracking on bitwise operations") (v5.13-rc4) and backported to the stable kernels in v5.12.4, v5.11.21, and v5.10.37. The AND/OR issues were introduced by commit 3f50f132d840 ("bpf: Verifier, do explicit ALU32 bounds tracking") (5.7-rc1) and the XOR variant was introduced by 2921c90d4718 ("bpf:Fix a verifier failure with xor") ( 5.10-rc1).

Launchpad

Affected Software

11 affected componentsFixes available
Linux Linux kernel>=5.10<5.10.37
Linux Linux kernel>=5.11<5.11.21
Linux Linux kernel>=5.12<5.12.4
Linux Linux kernel=5.13
Linux Linux kernel=5.13-rc1
Linux Linux kernel=5.13-rc2
Linux Linux kernel=5.13-rc3
Canonical Ubuntu Linux=20.04
Canonical Ubuntu Linux=20.10
Canonical Ubuntu Linux=21.04
debian/linux
5.10.223-15.10.259-16.1.176-16.1.177-16.12.94-16.12.95-17.1.3-17.1.4-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.259-1Fixed in 6.1.176-1Fixed in 6.1.177-1Fixed in 6.12.94-1Fixed in 6.12.95-1Fixed in 7.1.3-1Fixed in 7.1.4-1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v5.13-rc4Patch 049c4e13714
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v5.12.4
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v5.11.21
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v5.10.37

Event History

Jun 4, 2021
CVE Published
via MITRE·01:40 AM
Data Sourced
via MITRE·01:40 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:57 PM
Description
Jun 29, 2026
Advisory Published
via ZDI·04:44 AM
Data Sourced
via ZDI·04:44 AM
DescriptionAffected Software
Jul 8, 2026
Data Sourced
via Ubuntu·05:00 AM
RemedyDescriptionSeverityAffected Software
Jul 20, 2026
Data Sourced
via Debian·11:58 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2021-3490?

CVE-2021-3490 is considered a high severity vulnerability due to its potential for arbitrary code execution in the Linux kernel.

2

How do I fix CVE-2021-3490?

To mitigate CVE-2021-3490, update your Linux kernel to a version that addresses this vulnerability, such as 5.10.223-1 or later.

3

Which Linux kernel versions are affected by CVE-2021-3490?

CVE-2021-3490 affects Linux kernel versions between 5.10 and 5.13, including specific release candidates.

4

What type of vulnerability is CVE-2021-3490 classified as?

CVE-2021-3490 is classified as a memory corruption vulnerability that stems from improper bounds tracking.

5

Can CVE-2021-3490 be exploited remotely?

CVE-2021-3490 requires local access to the system for exploitation, making it a local privilege escalation issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203