OESA-2021-1003 (CVE-2020-14351)
Vulnerability from osv_openeuler – Published: 2021-02-04 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. A use-after-free memory flaw was found in the perf subsystem allowing a local attacker with permission to monitor perf events to corrupt memory and possibly escalate privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.(CVE-2020-14351)
An issue was discovered in the Linux kernel through 5.9.1, as used with Xen through 4.14.x. drivers/xen/events/events_base.c allows event-channel removal during the event-handling loop (a race condition). This can cause a use-after-free or NULL pointer dereference, as demonstrated by a dom0 crash via events for an in-reconfiguration paravirtualized device, aka CID-073d0552ead5.(CVE-2020-27675)
A flaw was found in the Linux kernel. A use-after-free was found in the way the console subsystem was using ioctls KDGKBSENT and KDSKBSENT. A local user could use this flaw to get read memory access out of bounds. The highest threat from this vulnerability is to data confidentiality.(CVE-2020-25656)
Improper access control in BlueZ may allow an unauthenticated user to potentially enable information disclosure via adjacent access.(CVE-2020-12352)
A locking issue was discovered in the tty subsystem of the Linux kernel through 5.9.13. drivers/tty/tty_jobctrl.c allows a use-after-free attack against TIOCSPGRP, aka CID-54ffccbf053b.(CVE-2020-29661)
A flaw was found in the way RTAS handled memory accesses in userspace to kernel communication. On a locked down (usually due to Secure Boot) guest system running on top of PowerVM or KVM hypervisors (pseries platform) a root like local user could use this flaw to further increase their privileges to that of a running kernel.(CVE-2020-27777)
A locking inconsistency issue was discovered in the tty subsystem of the Linux kernel through 5.9.13. drivers/tty/tty_io.c and drivers/tty/tty_jobctrl.c may allow a read-after-free attack against TIOCGSID, aka CID-c8bcd9c5be24.(CVE-2020-29660)
An issue was discovered in the Linux kernel through 5.10.1, as used with Xen through 4.14.x. The Linux kernel PV block backend expects the kernel thread handler to reset ring->xenblkd to NULL when stopped. However, the handler may not have time to run if the frontend quickly toggles between the states connect and disconnect. As a consequence, the block backend may re-use a pointer after it was freed. A misbehaving guest can trigger a dom0 crash by continuously connecting / disconnecting a block frontend. Privilege escalation and information leaks cannot be ruled out. This only affects systems with a Linux blkback.(CVE-2020-29569)
A flaw was found in the JFS filesystem code. This flaw allows a local attacker with the ability to set extended attributes to panic the system, causing memory corruption or escalating privileges. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.(CVE-2020-27815)
A vulnerability was found in Linux Kernel where in the spk_ttyio_receive_buf2() function, it would dereference spk_ttyio_synth without checking whether it is NULL or not, and may lead to a NULL-ptr deref crash.(CVE-2020-27830)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"bpftool-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2101.1.0.0055.oe1.src.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"bpftool-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2101.1.0.0055.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2101.1.0.0055.oe1.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-source-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-4.19.90-2101.1.0.0055.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2101.1.0.0055.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-2101.1.0.0055.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\n\nSecurity Fix(es):\n\nA flaw was found in the Linux kernel. A use-after-free memory flaw was found in the perf subsystem allowing a local attacker with permission to monitor perf events to corrupt memory and possibly escalate privileges. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.(CVE-2020-14351)\n\nAn issue was discovered in the Linux kernel through 5.9.1, as used with Xen through 4.14.x. drivers/xen/events/events_base.c allows event-channel removal during the event-handling loop (a race condition). This can cause a use-after-free or NULL pointer dereference, as demonstrated by a dom0 crash via events for an in-reconfiguration paravirtualized device, aka CID-073d0552ead5.(CVE-2020-27675)\n\nA flaw was found in the Linux kernel. A use-after-free was found in the way the console subsystem was using ioctls KDGKBSENT and KDSKBSENT. A local user could use this flaw to get read memory access out of bounds. The highest threat from this vulnerability is to data confidentiality.(CVE-2020-25656)\n\nImproper access control in BlueZ may allow an unauthenticated user to potentially enable information disclosure via adjacent access.(CVE-2020-12352)\n\nA locking issue was discovered in the tty subsystem of the Linux kernel through 5.9.13. drivers/tty/tty_jobctrl.c allows a use-after-free attack against TIOCSPGRP, aka CID-54ffccbf053b.(CVE-2020-29661)\n\nA flaw was found in the way RTAS handled memory accesses in userspace to kernel communication. On a locked down (usually due to Secure Boot) guest system running on top of PowerVM or KVM hypervisors (pseries platform) a root like local user could use this flaw to further increase their privileges to that of a running kernel.(CVE-2020-27777)\n\nA locking inconsistency issue was discovered in the tty subsystem of the Linux kernel through 5.9.13. drivers/tty/tty_io.c and drivers/tty/tty_jobctrl.c may allow a read-after-free attack against TIOCGSID, aka CID-c8bcd9c5be24.(CVE-2020-29660)\n\nAn issue was discovered in the Linux kernel through 5.10.1, as used with Xen through 4.14.x. The Linux kernel PV block backend expects the kernel thread handler to reset ring-\u003exenblkd to NULL when stopped. However, the handler may not have time to run if the frontend quickly toggles between the states connect and disconnect. As a consequence, the block backend may re-use a pointer after it was freed. A misbehaving guest can trigger a dom0 crash by continuously connecting / disconnecting a block frontend. Privilege escalation and information leaks cannot be ruled out. This only affects systems with a Linux blkback.(CVE-2020-29569)\n\nA flaw was found in the JFS filesystem code. This flaw allows a local attacker with the ability to set extended attributes to panic the system, causing memory corruption or escalating privileges. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.(CVE-2020-27815)\n\nA vulnerability was found in Linux Kernel where in the spk_ttyio_receive_buf2() function, it would dereference spk_ttyio_synth without checking whether it is NULL or not, and may lead to a NULL-ptr deref crash.(CVE-2020-27830)",
"id": "OESA-2021-1003",
"modified": "2026-08-06T11:04:13Z",
"published": "2021-02-04T11:04:13Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1003"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-14351"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27675"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-25656"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-12352"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29661"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27777"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29660"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-29569"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27815"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-27830"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2020-14351",
"CVE-2020-27675",
"CVE-2020-25656",
"CVE-2020-12352",
"CVE-2020-29661",
"CVE-2020-27777",
"CVE-2020-29660",
"CVE-2020-29569",
"CVE-2020-27815",
"CVE-2020-27830"
]
}
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.