What is CVE-2026-53124?

CVE-2026-53124 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10, affecting Linux kernel versions from 6.14.6 onward and patched in 7.0.10 and 7.1. CVE-2026-53124 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

Yes, CVE-2026-53124 has been patched. Fixed versions include 7.0.10 and 7.1. If you are running Linux kernel 6.14.6 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2026-53124 actively exploited?

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

CVE-2026-53124

Medium

In the Linux kernel, the following vulnerability has been resolved: ublk: reset per-IO canceled flag on each fetch If a ublk server starts recovering devices but dies before issuing fetch commands for all IOs, cancellation of the fetch commands that were successfully issued may never complete. This is because the per-IO canceled flag can remain set even after the fetch for that IO has been submitted - the per-IO canceled flags for all IOs in a queue are reset together only once all IOs for that queue have been fetched. So if a nonempty proper subset of the IOs for a queue are fetched when the ublk server dies, the IOs in that subset will never successfully be canceled, as their canceled flags remain set, and this prevents ublk_cancel_cmd from actually calling io_uring_cmd_done on the commands, despite the fact that they are outstanding. Fix this by resetting the per-IO cancel flags immediately when each IO is fetched instead of waiting for all IOs for the queue (which may never happen).

Package Linux Kernel

Published 2026-06-24

Last modified 2026-07-23

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

Affected versions

Linux kernel versions 6.14.6, 6.15 and later are affected. Fixed in 7.0.10, 7.1 and their respective stable series.

Affected from

≥ 6.14.6 ≥ 6.15

Fixed in

✓ 7.0.10 7.0.x ✓ 7.1

References

2 total

Kernel Git
https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b

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

Patch

Details

CVE ID CVE-2026-53124

Severity Medium

CVSS score 5.5 / 10

CVSS version 3.1

Published 2026-06-24

Modified 2026-07-23

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2026-53124?

CVE-2026-53124 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.14.6 onward and has been patched in 7.0.10 and 7.1. CVE-2026-53124 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2026-53124?

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

Yes. CVE-2026-53124 has been patched. Fixed versions include 7.0.10 and 7.1. If you are running Linux kernel 6.14.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2026-53124 actively exploited?

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