CVE-2023-53530

Kernel BUG diagnostic via preemptible CPU access

Published Oct 1, 2025 · Updated May 11, 2026

Improper CPU-context access in Linux 6.3 through 6.5.4 allows local users to trigger a kernel BUG diagnostic during qla2xxx NVMe-FC work. qla_nvme_post_cmd and related work-queue paths call smp_processor_id() from preemptible code and use queue_work_on() to bind work to the selected CPU. The reported configuration uses qla2xxx with NVMe over Fibre Channel and CONFIG_DEBUG_PREEMPT; the published trace shows a diagnostic failure, with no reported data access or modification.

CVSS severity5.5
Medium
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper CPU-context access in Linux 6.3 through 6.5.4 allows local users to trigger a kernel BUG diagnostic during qla2xxx NVMe-FC work. qla_nvme_post_cmd and related work-queue paths call smp_processor_id() from preemptible code and use queue_work_on() to bind work to the selected CPU. The reported configuration uses qla2xxx with NVMe over Fibre Channel and CONFIG_DEBUG_PREEMPT; the published trace shows a diagnostic failure, with no reported data access or modification.

The record

CVE
CVE-2023-53530
Published
Oct 1, 2025
Updated
May 11, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Oct 1, 2025CVE publishedPublication date reported by the CVE source.
  2. May 11, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=1d201c81d4cc6840735bbcc99e6031503e5cf3b8 <25bd0c7def04a272f8e89b36971712fe29c6e438
  2. Affected versionversion=1d201c81d4cc6840735bbcc99e6031503e5cf3b8 <59f10a05b5c7b675256a66e3161741239889ff80
  3. Affected versionversion=35c02a333d523d9da0b482b0d751cdeb95c068ae <52c7b41ad6ee53222f4ee2f0c099a6ed8291a168
  4. Affected versionversion=532a239605667320f4fd7473e416b718d0a2fbbb <1a541999f31fcb10ea50eba2a563e6c451fd5c7d
  5. Affected versionversion=6.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=1d201c81d4cc6840735bbcc99e6031503e5cf3b8 <25bd0c7def04a272f8e89b36971712fe29c6e438; version=1d201c81d4cc6840735bbcc99e6031503e5cf3b8 <59f10a05b5c7b675256a66e3161741239889ff80; version=35c02a333d523d9da0b482b0d751cdeb95c068ae <52c7b41ad6ee53222f4ee2f0c099a6ed8291a168; version=532a239605667320f4fd7473e416b718d0a2fbbb <1a541999f31fcb10ea50eba2a563e6c451fd5c7d; version=6.3

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo