OESA-2022-2161 (CVE-2022-20568)
Vulnerability from osv_openeuler – Published: 2022-12-30 11:05 – Updated: 2026-08-06 11:05 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In (TBD) of (TBD), there is a possible way to corrupt kernel memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-220738351References: Upstream kernel(CVE-2022-20568)
In verity_target of dm-verity-target.c, there is a possible way to modify read-only files due to a missing permission check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-234475629References: Upstream kernel(CVE-2022-20572)
In drivers/media/dvb-core/dmxdev.c in the Linux kernel through 5.19.10, there is a use-after-free caused by refcount races, affecting dvb_demux_open and dvb_dmxdev_release.(CVE-2022-41218)
An issue was discovered in the Linux kernel through 5.16-rc6. malidp_crtc_reset in drivers/gpu/drm/arm/malidp_crtc.c lacks check of the return value of kzalloc() and will cause the null pointer dereference.(CVE-2022-3115)
An issue was discovered in the Linux kernel through 5.16-rc6. free_charger_irq() in drivers/power/supply/wm8350_power.c lacks free of WM8350_IRQ_CHG_FAST_RDY, which is registered in wm8350_init_charger().(CVE-2022-3111)
An issue was discovered in the Linux kernel through 5.16-rc6. kfd_parse_subtype_iolink in drivers/gpu/drm/amd/amdkfd/kfd_crat.c lacks check of the return value of kmemdup().(CVE-2022-3108)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"bpftool-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-devel-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"python2-perf-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"perf-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"python3-perf-4.19.90-2212.4.0.0183.oe1.aarch64.rpm",
"kernel-source-4.19.90-2212.4.0.0183.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2212.4.0.0183.oe1.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"python2-perf-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"python3-perf-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"perf-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-source-4.19.90-2212.4.0.0183.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2212.4.0.0183.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP3",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2212.4.0.0183.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nIn (TBD) of (TBD), there is a possible way to corrupt kernel memory due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-220738351References: Upstream kernel(CVE-2022-20568)\r\n\r\nIn verity_target of dm-verity-target.c, there is a possible way to modify read-only files due to a missing permission check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-234475629References: Upstream kernel(CVE-2022-20572)\n\nIn drivers/media/dvb-core/dmxdev.c in the Linux kernel through 5.19.10, there is a use-after-free caused by refcount races, affecting dvb_demux_open and dvb_dmxdev_release.(CVE-2022-41218)\n\nAn issue was discovered in the Linux kernel through 5.16-rc6. malidp_crtc_reset in drivers/gpu/drm/arm/malidp_crtc.c lacks check of the return value of kzalloc() and will cause the null pointer dereference.(CVE-2022-3115)\n\nAn issue was discovered in the Linux kernel through 5.16-rc6. free_charger_irq() in drivers/power/supply/wm8350_power.c lacks free of WM8350_IRQ_CHG_FAST_RDY, which is registered in wm8350_init_charger().(CVE-2022-3111)\n\nAn issue was discovered in the Linux kernel through 5.16-rc6. kfd_parse_subtype_iolink in drivers/gpu/drm/amd/amdkfd/kfd_crat.c lacks check of the return value of kmemdup().(CVE-2022-3108)",
"id": "OESA-2022-2161",
"modified": "2026-08-06T11:05:28Z",
"published": "2022-12-30T11:05:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-2161"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-20568"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-20572"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-41218"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3115"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3111"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-3108"
}
],
"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-2022-20568",
"CVE-2022-20572",
"CVE-2022-41218",
"CVE-2022-3115",
"CVE-2022-3111",
"CVE-2022-3108"
]
}
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.
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.