OESA-2024-1297 (CVE-2023-52445)
Vulnerability from osv_openeuler – Published: 2024-03-22 11:06 – Updated: 2026-08-06 11:06 – Source websiteThe Linux Kernel, the operating system core itself.
Security Fix(es):
In the Linux kernel, the following vulnerability has been resolved:
media: pvrusb2: fix use after free on context disconnection
Upon module load, a kthread is created targeting the pvr2_context_thread_func function, which may call pvr2_context_destroy and thus call kfree() on the context object. However, that might happen before the usb hub_event handler is able to notify the driver. This patch adds a sanity check before the invalid read reported by syzbot, within the context disconnection call stack.(CVE-2023-52445)
In the Linux kernel, the following vulnerability has been resolved:
mtd: Fix gluebi NULL pointer dereference caused by ftl notifier
If both ftl.ko and gluebi.ko are loaded, the notifier of ftl triggers NULL pointer dereference when trying to access ‘gluebi->desc’ in gluebi_read().
ubi_gluebi_init ubi_register_volume_notifier ubi_enumerate_volumes ubi_notify_all gluebi_notify nb->notifier_call() gluebi_create mtd_device_register mtd_device_parse_register add_mtd_device blktrans_notify_add not->add() ftl_add_mtd tr->add_mtd() scan_header mtd_read mtd_read_oob mtd_read_oob_std gluebi_read mtd->read() gluebi->desc - NULL
Detailed reproduction information available at the Link [1],
In the normal case, obtain gluebi->desc in the gluebi_get_device(), and access gluebi->desc in the gluebi_read(). However, gluebi_get_device() is not executed in advance in the ftl_add_mtd() process, which leads to NULL pointer dereference.
The solution for the gluebi module is to run jffs2 on the UBI volume without considering working with ftl or mtdblock [2]. Therefore, this problem can be avoided by preventing gluebi from creating the mtdblock device after creating mtd partition of the type MTD_UBIVOLUME.(CVE-2023-52449)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"bpftool-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-debugsource-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-source-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-tools-devel-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"perf-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"python2-perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"python3-perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-tools-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"python2-perf-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"python3-perf-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-devel-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"kernel-tools-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm",
"bpftool-4.19.90-2403.3.0.0270.oe2003sp4.aarch64.rpm"
],
"src": [
"kernel-4.19.90-2403.3.0.0270.oe2003sp4.src.rpm"
],
"x86_64": [
"python2-perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-tools-devel-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"bpftool-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-tools-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-devel-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"perf-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-debugsource-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"python2-perf-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-tools-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"kernel-source-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"python3-perf-debuginfo-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"python3-perf-4.19.90-2403.3.0.0270.oe2003sp4.x86_64.rpm",
"bpftool-4.19.90-2403.3.0.0270.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-2403.3.0.0270.oe2003sp4"
}
],
"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 the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmedia: pvrusb2: fix use after free on context disconnection\r\n\r\nUpon module load, a kthread is created targeting the\npvr2_context_thread_func function, which may call pvr2_context_destroy\nand thus call kfree() on the context object. However, that might happen\nbefore the usb hub_event handler is able to notify the driver. This\npatch adds a sanity check before the invalid read reported by syzbot,\nwithin the context disconnection call stack.(CVE-2023-52445)\r\n\r\nIn the Linux kernel, the following vulnerability has been resolved:\r\n\r\nmtd: Fix gluebi NULL pointer dereference caused by ftl notifier\r\n\r\nIf both ftl.ko and gluebi.ko are loaded, the notifier of ftl\ntriggers NULL pointer dereference when trying to access\n\u2018gluebi-\u0026gt;desc\u2019 in gluebi_read().\r\n\r\nubi_gluebi_init\n ubi_register_volume_notifier\n ubi_enumerate_volumes\n ubi_notify_all\n gluebi_notify nb-\u0026gt;notifier_call()\n gluebi_create\n mtd_device_register\n mtd_device_parse_register\n add_mtd_device\n blktrans_notify_add not-\u0026gt;add()\n ftl_add_mtd tr-\u0026gt;add_mtd()\n scan_header\n mtd_read\n mtd_read_oob\n mtd_read_oob_std\n gluebi_read mtd-\u0026gt;read()\n gluebi-\u0026gt;desc - NULL\r\n\r\nDetailed reproduction information available at the Link [1],\r\n\r\nIn the normal case, obtain gluebi-\u0026gt;desc in the gluebi_get_device(),\nand access gluebi-\u0026gt;desc in the gluebi_read(). However,\ngluebi_get_device() is not executed in advance in the\nftl_add_mtd() process, which leads to NULL pointer dereference.\r\n\r\nThe solution for the gluebi module is to run jffs2 on the UBI\nvolume without considering working with ftl or mtdblock [2].\nTherefore, this problem can be avoided by preventing gluebi from\ncreating the mtdblock device after creating mtd partition of the\ntype MTD_UBIVOLUME.(CVE-2023-52449)",
"id": "OESA-2024-1297",
"modified": "2026-08-06T11:06:44Z",
"published": "2024-03-22T11:06:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2024-1297"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52445"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52449"
}
],
"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-52445",
"CVE-2023-52449"
]
}
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.