Menu

Star on GitHub · 3.2k

CVE-2023-53231

5.5 · MEDIUM

In the Linux kernel, the following vulnerability has been resolved: erofs: Fix detection of atomic context Current check for atomic context is not sufficient as z_erofs_decompressqueue_endio can…

Published Sep 15, 2025EPSS 0.16%

Overview

CVE-2023-53231 is a medium-severity vulnerability. It was published on September 15, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

erofs: Fix detection of atomic context

Current check for atomic context is not sufficient as

z_erofs_decompressqueue_endio can be called under rcu lock

from blk_mq_flush_plug_list(). See the stacktrace [1]

In such case we should hand off the decompression work for async

processing rather than trying to do sync decompression in current

context. Patch fixes the detection by checking for

rcu_read_lock_any_held() and while at it use more appropriate

!in_task() check than in_atomic().

Background: Historically erofs would always schedule a kworker for

decompression which would incur the scheduling cost regardless of

the context. But z_erofs_decompressqueue_endio() may not always

be in atomic context and we could actually benefit from doing the

decompression in z_erofs_decompressqueue_endio() if we are in

thread context, for example when running with dm-verity.

This optimization was later added in patch [2] which has show

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2023-53231?

CVE-2023-53231 is a medium-severity vulnerability. It was published on September 15, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2023-53231?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2023-53231?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2023-53231?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2023-53231 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2023

View all