OESA-2023-1439 (CVE-2023-1295)
Vulnerability from osv_openeuler – Published: 2023-07-21 11:05 – Updated: 2026-08-06 11:05 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
A time-of-check to time-of-use issue exists in io_uring subsystem's IORING_OP_CLOSE operation in the Linux kernel's versions 5.6 - 5.11 (inclusive), which allows a local user to elevate their privileges to root. Introduced in b5dba59e0cf7e2cc4d3b3b1ac5fe81ddf21959eb, patched in 9eac1904d3364254d622bf2c771c4f85cd435fc2, backported to stable in 788d0824269bef539fe31a785b1517882eafed93.(CVE-2023-1295)
A heap out-of-bounds write vulnerability in the Linux Kernel ipvlan network driver can be exploited to achieve local privilege escalation.
The out-of-bounds write is caused by missing skb->cb initialization in the ipvlan network driver. The vulnerability is reachable if CONFIG_IPVLAN is enabled.
We recommend upgrading past commit 90cbed5247439a966b645b34eb0a2e037836ea8e.
(CVE-2023-3090)
A use-after-free flaw was found in the Netfilter subsystem of the Linux kernel when processing named and anonymous sets in batch requests, which can lead to performing arbitrary reads and writes in kernel memory. This flaw allows a local user with CAP_NET_ADMIN capability to crash or potentially escalate their privileges on the system.(CVE-2023-3117)
An issue was discovered in the Linux kernel through 6.1-rc8. dpu_crtc_atomic_check in drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c lacks check of the return value of kzalloc() and will cause the NULL Pointer Dereference.(CVE-2023-3220)
A flaw null pointer dereference in the Linux kernel DECnet networking protocol was found. A remote user could use this flaw to crash the system.(CVE-2023-3338)
A null pointer dereference was found in the Linux kernel's Integrated Sensor Hub (ISH) driver. This issue could allow a local user to crash the system.(CVE-2023-3358)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-devel-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-tools-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-tools-devel-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-debugsource-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"perf-debuginfo-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"python2-perf-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"perf-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"kernel-source-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"python3-perf-4.19.90-2307.4.0.0210.oe1.aarch64.rpm",
"bpftool-4.19.90-2307.4.0.0210.oe1.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2307.4.0.0210.oe1.src.rpm"
],
"x86_64": [
"perf-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"python2-perf-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"bpftool-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-debugsource-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-tools-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"perf-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-tools-devel-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"python3-perf-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-devel-4.19.90-2307.4.0.0210.oe1.x86_64.rpm",
"kernel-source-4.19.90-2307.4.0.0210.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-2307.4.0.0210.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "The Linux Kernel, the operating system core itself.\n\nSecurity Fix(es):\n\nA time-of-check to time-of-use issue exists in io_uring subsystem\u0026apos;s IORING_OP_CLOSE operation in the Linux kernel\u0026apos;s versions 5.6 - 5.11 (inclusive), which allows a local user to elevate their privileges to root. Introduced in b5dba59e0cf7e2cc4d3b3b1ac5fe81ddf21959eb, patched in 9eac1904d3364254d622bf2c771c4f85cd435fc2, backported to stable in 788d0824269bef539fe31a785b1517882eafed93.(CVE-2023-1295)\n\nA heap out-of-bounds write vulnerability in the Linux Kernel ipvlan network driver can be exploited to achieve local privilege escalation.\n\nThe out-of-bounds write is caused by missing skb-\u0026gt;cb initialization in the ipvlan network driver. The vulnerability is reachable if\u00a0CONFIG_IPVLAN is enabled.\n\n\nWe recommend upgrading past commit 90cbed5247439a966b645b34eb0a2e037836ea8e.\n\n(CVE-2023-3090)\n\nA use-after-free flaw was found in the Netfilter subsystem of the Linux kernel when processing named and anonymous sets in batch requests, which can lead to performing arbitrary reads and writes in kernel memory. This flaw allows a local user with CAP_NET_ADMIN capability to crash or potentially escalate their privileges on the system.(CVE-2023-3117)\n\nAn issue was discovered in the Linux kernel through 6.1-rc8. dpu_crtc_atomic_check in drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c lacks check of the return value of kzalloc() and will cause the NULL Pointer Dereference.(CVE-2023-3220)\n\nA flaw null pointer dereference in the Linux kernel DECnet networking protocol was found. A remote user could use this flaw to crash the system.(CVE-2023-3338)\n\nA null pointer dereference was found in the Linux kernel\u0026apos;s Integrated Sensor Hub (ISH) driver. This issue could allow a local user to crash the system.(CVE-2023-3358)",
"id": "OESA-2023-1439",
"modified": "2026-08-06T11:05:54Z",
"published": "2023-07-21T11:05:54Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1439"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1295"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3090"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3117"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3220"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3338"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-3358"
}
],
"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-1295",
"CVE-2023-3090",
"CVE-2023-3117",
"CVE-2023-3220",
"CVE-2023-3338",
"CVE-2023-3358"
]
}
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.