BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-53231High confidence

erofs: Fix detection of atomic context

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 3 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.16% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

13 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 10 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.4.11-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcp-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-intelAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatency-hwe-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-53231 · CSAF 2.0 · revision 45 · interimSUSE Product Security TeamCVE-2023-53231
145 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-source as component of SLES-LTSS-TERADATA 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
Summary
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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-59853

No EUVD known-exploited evidence

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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
5.5 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 10 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/

What

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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration.
CWE not yet assigned
CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2023-59853Official EUVD mapping

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 shown improvement in performance benchmarks. ============================================== [1] Problem stacktrace [name:core&]BUG: sleeping function called from invalid context at kernel/locking/mutex.c:291 [name:core&]in_atomic(): 0, irqs_disabled(): 0, non_block: 0, pid: 1615, name: CpuMonitorServi [name:core&]preempt_count: 0, expected: 0 [name:core&]RCU nest depth: 1, expected: 0 CPU: 7 PID: 1615 Comm: CpuMonitorServi Tainted: G S W OE 6.1.25-android14-5-maybe-dirty-mainline #1 Hardware name: MT6897 (DT) Call trace: dump_backtrace+0x108/0x15c show_stack+0x20/0x30 dump_stack_lvl+0x6c/0x8c dump_stack+0x20/0x48 __might_resched+0x1fc/0x308 __might_sleep+0x50/0x88 mutex_lock+0x2c/0x110 z_erofs_decompress_queue+0x11c/0xc10 z_erofs_decompress_kickoff+0x110/0x1a4 z_erofs_decompressqueue_endio+0x154/0x180 bio_endio+0x1b0/0x1d8 __dm_io_complete+0x22c/0x280 clone_endio+0xe4/0x280 bio_endio+0x1b0/0x1d8 blk_update_request+0x138/0x3a4 blk_mq_plug_issue_direct+0xd4/0x19c blk_mq_flush_plug_list+0x2b0/0x354 __blk_flush_plug+0x110/0x160 blk_finish_plug+0x30/0x4c read_pages+0x2fc/0x370 page_cache_ra_unbounded+0xa4/0x23c page_cache_ra_order+0x290/0x320 do_sync_mmap_readahead+0x108/0x2c0 filemap_fault+0x19c/0x52c __do_fault+0xc4/0x114 handle_mm_fault+0x5b4/0x1168 do_page_fault+0x338/0x4b4 do_translation_fault+0x40/0x60 do_mem_abort+0x60/0xc8 el0_da+0x4c/0xe0 el0t_64_sync_handler+0xd4/0xfc el0t_64_sync+0x1a0/0x1a4 [2] Link: https://lore.kernel.org/all/20210317035448.13921-1-huangjianan@oppo.com/

Official EUVD record ↗
BSI · German · WID-SEC-2025-2053Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht näher beschriebene Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20250917SECURITY BULLETIN 17 SEPT 2025

