What is CVE-2026-93039?

CVE-2026-93039 is a High severity Linux kernel vulnerability with a CVSS score of 7.4 out of 10, affecting Linux kernel versions from 4.19 onward and patched in 5.10.270, 5.15.221, 6.1.188 and others. CVE-2026-93039 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

What is the CVSS score for CVE-2026-93039?

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

Is there a patch available for CVE-2026-93039?

Yes, CVE-2026-93039 has been patched. Fixed versions include 5.10.270, 5.15.221, 6.1.188 and others. If you are running Linux kernel 4.19 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-93039 actively exploited?

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

CVE-2026-93039

High

In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: Keep link pointers valid on realloc failure meson_card_reallocate_links() grows the DAI link and private data arrays with two consecutive krealloc() calls and updates the owner pointers only after both calls have succeeded. A successful krealloc() may move the data: it frees the old block and returns a new one. When that happens for the link array and the second krealloc() then fails, card->dai_link still points to the block that krealloc() already freed, and the error path frees the new block too. The probe error path then calls meson_card_clean_references(), which dereferences card->dai_link and kfree()s it again, resulting in a use-after-free and a double free. Commit card->dai_link and card->num_links right after the first krealloc() succeeds, so the pointer always refers to a valid allocation that meson_card_clean_references() can walk and free. krealloc() with __GFP_ZERO zero-initializes the added entries, so walking them on the error path is safe. With both failure paths reduced to a plain return, drop the goto labels and the error message.

Package Linux Kernel

Published 2026-09-17

Last modified 2026-09-18

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.4

out of 10

High

Attack Vector

Local

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

Linux kernel versions 4.19 and later are affected. Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6, 7.3-rc1 and their respective stable series.

Affected from

≥ 4.19

Fixed in

✓ 5.10.270 5.10.x ✓ 5.15.221 5.15.x ✓ 6.1.188 6.1.x ✓ 6.6.157 6.6.x ✓ 6.12.110 6.12.x ✓ 6.18.52 6.18.x ✓ 7.2.6 7.2.x ✓ 7.3-rc1

References

8 total

Showing 5 of 8 references View all on NVD

Details

CVE ID CVE-2026-93039

Severity High

CVSS score 7.4 / 10

CVSS version 3.1

Published 2026-09-17

Modified 2026-09-18

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-93039?

CVE-2026-93039 is a High severity Linux kernel vulnerability with a CVSS score of 7.4 out of 10 . It affects Linux kernel versions from 4.19 onward and has been patched in 5.10.270, 5.15.221, 6.1.188 and others. CVE-2026-93039 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-93039?

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

Yes. CVE-2026-93039 has been patched. Fixed versions include 5.10.270, 5.15.221, 6.1.188 and others. If you are running Linux kernel 4.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-93039 actively exploited?

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