OESA-2026-1504 (CVE-2023-53577)
Vulnerability from osv_openeuler – Published: 2026-03-06 11:10 – Updated: 2026-08-06 11:10 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
bpf, cpumap: Make sure kthread is running before map update returns
The following warning was reported when running stress-mode enabled xdp_redirect_cpu with some RT threads:
------------[ cut here ]------------ WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135 CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events cpu_map_kthread_stop RIP: 0010:put_cpu_map_entry+0xda/0x220 ...... Call Trace: <TASK> ? show_regs+0x65/0x70 ? __warn+0xa5/0x240 ...... ? put_cpu_map_entry+0xda/0x220 cpu_map_kthread_stop+0x41/0x60 process_one_work+0x6b0/0xb80 worker_thread+0x96/0x720 kthread+0x1a5/0x1f0 ret_from_fork+0x3a/0x70 ret_from_fork_asm+0x1b/0x30 </TASK>
The root cause is the same as commit 436901649731 ("bpf: cpumap: Fix memory leak in cpu_map_update_elem"). The kthread is stopped prematurely by kthread_stop() in cpu_map_kthread_stop(), and kthread() doesn't call cpu_map_kthread_run() at all but XDP program has already queued some frames or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks the ptr_ring, it will find it was not emptied and report a warning.
An alternative fix is to use __cpu_map_ring_cleanup() to drop these pending frames or skbs when kthread_stop() returns -EINTR, but it may confuse the user, because these frames or skbs have been handled correctly by XDP program. So instead of dropping these frames or skbs, just make sure the per-cpu kthread is running before __cpu_map_entry_alloc() returns.
After apply the fix, the error handle for kthread_stop() will be unnecessary because it will always return 0, so just remove it.(CVE-2023-53577)
In the Linux kernel, the following vulnerability has been resolved:
scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()
In iscsit_dec_conn_usage_count(), the function calls complete() while holding the conn->conn_usage_lock. As soon as complete() is invoked, the waiter (such as iscsit_close_connection()) may wake up and proceed to free the iscsit_conn structure.
If the waiter frees the memory before the current thread reaches spin_unlock_bh(), it results in a KASAN slab-use-after-free as the function attempts to release a lock within the already-freed connection structure.
Fix this by releasing the spinlock before calling complete().(CVE-2026-23216)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"bpftool-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2603.1.0.0364.oe2003sp4.src.rpm"
],
"x86_64": [
"bpftool-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"python2-perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2603.1.0.0364.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "4.19.90-2603.1.0.0364.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf, cpumap: Make sure kthread is running before map update returns\n\nThe following warning was reported when running stress-mode enabled\nxdp_redirect_cpu with some RT threads:\n\n ------------[ cut here ]------------\n WARNING: CPU: 4 PID: 65 at kernel/bpf/cpumap.c:135\n CPU: 4 PID: 65 Comm: kworker/4:1 Not tainted 6.5.0-rc2+ #1\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996)\n Workqueue: events cpu_map_kthread_stop\n RIP: 0010:put_cpu_map_entry+0xda/0x220\n ......\n Call Trace:\n \u0026lt;TASK\u0026gt;\n ? show_regs+0x65/0x70\n ? __warn+0xa5/0x240\n ......\n ? put_cpu_map_entry+0xda/0x220\n cpu_map_kthread_stop+0x41/0x60\n process_one_work+0x6b0/0xb80\n worker_thread+0x96/0x720\n kthread+0x1a5/0x1f0\n ret_from_fork+0x3a/0x70\n ret_from_fork_asm+0x1b/0x30\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is the same as commit 436901649731 (\u0026quot;bpf: cpumap: Fix memory\nleak in cpu_map_update_elem\u0026quot;). The kthread is stopped prematurely by\nkthread_stop() in cpu_map_kthread_stop(), and kthread() doesn\u0026apos;t call\ncpu_map_kthread_run() at all but XDP program has already queued some\nframes or skbs into ptr_ring. So when __cpu_map_ring_cleanup() checks\nthe ptr_ring, it will find it was not emptied and report a warning.\n\nAn alternative fix is to use __cpu_map_ring_cleanup() to drop these\npending frames or skbs when kthread_stop() returns -EINTR, but it may\nconfuse the user, because these frames or skbs have been handled\ncorrectly by XDP program. So instead of dropping these frames or skbs,\njust make sure the per-cpu kthread is running before\n__cpu_map_entry_alloc() returns.\n\nAfter apply the fix, the error handle for kthread_stop() will be\nunnecessary because it will always return 0, so just remove it.(CVE-2023-53577)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)",
"id": "OESA-2026-1504",
"modified": "2026-08-06T11:10:31Z",
"published": "2026-03-06T11:10:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1504"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53577"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23216"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2023-53577",
"CVE-2026-23216"
]
}
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.