What is CVE-2023-52518?

CVE-2023-52518 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 5.16 onward and patched in 6.1.57, 6.5.7 and 6.6. CVE-2023-52518 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2023-52518?

CVE-2023-52518 has a CVSS score of 5.5 out of 10, rated Medium severity. The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.

Is there a patch available for CVE-2023-52518?

Yes, CVE-2023-52518 has been patched. Fixed versions include 6.1.57, 6.5.7 and 6.6. If you are running Linux kernel 5.16 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-52518 actively exploited?

CVE-2023-52518 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

CVE-2023-52518

Medium

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_codec: Fix leaking content of local_codecs The following memory leak can be observed when the controller supports codecs which are stored in local_codecs list but the elements are never freed: unreferenced object 0xffff88800221d840 (size 32): comm "kworker/u3:0", pid 36, jiffies 4294898739 (age 127.060s) hex dump (first 32 bytes): f8 d3 02 03 80 88 ff ff 80 d8 21 02 80 88 ff ff ..........!..... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffffb324f557>] __kmalloc+0x47/0x120 [<ffffffffb39ef37d>] hci_codec_list_add.isra.0+0x2d/0x160 [<ffffffffb39ef643>] hci_read_codec_capabilities+0x183/0x270 [<ffffffffb39ef9ab>] hci_read_supported_codecs+0x1bb/0x2d0 [<ffffffffb39f162e>] hci_read_local_codecs_sync+0x3e/0x60 [<ffffffffb39ff1b3>] hci_dev_open_sync+0x943/0x11e0 [<ffffffffb396d55d>] hci_power_on+0x10d/0x3f0 [<ffffffffb30c99b4>] process_one_work+0x404/0x800 [<ffffffffb30ca134>] worker_thread+0x374/0x670 [<ffffffffb30d9108>] kthread+0x188/0x1c0 [<ffffffffb304db6b>] ret_from_fork+0x2b/0x50 [<ffffffffb300206a>] ret_from_fork_asm+0x1a/0x30

Package Linux Kernel

Published 2024-03-02

Last modified 2025-03-19

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

5.5

out of 10

Medium

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

High

Vector string

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Weakness type

CWE-770

CVE-2023-52518 is classified as CWE-770

See CWE-770 on MITRE CWE for full details on this weakness type.

Affected versions

Linux kernel versions 5.16 and later are affected. Fixed in 6.1.57, 6.5.7, 6.6 and their respective stable series.

Affected from

≥ 5.16

Fixed in

✓ 6.1.57 6.1.x ✓ 6.5.7 6.5.x ✓ 6.6

References

3 total

Kernel Git
https://git.kernel.org/stable/c/626535077ba9dc110787540d1fe24881094c15a1

Patch
Kernel Git
https://git.kernel.org/stable/c/b938790e70540bf4f2e653dcd74b232494d06c8f

Patch
Kernel Git
https://git.kernel.org/stable/c/eea5a8f0c3b7c884d2351e75fbdd0a3d7def5ae1

Patch

Details

CVE ID CVE-2023-52518

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-03-02

Modified 2025-03-19

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-52518?

CVE-2023-52518 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 5.16 onward and has been patched in 6.1.57, 6.5.7 and 6.6. CVE-2023-52518 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-52518?

CVE-2023-52518 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
Is there a patch available for CVE-2023-52518?

Yes. CVE-2023-52518 has been patched. Fixed versions include 6.1.57, 6.5.7 and 6.6. If you are running Linux kernel 5.16 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-52518 actively exploited?

No. CVE-2023-52518 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.