OESA-2023-1268 (CVE-2023-1855)
Vulnerability from osv_openeuler – Published: 2023-04-28 11:05 – Updated: 2026-08-06 11:05 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
A use-after-free flaw was found in xgene_hwmon_remove in drivers/hwmon/xgene-hwmon.c in the Hardware Monitoring Linux Kernel Driver (xgene-hwmon). This flaw could allow a local attacker to crash the system due to a race problem. This vulnerability could even lead to a kernel information leak problem.(CVE-2023-1855)
A use-after-free flaw was found in ndlc_remove in drivers/nfc/st-nci/ndlc.c in the Linux Kernel. This flaw could allow an attacker to crash the system due to a race problem.(CVE-2023-1990)
A use-after-free vulnerability in the Linux Kernel io_uring system can be exploited to achieve local privilege escalation.
The io_file_get_fixed function lacks the presence of ctx->uring_lock which can lead to a Use-After-Free vulnerability due a race condition with fixed files getting unregistered.
We recommend upgrading past commit da24142b1ef9fd5d36b76e36bab328a5b27523e8.
(CVE-2023-1872)
A race condition was found in the Linux kernel's RxRPC network protocol, within the processing of RxRPC bundles. This issue results from the lack of proper locking when performing operations on an object. This may allow an attacker to escalate privileges and execute arbitrary code in the context of the kernel.(CVE-2023-2006)
The Linux kernel before 6.2.9 has a race condition and resultant use-after-free in drivers/power/supply/da9150-charger.c if a physically proximate attacker unplugs a device.(CVE-2023-30772)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-tools-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-source-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"python3-perf-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-debuginfo-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-devel-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-debugsource-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"bpftool-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"perf-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"bpftool-debuginfo-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-tools-devel-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"kernel-headers-5.10.0-60.92.0.116.oe2203.aarch64.rpm",
"perf-debuginfo-5.10.0-60.92.0.116.oe2203.aarch64.rpm"
],
"src": [
"kernel-5.10.0-60.92.0.116.oe2203.src.rpm"
],
"x86_64": [
"kernel-debuginfo-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"python3-perf-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"perf-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"perf-debuginfo-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-devel-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-source-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-headers-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-tools-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"bpftool-debuginfo-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-tools-devel-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"bpftool-5.10.0-60.92.0.116.oe2203.x86_64.rpm",
"kernel-debugsource-5.10.0-60.92.0.116.oe2203.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-60.92.0.116.oe2203"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nA use-after-free flaw was found in xgene_hwmon_remove in drivers/hwmon/xgene-hwmon.c in the Hardware Monitoring Linux Kernel Driver (xgene-hwmon). This flaw could allow a local attacker to crash the system due to a race problem. This vulnerability could even lead to a kernel information leak problem.(CVE-2023-1855)\r\n\r\nA use-after-free flaw was found in ndlc_remove in drivers/nfc/st-nci/ndlc.c in the Linux Kernel. This flaw could allow an attacker to crash the system due to a race problem.(CVE-2023-1990)\r\n\r\nA use-after-free vulnerability in the Linux Kernel io_uring system can be exploited to achieve local privilege escalation.\r\n\r\nThe io_file_get_fixed function lacks the presence of ctx-\u0026gt;uring_lock which can lead to a Use-After-Free vulnerability due a race condition with fixed files getting unregistered.\r\n\r\nWe recommend upgrading past commit da24142b1ef9fd5d36b76e36bab328a5b27523e8.\r\n\r\n(CVE-2023-1872)\r\n\r\nA race condition was found in the Linux kernel\u0026apos;s RxRPC network protocol, within the processing of RxRPC bundles. This issue results from the lack of proper locking when performing operations on an object. This may allow an attacker to escalate privileges and execute arbitrary code in the context of the kernel.(CVE-2023-2006)\r\n\r\nThe Linux kernel before 6.2.9 has a race condition and resultant use-after-free in drivers/power/supply/da9150-charger.c if a physically proximate attacker unplugs a device.(CVE-2023-30772)",
"id": "OESA-2023-1268",
"modified": "2026-08-06T11:05:44Z",
"published": "2023-04-28T11:05:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1268"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1855"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1990"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1872"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-2006"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-30772"
}
],
"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-2023-1855",
"CVE-2023-1990",
"CVE-2023-1872",
"CVE-2023-2006",
"CVE-2023-30772"
]
}
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.