The Cyber Security Agency of Singapore included this CVE in its official SECURITY BULLETIN 17 SEPT 2025, published on 17 September 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-53152 Référence CVE CVE-2023-53168 https://www.cve.org/CVERecord?id=CVE-2023-53168 Référence CVE CVE-2023-53178 https://www.cve.org/CVERecord?id=CVE-2023-53178 Référence CVE CVE-2023-53180 https://www.cve.org/CVERecord?id=CVE-2023-53180 Référence CVE CVE-2023-53187 https://www.cve.org/CVERecord?id=CVE-2023-53187 Référence CVE CVE-2023-53198 https://www.cve.org/CVERecord?id=CVE-2023-53198 Référence CVE CVE-2023-53209 https://www.cve.org/CVERecord?id=CVE-2023-53209 Référence CVE CVE-2023-53218 https://www.cve.org/CVERecord?id=CVE-2023-53218 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53240 https://www.cve.org/CVERecord?id=CVE-2023-53240 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=CVE-2023-53247 Référence CVE CVE-2023-53248 https://www.cve.org/CVERecord?id=CVE-2023-53248 Référence CVE CVE-2023-53254 https://www.cve.org/CVERecord?id=CVE-2023-53254 Référence CVE CVE-2023-53258 https://www.cve.org/CVERecord?id=CVE-2023-53258 Référence CVE CVE-2023-53261 https://www.cve.org/CVERecord?id=CVE-2023-53261 Référence CVE CVE-2023-53292 https://www.cve.org/CVERecord?id=CVE-2023-53292 Référence CVE CVE-2023-53320 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2023-53152 Référence CVE CVE-2023-53168 https://www.cve.org/CVERecord?id=CVE-2023-53168 Référence CVE CVE-2023-53178 https://www.cve.org/CVERecord?id=CVE-2023-53178 Référence CVE CVE-2023-53180 https://www.cve.org/CVERecord?id=CVE-2023-53180 Référence CVE CVE-2023-53187 https://www.cve.org/CVERecord?id=CVE-2023-53187 Référence CVE CVE-2023-53198 https://www.cve.org/CVERecord?id=CVE-2023-53198 Référence CVE CVE-2023-53209 https://www.cve.org/CVERecord?id=CVE-2023-53209 Référence CVE CVE-2023-53218 https://www.cve.org/CVERecord?id=CVE-2023-53218 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53240 https://www.cve.org/CVERecord?id=CVE-2023-53240 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=CVE-2023-53247 Référence CVE CVE-2023-53248 https://www.cve.org/CVERecord?id=CVE-2023-53248 Référence CVE CVE-2023-53254 https://www.cve.org/CVERecord?id=CVE-2023-53254 Référence CVE CVE-2023-53258 https://www.cve.org/CVERecord?id=CVE-2023-53258 Référence CVE CVE-2023-53261 https://www.cve.org/CVERecord?id=CVE-2023-53261 Référence CVE CVE-2023-53292 https://www.cve.org/CVERecord?id=CVE-2023-53292 Référence CVE CVE-2023-53320 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1078Multiples vulnérabilités dans les produits Microsoft

