What is CVE-2024-38592?

CVE-2024-38592 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 6.7 onward and patched in 6.8.12, 6.9.3 and 6.10. CVE-2024-38592 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2024-38592?

CVE-2024-38592 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-2024-38592?

Yes, CVE-2024-38592 has been patched. Fixed versions include 6.8.12, 6.9.3 and 6.10. If you are running Linux kernel 6.7 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2024-38592 actively exploited?

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

CVE-2024-38592

Medium

In the Linux kernel, the following vulnerability has been resolved: drm/mediatek: Init `ddp_comp` with devm_kcalloc() In the case where `conn_routes` is true we allocate an extra slot in the `ddp_comp` array but mtk_drm_crtc_create() never seemed to initialize it in the test case I ran. For me, this caused a later crash when we looped through the array in mtk_drm_crtc_mode_valid(). This showed up for me when I booted with `slub_debug=FZPUA` which poisons the memory initially. Without `slub_debug` I couldn't reproduce, presumably because the later code handles the value being NULL and in most cases (not guaranteed in all cases) the memory the allocator returned started out as 0. It really doesn't hurt to initialize the array with devm_kcalloc() since the array is small and the overhead of initting a handful of elements to 0 is small. In general initting memory to zero is a safer practice and usually it's suggested to only use the non-initting alloc functions if you really need to. Let's switch the function to use an allocation function that zeros the memory. For me, this avoids the crash.

Package Linux Kernel

Published 2024-06-19

Last modified 2025-09-17

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-908

CVE-2024-38592 is classified as CWE-908

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

Affected versions

Linux kernel versions 6.7 and later are affected. Fixed in 6.8.12, 6.9.3, 6.10 and their respective stable series.

Affected from

≥ 6.7

Fixed in

✓ 6.8.12 6.8.x ✓ 6.9.3 6.9.x ✓ 6.10

References

3 total

Kernel Git
https://git.kernel.org/stable/c/01a2c5123e27b3c4685bf2fc4c2e879f6e0c7b33

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

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

Patch

Details

CVE ID CVE-2024-38592

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2024-06-19

Modified 2025-09-17

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2024-38592?

CVE-2024-38592 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.7 onward and has been patched in 6.8.12, 6.9.3 and 6.10. CVE-2024-38592 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2024-38592?

CVE-2024-38592 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-2024-38592?

Yes. CVE-2024-38592 has been patched. Fixed versions include 6.8.12, 6.9.3 and 6.10. If you are running Linux kernel 6.7 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2024-38592 actively exploited?

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