OESA-2021-1379 (CVE-2021-3669)
Vulnerability from osv_openeuler – Published: 2021-10-15 11:04 – Updated: 2026-08-06 11:04 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
A flaw was found in the Linux kernel. Measuring usage of the shared memory does not scale with large shared memory segment counts which could lead to resource exhaustion and DoS.(CVE-2021-3669)
(CVE-2021-3764)
(CVE-2021-3744)
arch/mips/net/bpf_jit.c in the Linux kernel before 5.4.10 can generate undesirable machine code when transforming unprivileged cBPF programs, allowing execution of arbitrary code within the kernel context. This occurs because conditional branches can exceed the 128 KB limit of the MIPS architecture.(CVE-2021-38300)
A use-after-free flaw was found in the Linux kernel's Bluetooth subsystem in the way user calls connect to the socket and disconnect simultaneously due to a race condition. This flaw allows a user to crash the system or escalate their privileges. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.(CVE-2021-3752)
A flaw was found in the Linux kernel. A corrupted timer tree caused the task wakeup to be missing in the timerqueue_add function in lib/timerqueue.c. This flaw allows a local attacker with special user privileges to cause a denial of service, slowing and eventually stopping the system while running OSP.(CVE-2021-20317)
prealloc_elems_and_freelist in kernel/bpf/stackmap.c in the Linux kernel through 5.14.9 allows unprivileged users to trigger an eBPF multiplication integer overflow with a resultant out-of-bounds write.(CVE-2021-41864)
The decode_data function in drivers/net/hamradio/6pack.c in the Linux kernel before 5.13.13 has a slab out-of-bounds write. Input from a process that has the CAP_NET_ADMIN capability can lead to root access.(CVE-2021-42008)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-devel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"bpftool-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python2-perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-source-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python3-perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2110.3.0.0116.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2110.3.0.0116.oe1.src.rpm"
],
"x86_64": [
"kernel-tools-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python2-perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-source-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"bpftool-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python3-perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2110.3.0.0116.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python2-perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python3-perf-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-source-4.19.90-2110.3.0.0116.oe1.aarch64.rpm",
"kernel-4.19.90-2110.3.0.0116.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2110.3.0.0116.oe1.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python3-perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python2-perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"perf-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2110.3.0.0116.oe1.x86_64.rpm",
"kernel-source-4.19.90-2110.3.0.0116.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP2",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2110.3.0.0116.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\n\r\n\r\nSecurity Fix(es):\r\n\r\nA flaw was found in the Linux kernel. Measuring usage of the shared memory does not scale with large shared memory segment counts which could lead to resource exhaustion and DoS.(CVE-2021-3669)\r\n\r\n(CVE-2021-3764)\r\n\r\n(CVE-2021-3744)\r\n\r\narch/mips/net/bpf_jit.c in the Linux kernel before 5.4.10 can generate undesirable machine code when transforming unprivileged cBPF programs, allowing execution of arbitrary code within the kernel context. This occurs because conditional branches can exceed the 128 KB limit of the MIPS architecture.(CVE-2021-38300)\r\n\r\nA use-after-free flaw was found in the Linux kernel\u0026apos;s Bluetooth subsystem in the way user calls connect to the socket and disconnect simultaneously due to a race condition. This flaw allows a user to crash the system or escalate their privileges. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.(CVE-2021-3752)\r\n\r\nA flaw was found in the Linux kernel. A corrupted timer tree caused the task wakeup to be missing in the timerqueue_add function in lib/timerqueue.c. This flaw allows a local attacker with special user privileges to cause a denial of service, slowing and eventually stopping the system while running OSP.(CVE-2021-20317)\r\n\r\nprealloc_elems_and_freelist in kernel/bpf/stackmap.c in the Linux kernel through 5.14.9 allows unprivileged users to trigger an eBPF multiplication integer overflow with a resultant out-of-bounds write.(CVE-2021-41864)\r\n\r\nThe decode_data function in drivers/net/hamradio/6pack.c in the Linux kernel before 5.13.13 has a slab out-of-bounds write. Input from a process that has the CAP_NET_ADMIN capability can lead to root access.(CVE-2021-42008)",
"id": "OESA-2021-1379",
"modified": "2026-08-06T11:04:39Z",
"published": "2021-10-15T11:04:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1379"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3669"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3764"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3744"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-38300"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-3752"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-20317"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-41864"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-42008"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2021-3669",
"CVE-2021-3764",
"CVE-2021-3744",
"CVE-2021-38300",
"CVE-2021-3752",
"CVE-2021-20317",
"CVE-2021-41864",
"CVE-2021-42008"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.