OESA-2023-1180 (CVE-2023-1074)
Vulnerability from osv_openeuler – Published: 2023-03-24 11:05 – Updated: 2026-08-06 11:05 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
A flaw in the Linux Kernel found. Fail if no bound addresses can be used for a given scope. A type confusion can happen in inet_diag_msg_sctpasoc_fill() in net/sctp/diag.c, which uses a type confused pointer to return information to userspace when issuing a list_entry() on asoc->base.bind_addr.address_list.next when the list is empty.
References: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=458e279f861d3f61796894cd158b780765a1569f https://www.openwall.com/lists/oss-security/2023/01/23/1(CVE-2023-1074)
A flaw was found in the Linux kernel. A use-after-free may be triggered in asus_kbd_backlight_set when plugging/disconnecting in a malicious USB device, which advertises itself as an Asus device. Similarly to the previous known CVE-2023-25012, but in asus devices, the work_struct may be scheduled by the LED controller while the device is disconnecting, triggering a use-after-free on the struct asus_kbd_leds *led structure. A malicious USB device may exploit the issue to cause memory corruption with controlled data.
Reference: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4ab3a086d10eeec1424f2e8a968827a6336203df(CVE-2023-1079)
A flaw found in the Linux Kernel. The missing check causes a type confusion when issuing a list_entry() on an empty report_list. The problem is caused by the assumption that the device must have valid report_list. While this will be true for all normal HID devices, a suitably malicious device can violate the assumption.
References: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b12fece4c64857e5fab4290bf01b2e0317a88456 https://www.openwall.com/lists/oss-security/2023/01/17/3(CVE-2023-1073)
Kernel: denial of service in tipc_conn_close(CVE-2023-1382)
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"kernel-headers-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-source-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"python3-perf-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-debugsource-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"python3-perf-debuginfo-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"perf-debuginfo-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-devel-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-debuginfo-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"bpftool-debuginfo-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-tools-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-tools-debuginfo-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"perf-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"bpftool-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm",
"kernel-tools-devel-5.10.0-136.24.0.100.oe2203sp1.aarch64.rpm"
],
"src": [
"kernel-5.10.0-136.24.0.100.oe2203sp1.src.rpm"
],
"x86_64": [
"kernel-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-debuginfo-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"python3-perf-debuginfo-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"perf-debuginfo-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-devel-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"bpftool-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-tools-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"perf-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-tools-devel-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"bpftool-debuginfo-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-tools-debuginfo-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"python3-perf-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-headers-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-source-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm",
"kernel-debugsource-5.10.0-136.24.0.100.oe2203sp1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP1",
"name": "kernel",
"purl": "pkg:rpm/openEuler/kernel\u0026distro=openEuler-22.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.10.0-136.24.0.100.oe2203sp1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\r\n\r\nA flaw in the Linux Kernel found. Fail if no bound addresses can be used for a given scope. A type confusion can happen in inet_diag_msg_sctpasoc_fill() in net/sctp/diag.c, which uses a type confused pointer to return information to userspace when issuing a list_entry() on asoc-\u0026gt;base.bind_addr.address_list.next when the list is empty.\r\n\r\nReferences:\nhttps://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=458e279f861d3f61796894cd158b780765a1569f\nhttps://www.openwall.com/lists/oss-security/2023/01/23/1(CVE-2023-1074)\r\n\r\nA flaw was found in the Linux kernel. A use-after-free may be triggered in asus_kbd_backlight_set when plugging/disconnecting in a malicious USB device, which advertises itself as an Asus device.\nSimilarly to the previous known CVE-2023-25012, but in asus devices, the work_struct may be scheduled by the LED controller while the device is disconnecting, triggering a use-after-free on the struct asus_kbd_leds *led structure. A malicious USB device may exploit the issue to cause memory corruption with controlled data.\r\n\r\nReference:\nhttps://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4ab3a086d10eeec1424f2e8a968827a6336203df(CVE-2023-1079)\r\n\r\nA flaw found in the Linux Kernel. The missing check causes a type confusion when issuing a list_entry()\non an empty report_list. The problem is caused by the assumption that the device must have valid report_list. While this will be true for all normal HID devices, a suitably malicious device can violate the assumption.\r\n\r\nReferences:\nhttps://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b12fece4c64857e5fab4290bf01b2e0317a88456\nhttps://www.openwall.com/lists/oss-security/2023/01/17/3(CVE-2023-1073)\r\n\r\n\nKernel: denial of service in tipc_conn_close(CVE-2023-1382)",
"id": "OESA-2023-1180",
"modified": "2026-08-06T11:05:39Z",
"published": "2023-03-24T11:05:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2023-1180"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1074"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1079"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1073"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1382"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "kernel security update",
"upstream": [
"CVE-2023-1074",
"CVE-2023-1079",
"CVE-2023-1073",
"CVE-2023-1382"
]
}
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.