0217 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40218 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40219 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40220 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-61729 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-66293 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-66476 du 05 décembre 2025 Bulletin de sécurité Microsoft CVE-2022-50303 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2022-50304 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2023-53209 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2023-53231 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-12084 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-12385 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40223 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40233 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40240 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40242 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40243 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40244 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-2025-40245 du 06 décembre 2025 Bulletin de sécurité Microsoft CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1032Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53243 https://www.cve.org/CVERecord?id=CVE-2023-53243 Référence CVE CVE-2023-53245 https://www.cve.org/CVERecord?id=CVE-2023-53245 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=CVE-2023-53247 Référence CVE CVE-2023-53248 https://www.cve.org/CVERecord?id=CVE-2023-53248 Référence CVE CVE-2023-53249 https://www.cve.org/CVERecord?id=CVE-2023-53249 Référence CVE CVE-2023-53251 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1009Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53209 Référence CVE CVE-2023-53210 https://www.cve.org/CVERecord?id=CVE-2023-53210 Référence CVE CVE-2023-53215 https://www.cve.org/CVERecord?id=CVE-2023-53215 Référence CVE CVE-2023-53217 https://www.cve.org/CVERecord?id=CVE-2023-53217 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53243 https://www.cve.org/CVERecord?id=CVE-2023-53243 Référence CVE CVE-2023-53245 https://www.cve.org/CVERecord?id=CVE-2023-53245 Référence CVE CVE-2023-53247 https://www.cve.org/CVERecord?id=CVE-2023-53247 Référence CVE CVE-2023-53248 https://www.cve.org/CVERecord?id=CVE-2023-53248 Référence CVE CVE-2023-53249 https://www.cve.org/CVERecord?id=CVE-2023-53249 Référence CVE CVE-2023-53251 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0921Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53217 Référence CVE CVE-2023-53219 https://www.cve.org/CVERecord?id=CVE-2023-53219 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53223 https://www.cve.org/CVERecord?id=CVE-2023-53223 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53229 https://www.cve.org/CVERecord?id=CVE-2023-53229 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53234 https://www.cve.org/CVERecord?id=CVE-2023-53234 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53239 https://www.cve.org/CVERecord?id=CVE-2023-53239 Référence CVE CVE-2023-53241 https://www.cve.org/CVERecord?id=CVE-2023-53241 Référence CVE CVE-2023-53242 https://www.cve.org/CVERecord?id=CVE-2023-53242 Référence CVE CVE-2023-53243 https://www.cve.org/CVERecord?id=CVE-2023-53243 Référence CVE CVE-2023-53244 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0895Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2023-53217 Référence CVE CVE-2023-53219 https://www.cve.org/CVERecord?id=CVE-2023-53219 Référence CVE CVE-2023-53220 https://www.cve.org/CVERecord?id=CVE-2023-53220 Référence CVE CVE-2023-53221 https://www.cve.org/CVERecord?id=CVE-2023-53221 Référence CVE CVE-2023-53222 https://www.cve.org/CVERecord?id=CVE-2023-53222 Référence CVE CVE-2023-53223 https://www.cve.org/CVERecord?id=CVE-2023-53223 Référence CVE CVE-2023-53226 https://www.cve.org/CVERecord?id=CVE-2023-53226 Référence CVE CVE-2023-53229 https://www.cve.org/CVERecord?id=CVE-2023-53229 Référence CVE CVE-2023-53230 https://www.cve.org/CVERecord?id=CVE-2023-53230 Référence CVE CVE-2023-53231 https://www.cve.org/CVERecord?id=CVE-2023-53231 Référence CVE CVE-2023-53232 https://www.cve.org/CVERecord?id=CVE-2023-53232 Référence CVE CVE-2023-53234 https://www.cve.org/CVERecord?id=CVE-2023-53234 Référence CVE CVE-2023-53235 https://www.cve.org/CVERecord?id=CVE-2023-53235 Référence CVE CVE-2023-53237 https://www.cve.org/CVERecord?id=CVE-2023-53237 Référence CVE CVE-2023-53238 https://www.cve.org/CVERecord?id=CVE-2023-53238 Référence CVE CVE-2023-53239 https://www.cve.org/CVERecord?id=CVE-2023-53239 Référence CVE CVE-2023-53241 https://www.cve.org/CVERecord?id=CVE-2023-53241 Référence CVE CVE-2023-53242 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-030166Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 4.19, 5.15.222 ≤ 5.15.*, 6.1.189 ≤ 6.1.*, 6.4.7 ≤ 6.4.*, 6.5 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 15 Sept 2025 · Last source change 3 Oct 2026, 10:54 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-59853
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    aea1286dcbbb87cf33595c2ac8b153c29a4611cb < 597fb60c75132719687e173b75cab8f6eb1ca657; aea1286dcbbb87cf33595c2ac8b153c29a4611cb < 12d0a24afd9ea58e581ea64d64e066f2027b28d9; 4.19 · Fixed: < 4.19; 6.4.7 ≤ 6.4.*; 6.5 ≤ *
    After
    Linux: aea1286dcbbb87cf33595c2ac8b153c29a4611cb < c3446e50fb4dc39e2dfb5951a57bc175d38f68be, aea1286dcbbb87cf33595c2ac8b153c29a4611cb < 96bcd9650e15901201d964eef5f79d18a81daac8, aea1286dcbbb87cf33595c2ac8b153c29a4611cb < 597fb60c75132719687e173b75cab8f6eb1ca657, aea1286dcbbb87cf33595c2ac8b153c29a4611cb < 12d0a24afd9ea58e581ea64d64e066f2027b28d9, 4.19 · Fixed: Linux: < 4.19, 5.15.222 ≤ 5.15.*, 6.1.189 ≤ 6.1.*, 6.4.7 ≤ 6.4.*, 6.5 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-59853↗Vendor CSAF · SUSE Product Security Team↗Patch or update reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-53231 · cve.blacktree.nl