What is CVE-2026-43224?

CVE-2026-43224 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, classified as a Memory Leak flaw (CWE-401), affecting Linux kernel versions from 6.18 onward and patched in 6.18.16, 6.19.6 and 7.0. CVE-2026-43224 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

CVE-2026-43224 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-2026-43224?

Yes, CVE-2026-43224 has been patched. Fixed versions include 6.18.16, 6.19.6 and 7.0. If you are running Linux kernel 6.18 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-43224 actively exploited?

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

What is Memory Leak (CWE-401)?

The product does not release memory after use, causing gradual resource exhaustion. See MITRE CWE for full details: https://cwe.mitre.org/data/definitions/401.html

CVE-2026-43224

Medium

In the Linux kernel, the following vulnerability has been resolved: io_uring/zcrx: fix sgtable leak on mapping failures In an unlikely case when io_populate_area_dma() fails, which could only happen on a PAGE_POOL_32BIT_ARCH_WITH_64BIT_DMA machine, io_zcrx_map_area() will have an initialised and not freed table. It was supposed to be cleaned up in the error path, but !is_mapped prevents that.

Package Linux Kernel

Published 2026-05-06

Last modified 2026-05-08

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

CVE-2026-43224 is a Memory Leak vulnerability

What is Memory Leak?

The product does not release memory after use, causing gradual resource exhaustion. Learn more on MITRE CWE

Affected versions

Linux kernel versions 6.18 and later are affected. Fixed in 6.18.16, 6.19.6, 7.0 and their respective stable series.

Affected from

≥ 6.18

Fixed in

✓ 6.18.16 6.18.x ✓ 6.19.6 6.19.x ✓ 7.0

References

The following references provide additional information about CVE-2026-43224 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Kernel patch commit
https://git.kernel.org/stable/c/a983aae397767e9da931128ff2b5bf9066513ce3
Patch
Kernel patch commit
https://git.kernel.org/stable/c/ef075c1464ac9047e2cf7d23cb020bfd0b8e4b60
Patch
Kernel patch commit
https://git.kernel.org/stable/c/f1ae403324311e143ef20e53cf9a5f01e312f7c9
Patch

Details

CVE ID CVE-2026-43224

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-05-06

Modified 2026-05-08

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-43224?

CVE-2026-43224 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 , classified as a Memory Leak flaw (CWE-401) . It affects Linux kernel versions from 6.18 onward and has been patched in 6.18.16, 6.19.6 and 7.0. CVE-2026-43224 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-43224?

CVE-2026-43224 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-2026-43224?

Yes — CVE-2026-43224 has been patched. Fixed versions include 6.18.16, 6.19.6 and 7.0. If you are running Linux kernel 6.18 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-43224 actively exploited?

No — CVE-2026-43224 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
What is Memory Leak (CWE-401)?

The product does not release memory after use, causing gradual resource exhaustion. View CWE-401 on MITRE CWE →