CVSS 3.1
5.5 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HMedium (5.5) in linux linux kernel. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExplain CVE-2023-53627 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-53627?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-53627?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-53627 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 4.5 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.189 |
| Linux | 6.3 | 6.3.4 |
| Linux | later releases | 6.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.190-1 | DEBIAN-CVE-2023-53627 |
| Debian | 13, 14 | linux | 6.3.7-1 | DEBIAN-CVE-2023-53627 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 47 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | 24.04:LTS | linux-intel, linux-riscv, linux-oem-6.8 and 7 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Nvidia-BlueField:22.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:14.04:LTS | linux-azure | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:16.04:LTS | linux-gcp, linux-hwe, linux-azure and 2 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:18.04:LTS | linux, linux-aws, linux-kvm and 10 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:20.04:LTS | linux, linux-aws, linux-gcp and 19 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:18.04:LTS, Pro:FIPS-updates:20.04:LTS and 3 more | linux-fips, linux-aws-fips, linux-gcp-fips and 1 more | no fix listed | UBUNTU-CVE-2023-53627 |
| Ubuntu | Pro:Realtime:22.04:LTS | linux-realtime, linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2023-53627 |
| Azure Linux | 2 | kernel | no fix listed | AZL-76404 |
| Alpaquita | 23 | linux-lts | 6.1.189-r0 | BELL-CVE-2023-53627 |
| Alpaquita | stream | linux-lts | 6.6.58-r0 | BELL-CVE-2023-53627 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat rates this Moderate.
The issue arises because of missing locking when accessing the shared sas_dev.list structure. Two code paths can execute concurrently: the completion queue thread (cq thread) calls slot_complete_v3_hw() → hisi_sas_slot_task_free() → list_del_init() to remove completed task slots, while the SCSI error handler thread calls sas_scsi_find_task() → hisi_sas_abort_task() → dereg_device_v3_hw() → list_for_each_entry_safe() to traverse the same list when aborting tasks. Without synchronization, the deletion can invalidate list pointers while traversal is in progress. When the error handler attempts to follow the next pointer in the list after a concurrent deletion, it dereferences a NULL or freed pointer (register x1 = 0x0000000000000000 in the crash dump), causing a kernel panic. The race window is narrow and requires precise timing between I/O completion and error handling paths, which can be triggered under heavy I/O workload with concurrent errors. While this reliably causes availability impact through kernel panics, the underlying list corruption represents a memory safety violation. With sufficient control over timing and heap layout, race conditions on linked list structures can potentially be leveraged for more sophisticated attacks beyond denial of service, though such exploitation would be complex.
To mitigate this issue, prevent the hisi_sas_v3_hw module from loading. See https://access.redhat.com/solutions/41278 for instructions on blacklisting kernel modules.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Not affected | |
| Red Hat Enterprise Linux 6 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Will not fix | |
| Red Hat Enterprise Linux 8 | kernel-rt | Affected | |
| Red Hat Enterprise Linux 9 | kernel | Will not fix | |
| Red Hat Enterprise Linux 9 | kernel-rt | Affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-53627.