CVE-2021-3490
Linux kernel eBPF bitwise ops ALU32 bounds tracking
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).
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- High
- Privileges needed
- Low
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.8
Linux kernel eBPF bitwise ops ALU32 bounds tracking
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).
- Record
CVE-2021-3490- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Weakness
- CWE-787, CWE-20
- Updated
- 2026-11-02
EUVDEUVD-2021-26812
7.8
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).
- Record
EUVD-2021-26812- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-03
GitHub AdvisoriesGHSA-9wfm-q59x-qc3x No score
The eBPF ALU32 bounds tracking for bitwise ops (AND, OR and XOR) in the Linux kernel did not...
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).
- Record
GHSA-9wfm-q59x-qc3x- Weakness
- CWE-125
- Updated
- 2026-11-02
NVD
7.8
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).
- Record
CVE-2021-3490- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 2.0
- 7.2 High
AV:L/AC:L/Au:N/C:C/I:C/A:C - Weakness
- CWE-20, CWE-787, CWE-125
- Updated
- 2026-11-02
OSV
7.8
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).
- Record
CVE-2021-3490- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVDEBIAN-CVE-2021-3490
7.8
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).
- Record
DEBIAN-CVE-2021-3490- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 11 moreShow less
OSVUBUNTU-CVE-2021-3490
7.8
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).
- Record
UBUNTU-CVE-2021-3490- CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 3.1
- 7.8 High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVopenSUSE-SU-2021:1975-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 Azure kernel was updated to receive various security and bugfixes.
The following security bugs were fixed:
- CVE-2021-33200: Enforcing incorrect limits for pointer arithmetic operations by the BPF verifier could be abused to perform out-of-bounds reads and writes in kernel memory (bsc#1186484).
- CVE-2021-33034: Fixed a use-after-free when destroying an hci_chan. This could lead to writing an arbitrary values. (bsc#1186111)
- CVE-2020-26139: Fixed a denial-of-service when an Access Point (AP) forwards EAPOL frames to other clients even though the sender has not yet successfully authenticated to the AP. (bnc#1186062)
- CVE-2021-23134: A Use After Free vulnerability in nfc sockets allowed local attackers to elevate their privileges. (bnc#1186060)
- CVE-2021-3491: Fixed a potential heap overflow in mem_rw(). This vulnerability is related to the PROVIDE_BUFFERS operation, which allowed the MAX_RW_COUNT limit to be bypassed (bsc#1185642).
- CVE-2021-32399: Fixed a race condition when removing the HCI controller (bnc#1184611).
- CVE-2020-24586: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances this can be abused to inject arbitrary network packets and/or exfiltrate user data (bnc#1185859).
- CVE-2020-24587: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP encryption key is periodically renewed (bnc#1185859 bnc#1185862).
- CVE-2020-24588: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802.11n), an adversary can abuse this to inject arbitrary network packets. (bnc#1185861)
- CVE-2020-26147: The WEP, WPA, WPA2, and WPA3 implementations reassemble fragments, even though some of them were sent in plaintext. This vulnerability can be abused to inject packets and/or exfiltrate selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used (bnc#1185859).
- CVE-2020-26145: An issue was discovered with Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration. (bnc#1185860)
- CVE-2020-26141: An issue was discovered in the ALFA driver for AWUS036H, where the Message Integrity Check (authenticity) of fragmented TKIP frames was not verified. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol. (bnc#1185987)
- CVE-2021-29650: Fixed an issue with the netfilter subsystem that allowed attackers to cause a denial of service (panic) because net/netfilter/x_tables.c and include/linux/netfilter/x_tables.h lack a full memory barrier upon the assignment of a new table value (bnc#1184208).
- CVE-2021-29155: Fixed an issue that was discovered in kernel/bpf/verifier.c that performs undesirable out-of-bounds speculation on pointer arithmetic, leading to side-channel attacks that defeat Spectre mitigations and obtain sensitive information from kernel memory. Specifically, for sequences of pointer arithmetic operations, the pointer modification performed by the first operation was not correctly accounted for when…
- Record
openSUSE-SU-2021:1975-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2021:1977-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security and bugfixes.
The following security bugs were fixed:
- CVE-2021-33200: Enforcing incorrect limits for pointer arithmetic operations by the BPF verifier could be abused to perform out-of-bounds reads and writes in kernel memory (bsc#1186484).
- CVE-2021-33034: Fixed a use-after-free when destroying an hci_chan. This could lead to writing an arbitrary values. (bsc#1186111)
- CVE-2020-26139: Fixed a denial-of-service when an Access Point (AP) forwards EAPOL frames to other clients even though the sender has not yet successfully authenticated to the AP. (bnc#1186062)
- CVE-2021-23134: A Use After Free vulnerability in nfc sockets allowed local attackers to elevate their privileges. (bnc#1186060)
- CVE-2021-3491: Fixed a potential heap overflow in mem_rw(). This vulnerability is related to the PROVIDE_BUFFERS operation, which allowed the MAX_RW_COUNT limit to be bypassed (bsc#1185642).
- CVE-2021-32399: Fixed a race condition when removing the HCI controller (bnc#1184611).
- CVE-2020-24586: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances this can be abused to inject arbitrary network packets and/or exfiltrate user data (bnc#1185859).
- CVE-2020-24587: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP encryption key is periodically renewed (bnc#1185859 bnc#1185862).
- CVE-2020-24588: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802.11n), an adversary can abuse this to inject arbitrary network packets. (bnc#1185861)
- CVE-2020-26147: The WEP, WPA, WPA2, and WPA3 implementations reassemble fragments, even though some of them were sent in plaintext. This vulnerability can be abused to inject packets and/or exfiltrate selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used (bnc#1185859).
- CVE-2020-26145: An issue was discovered with Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration. (bnc#1185860)
- CVE-2020-26141: An issue was discovered in the ALFA driver for AWUS036H, where the Message Integrity Check (authenticity) of fragmented TKIP frames was not verified. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol. (bnc#1185987)
- CVE-2021-29650: Fixed an issue with the netfilter subsystem that allowed attackers to cause a denial of service (panic) because net/netfilter/x_tables.c and include/linux/netfilter/x_tables.h lack a full memory barrier upon the assignment of a new table value (bnc#1184208).
- CVE-2021-29155: Fixed an issue that was discovered in kernel/bpf/verifier.c that performs undesirable out-of-bounds speculation on pointer arithmetic, leading to side-channel attacks that defeat Spectre mitigations and obtain sensitive information from kernel memory. Specifically, for sequences of pointer arithmetic operations, the pointer modification performed by the first operation was not correctly accounted for when restricting…
- Record
openSUSE-SU-2021:1977-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10728-1 No score
kernel-devel-5.14.6-1.4 on GA media
These are all security issues fixed in the kernel-devel-5.14.6-1.4 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10728-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:13704-1 No score
kernel-devel-longterm-6.6.17-1.1 on GA media
These are all security issues fixed in the kernel-devel-longterm-6.6.17-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:13704-1- Updated
- 2026-11-02
OSVPUB-A-190876666 No score
In scalar32_min_max_and and related functions of verifier.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.
- Record
PUB-A-190876666- Updated
- 2026-11-05
OSVSUSE-SU-2021:1975-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 Azure kernel was updated to receive various security and bugfixes.
The following security bugs were fixed:
- CVE-2021-33200: Enforcing incorrect limits for pointer arithmetic operations by the BPF verifier could be abused to perform out-of-bounds reads and writes in kernel memory (bsc#1186484).
- CVE-2021-33034: Fixed a use-after-free when destroying an hci_chan. This could lead to writing an arbitrary values. (bsc#1186111)
- CVE-2020-26139: Fixed a denial-of-service when an Access Point (AP) forwards EAPOL frames to other clients even though the sender has not yet successfully authenticated to the AP. (bnc#1186062)
- CVE-2021-23134: A Use After Free vulnerability in nfc sockets allowed local attackers to elevate their privileges. (bnc#1186060)
- CVE-2021-3491: Fixed a potential heap overflow in mem_rw(). This vulnerability is related to the PROVIDE_BUFFERS operation, which allowed the MAX_RW_COUNT limit to be bypassed (bsc#1185642).
- CVE-2021-32399: Fixed a race condition when removing the HCI controller (bnc#1184611).
- CVE-2020-24586: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances this can be abused to inject arbitrary network packets and/or exfiltrate user data (bnc#1185859).
- CVE-2020-24587: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP encryption key is periodically renewed (bnc#1185859 bnc#1185862).
- CVE-2020-24588: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802.11n), an adversary can abuse this to inject arbitrary network packets. (bnc#1185861)
- CVE-2020-26147: The WEP, WPA, WPA2, and WPA3 implementations reassemble fragments, even though some of them were sent in plaintext. This vulnerability can be abused to inject packets and/or exfiltrate selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used (bnc#1185859).
- CVE-2020-26145: An issue was discovered with Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration. (bnc#1185860)
- CVE-2020-26141: An issue was discovered in the ALFA driver for AWUS036H, where the Message Integrity Check (authenticity) of fragmented TKIP frames was not verified. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol. (bnc#1185987)
- CVE-2021-29650: Fixed an issue with the netfilter subsystem that allowed attackers to cause a denial of service (panic) because net/netfilter/x_tables.c and include/linux/netfilter/x_tables.h lack a full memory barrier upon the assignment of a new table value (bnc#1184208).
- CVE-2021-29155: Fixed an issue that was discovered in kernel/bpf/verifier.c that performs undesirable out-of-bounds speculation on pointer arithmetic, leading to side-channel attacks that defeat Spectre mitigations and obtain sensitive information from kernel memory. Specifically, for sequences of pointer arithmetic operations, the pointer modification performed by the first operation was not correctly accounted for when…
- Record
SUSE-SU-2021:1975-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:1977-1 No score
Security update for the Linux Kernel
The SUSE Linux Enterprise 15 SP3 kernel was updated to receive various security and bugfixes.
The following security bugs were fixed:
- CVE-2021-33200: Enforcing incorrect limits for pointer arithmetic operations by the BPF verifier could be abused to perform out-of-bounds reads and writes in kernel memory (bsc#1186484).
- CVE-2021-33034: Fixed a use-after-free when destroying an hci_chan. This could lead to writing an arbitrary values. (bsc#1186111)
- CVE-2020-26139: Fixed a denial-of-service when an Access Point (AP) forwards EAPOL frames to other clients even though the sender has not yet successfully authenticated to the AP. (bnc#1186062)
- CVE-2021-23134: A Use After Free vulnerability in nfc sockets allowed local attackers to elevate their privileges. (bnc#1186060)
- CVE-2021-3491: Fixed a potential heap overflow in mem_rw(). This vulnerability is related to the PROVIDE_BUFFERS operation, which allowed the MAX_RW_COUNT limit to be bypassed (bsc#1185642).
- CVE-2021-32399: Fixed a race condition when removing the HCI controller (bnc#1184611).
- CVE-2020-24586: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that received fragments be cleared from memory after (re)connecting to a network. Under the right circumstances this can be abused to inject arbitrary network packets and/or exfiltrate user data (bnc#1185859).
- CVE-2020-24587: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that all fragments of a frame are encrypted under the same key. An adversary can abuse this to decrypt selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP encryption key is periodically renewed (bnc#1185859 bnc#1185862).
- CVE-2020-24588: The 802.11 standard that underpins Wi-Fi Protected Access (WPA, WPA2, and WPA3) and Wired Equivalent Privacy (WEP) doesn't require that the A-MSDU flag in the plaintext QoS header field is authenticated. Against devices that support receiving non-SSP A-MSDU frames (which is mandatory as part of 802.11n), an adversary can abuse this to inject arbitrary network packets. (bnc#1185861)
- CVE-2020-26147: The WEP, WPA, WPA2, and WPA3 implementations reassemble fragments, even though some of them were sent in plaintext. This vulnerability can be abused to inject packets and/or exfiltrate selected fragments when another device sends fragmented frames and the WEP, CCMP, or GCMP data-confidentiality protocol is used (bnc#1185859).
- CVE-2020-26145: An issue was discovered with Samsung Galaxy S3 i9305 4.4.4 devices. The WEP, WPA, WPA2, and WPA3 implementations accept second (or subsequent) broadcast fragments even when sent in plaintext and process them as full unfragmented frames. An adversary can abuse this to inject arbitrary network packets independent of the network configuration. (bnc#1185860)
- CVE-2020-26141: An issue was discovered in the ALFA driver for AWUS036H, where the Message Integrity Check (authenticity) of fragmented TKIP frames was not verified. An adversary can abuse this to inject and possibly decrypt packets in WPA or WPA2 networks that support the TKIP data-confidentiality protocol. (bnc#1185987)
- CVE-2021-29650: Fixed an issue with the netfilter subsystem that allowed attackers to cause a denial of service (panic) because net/netfilter/x_tables.c and include/linux/netfilter/x_tables.h lack a full memory barrier upon the assignment of a new table value (bnc#1184208).
- CVE-2021-29155: Fixed an issue that was discovered in kernel/bpf/verifier.c that performs undesirable out-of-bounds speculation on pointer arithmetic, leading to side-channel attacks that defeat Spectre mitigations and obtain sensitive information from kernel memory. Specifically, for sequences of pointer arithmetic operations, the pointer modification performed by the first operation was not correctly accounted for when restricting…
- Record
SUSE-SU-2021:1977-1- Updated
- 2026-11-02
OSVSUSE-SU-2021:2198-1 No score
Security update for the Linux Kernel (Live Patch 0 for SLE 15 SP3)
This update for the Linux Kernel 5.3.18-57 fixes several issues.
The following issues were fixed:
- CVE-2021-3489: Fixed an issue where the eBPF RINGBUF bpf_ringbuf_reserve did not check that the allocated size was smaller than the ringbuf size (bsc#1185640).
- CVE-2021-3490: Fixed an issue where the eBPF ALU32 bounds tracking for bitwise ops (AND, OR and XOR) did not update the 32-bit bounds (bsc#1185641).
- CVE-2021-33034: Fixed a use-after-free when destroying an hci_chan. This could lead to writing an arbitrary values (bsc#1186111).
- CVE-2021-32399: Fixed a race condition when removing the HCI controller (bsc#1184611).
- CVE-2020-36322: Fixed an issue was discovered in FUSE filesystem implementation which could have caused a system crash (bsc#1184211).
- CVE-2021-29154: Fixed incorrect computation of branch displacements, allowing arbitrary code execution (bsc#1184391).
- CVE-2021-28660: Fixed an out of bounds write in rtw_wx_set_scan (bsc#1183593).
- Fixed a data loss/data corruption that occurs if there is a write error on an md/raid array (bsc#1185847).
- Record
SUSE-SU-2021:2198-1- Updated
- 2026-11-02
OSVUSN-4948-1 No score
linux-oem-5.10 vulnerabilities
Ryota Shiga discovered that the eBPF implementation in the Linux kernel did not properly verify that a BPF program only reserved as much memory for a ring buffer as was allocated. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3489)
Manfred Paul discovered that the eBPF implementation in the Linux kernel did not properly track bounds on bitwise operations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3490)
Billy Jheng Bing-Jhong discovered that the io_uring implementation of the Linux kernel did not properly enforce the MAX_RW_COUNT limit in some situations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3491)
Kiyin (尹亮) discovered that the NFC LLCP protocol implementation in the Linux kernel contained a reference counting error. A local attacker could use this to cause a denial of service (system crash). (CVE-2020-25670)
Kiyin (尹亮) discovered that the NFC LLCP protocol implementation in the Linux kernel did not properly deallocate memory in certain error situations. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2020-25671, CVE-2020-25672)
It was discovered that the Xen paravirtualization backend in the Linux kernel did not properly deallocate memory in some situations. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2021-28688)
It was discovered that the io_uring subsystem in the Linux kernel contained a race condition leading to a deadlock condition. A local attacker could use this to cause a denial of service. (CVE-2021-28951)
John Stultz discovered that the audio driver for Qualcomm SDM845 systems in the Linux kernel did not properly validate port ID numbers. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-28952)
Zygo Blaxell discovered that the btrfs file system implementation in the Linux kernel contained a race condition during certain cloning operations. A local attacker could possibly use this to cause a denial of service (system crash). (CVE-2021-28964)
Vince Weaver discovered that the perf subsystem in the Linux kernel did not properly handle certain PEBS records properly for some Intel Haswell processors. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-28971)
It was discovered that the RPA PCI Hotplug driver implementation in the Linux kernel did not properly handle device name writes via sysfs, leading to a buffer overflow. A privileged attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-28972)
It was discovered that the Freescale Gianfar Ethernet driver for the Linux kernel did not properly handle receive queue overrun when jumbo frames were enabled in some situations. An attacker could use this to cause a denial of service (system crash). (CVE-2021-29264)
It was discovered that the vDPA backend virtio driver in the Linux kernel contained a use-after-free vulnerability. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-29266)
It was discovered that the TIPC protocol implementation in the Linux kernel did not properly validate passed encryption key sizes. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-29646)
It was discovered that the Qualcomm IPC router implementation in the Linux kernel did not properly initialize memory passed to user space. A local attacker could use this to expose sensitive information (kernel memory). (CVE-2021-29647)
It was discovered that the BPF user mode driver implementation in the Linux kernel did not properly deallocate memory in some situations. A local attacker could use this to cause a denial of service…
- Record
USN-4948-1- Updated
- 2026-11-02
OSVUSN-4949-1 No score
linux, linux-aws, linux-azure, linux-gcp, linux-hwe-5.8, linux-kvm, linux-oracle, linux-raspi vulnerabilities
Ryota Shiga discovered that the eBPF implementation in the Linux kernel did not properly verify that a BPF program only reserved as much memory for a ring buffer as was allocated. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3489)
Manfred Paul discovered that the eBPF implementation in the Linux kernel did not properly track bounds on bitwise operations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3490)
Billy Jheng Bing-Jhong discovered that the io_uring implementation of the Linux kernel did not properly enforce the MAX_RW_COUNT limit in some situations. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2021-3491)
It was discovered that the Nouveau GPU driver in the Linux kernel did not properly handle error conditions in some situations. A local attacker could use this to cause a denial of service (system crash). (CVE-2020-25639)
Olivier Benjamin, Norbert Manthey, Martin Mazein, and Jan H. Schönherr discovered that the Xen paravirtualization backend in the Linux kernel did not properly propagate errors to frontend drivers in some situations. An attacker in a guest VM could possibly use this to cause a denial of service (host domain crash). (CVE-2021-26930)
Jan Beulich discovered that multiple Xen backends in the Linux kernel did not properly handle certain error conditions under paravirtualization. An attacker in a guest VM could possibly use this to cause a denial of service (host domain crash). (CVE-2021-26931)
It was discovered that the fastrpc driver in the Linux kernel did not prevent user space applications from sending kernel RPC messages. A local attacker could possibly use this to gain elevated privileges. (CVE-2021-28375)
It was discovered that the Freescale Gianfar Ethernet driver for the Linux kernel did not properly handle receive queue overrun when jumbo frames were enabled in some situations. An attacker could use this to cause a denial of service (system crash). (CVE-2021-29264)
It was discovered that the USB/IP driver in the Linux kernel contained race conditions during the update of local and shared status. An attacker could use this to cause a denial of service (system crash). (CVE-2021-29265)
It was discovered that the vDPA backend virtio driver in the Linux kernel contained a use-after-free vulnerability. An attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2021-29266)
It was discovered that the TIPC protocol implementation in the Linux kernel did not properly validate passed encryption key sizes. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-29646)
It was discovered that a race condition existed in the netfilter subsystem of the Linux kernel when replacing tables. A local attacker could use this to cause a denial of service (system crash). (CVE-2021-29650)
- Record
USN-4949-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
linuxDebian:12 |
before 5.10.38-1 | 5.10.38-1 |
linuxDebian:13 |
before 5.10.38-1 | 5.10.38-1 |
linuxDebian:14 |
before 5.10.38-1 | 5.10.38-1 |
:linux_kernel:Android |
:0 up to :2021-10-05, plus listed versions Kernel |
:2021-10-05 |
kernel-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-source-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-syms-azureSUSE:Linux Enterprise Module for Public Cloud 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-64kbSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-defaultSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-default-baseSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2.18.2.2 | 5.3.18-59.5.2.18.2.2 |
Show 51 moreShow less
| Package | Affected | Fixed |
|---|---|---|
kernel-preemptSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-sourceSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-zfcpdumpSUSE:Linux Enterprise Module for Basesystem 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-docsSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-obs-buildSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.1 | 5.3.18-59.5.1 |
kernel-preemptSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-sourceSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-symsSUSE:Linux Enterprise Module for Development Tools 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.1 | 5.3.18-59.5.1 |
kernel-defaultSUSE:Linux Enterprise Module for Legacy 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-defaultSUSE:Linux Enterprise Live Patching 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-livepatch-SLE15-SP3_Update_1SUSE:Linux Enterprise Live Patching 15 SP3 From an advisory covering 52 CVEs |
before 1-7.5.1 | 1-7.5.1 |
kernel-defaultSUSE:Linux Enterprise High Availability Extension 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-defaultSUSE:Linux Enterprise Workstation Extension 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-preemptSUSE:Linux Enterprise Workstation Extension 15 SP3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-livepatch-SLE15-SP3_Update_0SUSE:Linux Enterprise Live Patching 15 SP3 From an advisory covering 7 CVEs |
before 2-3.1 | 2-3.1 |
linux-hwe-edgeUbuntu:16.04:LTS |
All versions, plus listed versions 4.8.0-28.30~16.04.14.8.0-30.32~16.04.14.8.0-32.34~16.04.14.8.0-34.36~16.04.14.10.0-14.16~16.04.1 Show 18 moreShow less4.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.34.13.0-17.20~16.04.14.13.0-19.22~16.04.14.13.0-21.24~16.04.14.13.0-25.29~16.04.24.15.0-13.14~16.04.14.15.0-15.16~16.04.14.15.0-20.21~16.04.14.15.0-22.24~16.04.14.15.0-23.25~16.04.1 |
None known |
linux-aws-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1021.24~18.04.15.0.0-1022.25~18.04.15.0.0-1023.26~18.04.15.0.0-1024.27~18.04.15.0.0-1025.285.0.0-1027.30 |
None known |
linux-aws-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1019.21~18.04.15.3.0-1023.25~18.04.15.3.0-1028.30~18.04.1 Show 5 moreShow less5.3.0-1030.32~18.04.15.3.0-1032.34~18.04.25.3.0-1033.355.3.0-1034.365.3.0-1035.37 |
None known |
linux-azureUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1002.24.15.0-1003.34.15.0-1004.44.15.0-1008.84.15.0-1009.9 Show 39 moreShow less4.15.0-1012.124.15.0-1013.134.15.0-1014.144.15.0-1018.184.15.0-1019.194.15.0-1021.214.15.0-1022.234.15.0-1023.244.15.0-1025.264.15.0-1028.294.15.0-1030.314.15.0-1031.324.15.0-1032.334.15.0-1035.364.15.0-1036.384.15.0-1037.394.18.0-1011.11~18.04.14.18.0-1013.13~18.04.14.18.0-1014.14~18.04.14.18.0-1018.18~18.04.14.18.0-1019.19~18.04.14.18.0-1020.20~18.04.14.18.0-1023.24~18.04.14.18.0-1024.25~18.04.14.18.0-1025.27~18.04.15.0.0-1014.14~18.04.15.0.0-1016.17~18.04.15.0.0-1018.19~18.04.15.0.0-1020.21~18.04.15.0.0-1022.23~18.04.15.0.0-1023.24~18.04.15.0.0-1025.27~18.04.15.0.0-1027.29~18.04.15.0.0-1028.30~18.04.15.0.0-1029.31~18.04.15.0.0-1031.335.0.0-1032.345.0.0-1035.375.0.0-1036.38 |
None known |
linux-azure-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1007.8~18.04.15.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.1 Show 11 moreShow less5.3.0-1013.14~18.04.15.3.0-1016.17~18.04.15.3.0-1018.19~18.04.15.3.0-1019.20~18.04.15.3.0-1020.21~18.04.15.3.0-1022.23~18.04.15.3.0-1028.29~18.04.15.3.0-1031.32~18.04.15.3.0-1032.33~18.04.15.3.0-1034.35~18.04.15.3.0-1035.36 |
None known |
linux-azure-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-1006.6~18.04.14.18.0-1007.7~18.04.14.18.0-1008.8~18.04.15.0.0-1012.12~18.04.2 |
None known |
linux-gcpUbuntu:18.04:LTS |
All versions, plus listed versions 4.15.0-1001.14.15.0-1003.34.15.0-1005.54.15.0-1006.64.15.0-1008.8 Show 33 moreShow less4.15.0-1009.94.15.0-1010.104.15.0-1014.144.15.0-1015.154.15.0-1017.184.15.0-1018.194.15.0-1019.204.15.0-1021.224.15.0-1023.244.15.0-1024.254.15.0-1025.264.15.0-1026.274.15.0-1027.284.15.0-1028.294.15.0-1029.314.15.0-1030.324.15.0-1032.344.15.0-1033.354.15.0-1034.364.15.0-1036.384.15.0-1037.394.15.0-1040.424.15.0-1042.454.15.0-1044.705.0.0-1020.20~18.04.15.0.0-1021.21~18.04.15.0.0-1025.26~18.04.15.0.0-1026.27~18.04.15.0.0-1028.29~18.04.15.0.0-1029.30~18.04.15.0.0-1031.325.0.0-1033.345.0.0-1034.35 |
None known |
linux-gcp-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1008.9~18.04.15.3.0-1009.10~18.04.15.3.0-1010.11~18.04.15.3.0-1012.13~18.04.15.3.0-1014.15~18.04.1 Show 8 moreShow less5.3.0-1016.17~18.04.15.3.0-1017.18~18.04.15.3.0-1018.19~18.04.15.3.0-1020.22~18.04.15.3.0-1026.28~18.04.15.3.0-1029.31~18.04.15.3.0-1030.32~18.04.15.3.0-1032.34~18.04.1 |
None known |
linux-gcp-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-1004.5~18.04.14.18.0-1005.6~18.04.14.18.0-1006.7~18.04.14.18.0-1007.8~18.04.14.18.0-1008.9~18.04.1 Show 7 moreShow less4.18.0-1009.10~18.04.14.18.0-1011.12~18.04.14.18.0-1012.13~18.04.14.18.0-1013.14~18.04.14.18.0-1015.16~18.04.15.0.0-1011.11~18.04.15.0.0-1013.13~18.04.1 |
None known |
linux-hweUbuntu:18.04:LTS |
All versions, plus listed versions 4.18.0-13.14~18.04.14.18.0-14.15~18.04.14.18.0-15.16~18.04.14.18.0-16.17~18.04.14.18.0-17.18~18.04.1 Show 38 moreShow less4.18.0-18.19~18.04.14.18.0-20.21~18.04.14.18.0-21.22~18.04.14.18.0-22.23~18.04.14.18.0-24.25~18.04.14.18.0-25.26~18.04.15.0.0-23.24~18.04.15.0.0-25.26~18.04.15.0.0-27.28~18.04.15.0.0-29.31~18.04.15.0.0-31.33~18.04.15.0.0-32.34~18.04.25.0.0-35.38~18.04.15.0.0-36.39~18.04.15.0.0-37.40~18.04.15.3.0-26.28~18.04.15.3.0-28.30~18.04.15.3.0-40.32~18.04.15.3.0-42.34~18.04.15.3.0-45.37~18.04.15.3.0-46.38~18.04.15.3.0-51.44~18.04.25.3.0-53.47~18.04.15.3.0-59.53~18.04.15.3.0-61.55~18.04.15.3.0-62.56~18.04.15.3.0-64.58~18.04.15.3.0-65.595.3.0-66.605.3.0-67.615.3.0-68.635.3.0-69.655.3.0-70.665.3.0-72.685.3.0-73.695.3.0-74.705.3.0-75.715.3.0-76.72 |
None known |
linux-hwe-edgeUbuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-15.16~18.04.15.0.0-16.17~18.04.15.0.0-17.18~18.04.15.0.0-19.20~18.04.15.0.0-20.21~18.04.1 Show 5 moreShow less5.3.0-19.20~18.04.25.3.0-22.24~18.04.15.3.0-23.25~18.04.15.3.0-23.25~18.04.25.3.0-24.26~18.04.2 |
None known |
linux-oracle-5.0Ubuntu:18.04:LTS |
All versions, plus listed versions 5.0.0-1007.12~18.04.15.0.0-1008.13~18.04.15.0.0-1009.14~18.04.15.0.0-1010.15~18.04.15.0.0-1011.165.0.0-1013.185.0.0-1014.19 |
None known |
linux-oracle-5.3Ubuntu:18.04:LTS |
All versions, plus listed versions 5.3.0-1011.12~18.04.15.3.0-1013.14~18.04.15.3.0-1014.15~18.04.15.3.0-1016.18~18.04.15.3.0-1018.20~18.04.1 Show 4 moreShow less5.3.0-1024.26~18.04.15.3.0-1027.29~18.04.15.3.0-1028.30~18.04.15.3.0-1030.32~18.04.1 |
None known |
linux-hwe-5.8Ubuntu:20.04:LTS |
before 5.8.0-53.60~20.04.1, plus listed versions 5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1 Show 12 moreShow less5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.1 |
5.8.0-53.60~20.04.1 |
linux-oem-5.10Ubuntu:20.04:LTS |
before 5.10.0-1026.27, plus listed versions 5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17 Show 6 moreShow less5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.26 |
5.10.0-1026.27 |
linux-riscv-5.8Ubuntu:20.04:LTS |
before 5.8.0-25.27~20.04.1, plus listed versions 5.8.0-14.16~20.04.15.8.0-14.16~20.04.35.8.0-16.18~20.04.15.8.0-17.19~20.04.15.8.0-18.20~20.04.15.8.0-20.22~20.04.15.8.0-22.24~20.04.1 |
5.8.0-25.27~20.04.1 |
linux-raspi2Ubuntu:20.04:LTS |
All versions, plus listed versions 5.3.0-1007.85.3.0-1014.165.3.0-1015.175.3.0-1017.195.4.0-1004.45.4.0-1006.6 |
None known |
linux-oem-5.10Ubuntu:20.04:LTS From an advisory covering 21 CVEs |
before 5.10.0-1026.27, plus listed versions 5.10.0-1008.95.10.0-1011.125.10.0-1013.145.10.0-1014.155.10.0-1016.17 Show 6 moreShow less5.10.0-1017.185.10.0-1019.205.10.0-1021.225.10.0-1022.235.10.0-1023.245.10.0-1025.26 |
5.10.0-1026.27 |
linux-hwe-5.8Ubuntu:20.04:LTS From an advisory covering 12 CVEs |
before 5.8.0-53.60~20.04.1, plus listed versions 5.8.0-23.24~20.04.15.8.0-25.26~20.04.15.8.0-28.30~20.04.15.8.0-29.31~20.04.15.8.0-31.33~20.04.1 Show 12 moreShow less5.8.0-33.36~20.04.15.8.0-34.37~20.04.25.8.0-36.40~20.04.15.8.0-38.43~20.04.15.8.0-40.45~20.04.15.8.0-41.46~20.04.15.8.0-43.49~20.04.15.8.0-44.50~20.04.15.8.0-45.51~20.04.15.8.0-48.54~20.04.15.8.0-49.55~20.04.15.8.0-50.56~20.04.1 |
5.8.0-53.60~20.04.1 |
kernel-azureopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-source-azureopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-syms-azureopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-38.3.1 | 5.3.18-38.3.1 |
kernel-64kbopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-debugopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-defaultopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-default-baseopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2.18.2.2 | 5.3.18-59.5.2.18.2.2 |
kernel-docsopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-kvmsmallopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-obs-buildopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.1 | 5.3.18-59.5.1 |
kernel-obs-qaopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.1 | 5.3.18-59.5.1 |
kernel-preemptopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-sourceopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-symsopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.1 | 5.3.18-59.5.1 |
kernel-zfcpdumpopenSUSE:Leap 15.3 From an advisory covering 52 CVEs |
before 5.3.18-59.5.2 | 5.3.18-59.5.2 |
kernel-sourceopenSUSE:Tumbleweed From an advisory covering 119 CVEs |
before 5.14.6-1.4 | 5.14.6-1.4 |
kernel-sourceopenSUSE:Tumbleweed From an advisory covering 194 CVEs |
before 6.6.17-1.1 | 6.6.17-1.1 |
Public exploits
Links only. Every CVE stores no exploit code.
| Source | Link | Date |
|---|---|---|
| Metasploit | Linux eBPF ALU32 32-bit Invalid Bounds Tracking LPE | 2021-05-11 |
| PoC in GitHub | chompie1337/Linux_LPE_eBPF_CVE-2021-3490 | 2021-06-24 |
| PoC in GitHub | pivik271/CVE-2021-3490 | 2023-04-06 |
| PoC in GitHub | sandesh9978/cve-2021-3490-ebpf-analysis | 2026-03-03 |
| PoC in GitHub | prabeershakya/CVE-2021-3490-POC | 2026-03-04 |
| PoC in GitHub | WhatsWrongAndWhy/CVE-2021-3490 | 2026-07-21 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected | ||
| exploits, facts | OSV | |
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, Metasploit, NVD, OSV, PoC in GitHub |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2021-3490 is a high vulnerability (CVSS 7.8) in Linux Kernel, published May 11, 2021. Public exploit code exists. EPSS puts the chance of exploitation in the next 30 days at 27.4%, the 98th percentile. Fixed in linux 5.10.38-1.
References
ubuntu.com/security/notices/USN-4950-1
ubuntu.com/security/notices/USN-4949-1
openwall.com/lists/oss-security/2021/05/11/11
git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit?id=049c4e13714ecbca567b4d5f6d563f05d431c80e
zerodayinitiative.com/advisories/ZDI-21-606
security.netapp.com/advisory/ntap-20210716-0004
Show 194 moreShow less
packetstormsecurity.com/files/164015/Linux-eBPF-ALU32-32-bit-Invalid-Bounds-Tracking-Local-Privilege-Escalation.html
nvd.nist.gov/vuln/detail/CVE-2021-3490
github.com/advisories/GHSA-9wfm-q59x-qc3x
security-tracker.debian.org/tracker/CVE-2021-3490
source.android.com/security/bulletin/2021-10-01
android.googlesource.com/kernel/common/+/049c4e13714ecbca567b4d5f6d563f05d431c80e
suse.com/support/update/announcement/2021/suse-su-20211975-1
bugzilla.suse.com/1043990
bugzilla.suse.com/1047233
bugzilla.suse.com/1055117
bugzilla.suse.com/1065729
bugzilla.suse.com/1087082
bugzilla.suse.com/1113295
bugzilla.suse.com/1133021
bugzilla.suse.com/1152457
bugzilla.suse.com/1152472
bugzilla.suse.com/1152489
bugzilla.suse.com/1153274
bugzilla.suse.com/1154353
bugzilla.suse.com/1155518
bugzilla.suse.com/1156256
bugzilla.suse.com/1156395
bugzilla.suse.com/1159280
bugzilla.suse.com/1160634
bugzilla.suse.com/1164648
bugzilla.suse.com/1167260
bugzilla.suse.com/1167574
bugzilla.suse.com/1167773
bugzilla.suse.com/1168777
bugzilla.suse.com/1168838
bugzilla.suse.com/1169709
bugzilla.suse.com/1171295
bugzilla.suse.com/1173485
bugzilla.suse.com/1174416
bugzilla.suse.com/1174426
bugzilla.suse.com/1175995
bugzilla.suse.com/1176447
bugzilla.suse.com/1176774
bugzilla.suse.com/1177028
bugzilla.suse.com/1177326
bugzilla.suse.com/1177411
bugzilla.suse.com/1177437
bugzilla.suse.com/1177666
bugzilla.suse.com/1178089
bugzilla.suse.com/1178134
bugzilla.suse.com/1178163
bugzilla.suse.com/1178181
bugzilla.suse.com/1178330
bugzilla.suse.com/1178378
bugzilla.suse.com/1178418
bugzilla.suse.com/1178612
bugzilla.suse.com/1179243
bugzilla.suse.com/1179454
bugzilla.suse.com/1179458
bugzilla.suse.com/1179519
bugzilla.suse.com/1179825
bugzilla.suse.com/1179827
bugzilla.suse.com/1179851
bugzilla.suse.com/1180100
bugzilla.suse.com/1180197
bugzilla.suse.com/1180814
bugzilla.suse.com/1180846
bugzilla.suse.com/1180980
bugzilla.suse.com/1181104
bugzilla.suse.com/1181161
bugzilla.suse.com/1181383
bugzilla.suse.com/1181507
bugzilla.suse.com/1181674
bugzilla.suse.com/1181862
bugzilla.suse.com/1182077
bugzilla.suse.com/1182257
bugzilla.suse.com/1182377
bugzilla.suse.com/1182378
bugzilla.suse.com/1182552
bugzilla.suse.com/1182574
bugzilla.suse.com/1182591
bugzilla.suse.com/1182613
bugzilla.suse.com/1182712
bugzilla.suse.com/1182713
bugzilla.suse.com/1182715
bugzilla.suse.com/1182716
bugzilla.suse.com/1182717
bugzilla.suse.com/1182999
bugzilla.suse.com/1183022
bugzilla.suse.com/1183048
bugzilla.suse.com/1183069
suse.com/security/cve/CVE-2019-18814
suse.com/security/cve/CVE-2019-19769
suse.com/security/cve/CVE-2020-24586
suse.com/security/cve/CVE-2020-24587
suse.com/security/cve/CVE-2020-24588
suse.com/security/cve/CVE-2020-25670
suse.com/security/cve/CVE-2020-25671
suse.com/security/cve/CVE-2020-25672
suse.com/security/cve/CVE-2020-25673
suse.com/security/cve/CVE-2020-26139
suse.com/security/cve/CVE-2020-26141
suse.com/security/cve/CVE-2020-26145
suse.com/security/cve/CVE-2020-26147
suse.com/security/cve/CVE-2020-27170
suse.com/security/cve/CVE-2020-27171
suse.com/security/cve/CVE-2020-27673
suse.com/security/cve/CVE-2020-27815
suse.com/security/cve/CVE-2020-35519
suse.com/security/cve/CVE-2020-36310
suse.com/security/cve/CVE-2020-36311
suse.com/security/cve/CVE-2020-36312
suse.com/security/cve/CVE-2020-36322
suse.com/security/cve/CVE-2021-20268
suse.com/security/cve/CVE-2021-23134
suse.com/security/cve/CVE-2021-27363
suse.com/security/cve/CVE-2021-27364
suse.com/security/cve/CVE-2021-27365
suse.com/security/cve/CVE-2021-28038
suse.com/security/cve/CVE-2021-28375
suse.com/security/cve/CVE-2021-28660
suse.com/security/cve/CVE-2021-28688
suse.com/security/cve/CVE-2021-28950
suse.com/security/cve/CVE-2021-28952
suse.com/security/cve/CVE-2021-28964
suse.com/security/cve/CVE-2021-28971
suse.com/security/cve/CVE-2021-28972
suse.com/security/cve/CVE-2021-29154
suse.com/security/cve/CVE-2021-29155
suse.com/security/cve/CVE-2021-29264
suse.com/security/cve/CVE-2021-29265
suse.com/security/cve/CVE-2021-29647
suse.com/security/cve/CVE-2021-29650
suse.com/security/cve/CVE-2021-30002
suse.com/security/cve/CVE-2021-32399
suse.com/security/cve/CVE-2021-33034
suse.com/security/cve/CVE-2021-33200
suse.com/security/cve/CVE-2021-3428
suse.com/security/cve/CVE-2021-3444
suse.com/security/cve/CVE-2021-3483
suse.com/security/cve/CVE-2021-3489
suse.com/security/cve/CVE-2021-3490
suse.com/security/cve/CVE-2021-3491
suse.com/support/update/announcement/2021/suse-su-20211977-1
suse.com/support/update/announcement/2021/suse-su-20212198-1
ubuntu.com/security/CVE-2021-3490
ubuntu.com/security/notices/USN-4948-1
cve.org/CVERecord?id=CVE-2021-3490
ubuntu.com/security/CVE-2020-25670
ubuntu.com/security/CVE-2020-25671
ubuntu.com/security/CVE-2020-25672
ubuntu.com/security/CVE-2021-3483
ubuntu.com/security/CVE-2021-3489
ubuntu.com/security/CVE-2021-3491
ubuntu.com/security/CVE-2021-28688
ubuntu.com/security/CVE-2021-28951
ubuntu.com/security/CVE-2021-28952
ubuntu.com/security/CVE-2021-28964
ubuntu.com/security/CVE-2021-28971
ubuntu.com/security/CVE-2021-28972
ubuntu.com/security/CVE-2021-29264
ubuntu.com/security/CVE-2021-29266
ubuntu.com/security/CVE-2021-29646
ubuntu.com/security/CVE-2021-29647
ubuntu.com/security/CVE-2021-29649
ubuntu.com/security/CVE-2021-29650
ubuntu.com/security/CVE-2021-29657
ubuntu.com/security/CVE-2021-31916
ubuntu.com/security/CVE-2020-25639
ubuntu.com/security/CVE-2021-26930
ubuntu.com/security/CVE-2021-26931
ubuntu.com/security/CVE-2021-28375
ubuntu.com/security/CVE-2021-29265
lists.opensuse.org/archives/list/[email protected]/thread/42KHRU57J2OGM24I4AOZ7JW6VV2BOPCV
lists.opensuse.org/archives/list/[email protected]/thread/YMMFY2OXW23MB2M73JXBDJKJD5G5YCOX
suse.com/security/cve/CVE-2017-1000251
suse.com/security/cve/CVE-2017-12153
suse.com/security/cve/CVE-2017-13080
suse.com/security/cve/CVE-2017-14051
suse.com/security/cve/CVE-2017-15129
suse.com/security/cve/CVE-2017-15265
suse.com/security/cve/CVE-2017-16536
suse.com/security/cve/CVE-2017-16537
suse.com/security/cve/CVE-2017-16645
suse.com/security/cve/CVE-2017-16646
suse.com/security/cve/CVE-2017-16647
suse.com/security/cve/CVE-2017-16648
suse.com/security/cve/CVE-2017-16995
suse.com/security/cve/CVE-2017-16996
suse.com/security/cve/CVE-2017-17448
suse.com/security/cve/CVE-2017-17449
suse.com/security/cve/CVE-2017-17450
suse.com/security/cve/CVE-2017-17852
suse.com/security/cve/CVE-2017-17853
suse.com/security/cve/CVE-2017-17854
suse.com/security/cve/CVE-2017-17855
suse.com/security/cve/CVE-2017-17856
suse.com/security/cve/CVE-2017-17857
suse.com/security/cve/CVE-2017-17862
Left out here: 386 references and the rest of 5 source descriptions. The JSON record has them.