What is CVE-2023-53810?

CVE-2023-53810 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10, affecting Linux kernel versions from 5.8 onward and patched in 5.10.180, 5.15.111, 6.1.28 and others. CVE-2023-53810 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

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

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

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

Yes, CVE-2023-53810 has been patched. Fixed versions include 5.10.180, 5.15.111, 6.1.28 and others. If you are running Linux kernel 5.8 or later up to the fix versions, apply the relevant patch for your kernel branch.

Is CVE-2023-53810 actively exploited?

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

CVE-2023-53810

High

In the Linux kernel, the following vulnerability has been resolved: blk-mq: release crypto keyslot before reporting I/O complete Once all I/O using a blk_crypto_key has completed, filesystems can call blk_crypto_evict_key(). However, the block layer currently doesn't call blk_crypto_put_keyslot() until the request is being freed, which happens after upper layers have been told (via bio_endio()) the I/O has completed. This causes a race condition where blk_crypto_evict_key() can see 'slot_refs != 0' without there being an actual bug. This makes __blk_crypto_evict_key() hit the 'WARN_ON_ONCE(atomic_read(&slot->slot_refs) != 0)' and return without doing anything, eventually causing a use-after-free in blk_crypto_reprogram_all_keys(). (This is a very rare bug and has only been seen when per-file keys are being used with fscrypt.) There are two options to fix this: either release the keyslot before bio_endio() is called on the request's last bio, or make __blk_crypto_evict_key() ignore slot_refs. Let's go with the first solution, since it preserves the ability to report bugs (via WARN_ON_ONCE) where a key is evicted while still in-use.

Package Linux Kernel

Published 2025-12-09

Last modified 2026-08-04

CVSS version 3.1

Patch available

Yes

CVSS 3.1 score

7.8

out of 10

High

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Vector string

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

Affected versions

Linux kernel versions 5.8 and later are affected. Fixed in 5.10.180, 5.15.111, 6.1.28, 6.2.15, 6.3.2, 6.4 and their respective stable series.

Affected from

≥ 5.8

Fixed in

✓ 5.10.180 5.10.x ✓ 5.15.111 5.15.x ✓ 6.1.28 6.1.x ✓ 6.2.15 6.2.x ✓ 6.3.2 6.3.x ✓ 6.4

References

6 total

Showing 5 of 6 references View all on NVD

Details

CVE ID CVE-2023-53810

Severity High

CVSS score 7.8 / 10

CVSS version 3.1

Published 2025-12-09

Modified 2026-08-04

KEV No

Patch

Yes

Package linux

Frequently asked questions

What is CVE-2023-53810?

CVE-2023-53810 is a High severity Linux kernel vulnerability with a CVSS score of 7.8 out of 10 . It affects Linux kernel versions from 5.8 onward and has been patched in 5.10.180, 5.15.111, 6.1.28 and others. CVE-2023-53810 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
What is the CVSS score for CVE-2023-53810?

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

Yes. CVE-2023-53810 has been patched. Fixed versions include 5.10.180, 5.15.111, 6.1.28 and others. If you are running Linux kernel 5.8 or later up to the fix versions, apply the relevant patch for your kernel branch.
Is CVE-2023-53810 actively exploited?

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