CVE-2023-52774
published 2024-05-21CVE-2023-52774: In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the…
PriorityP422medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start() the amount of requests on the device queue are
counted. The access to the device queue is unprotected against
concurrent access. With a lot of parallel I/O, especially with alias
devices enabled, the device queue can change while dasd_profile_start()
is accessing the queue. In the worst case this leads to a kernel panic
due to incorrect pointer accesses.
Fix this by taking the device lock before accessing the queue and
counting the requests. Additionally the check for a valid profile data
pointer can be done earlier to avoid unnecessary locking in a hot path.
Affected
22 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.66-1 (bookworm) | linux 6.1.66-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < ebdc569a07a3e8dbe66b4184922ad6f88ac0b96f | ebdc569a07a3e8dbe66b4184922ad6f88ac0b96f |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < f75617cc8df4155374132f0b500b0b3ebb967458 | f75617cc8df4155374132f0b500b0b3ebb967458 |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < f1ac7789406e2ca9ac51c41ad2daa597f47bdd4d | f1ac7789406e2ca9ac51c41ad2daa597f47bdd4d |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < c841de6247e94e07566d57163d3c0d8b29278f7a | c841de6247e94e07566d57163d3c0d8b29278f7a |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < 6062c527d0403cef27c54b91ac8390c3a497b250 | 6062c527d0403cef27c54b91ac8390c3a497b250 |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < dc96fde8fcb2b896fd6c64802a7f4ece2e69b0be | dc96fde8fcb2b896fd6c64802a7f4ece2e69b0be |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < 9372aab5d0ff621ea203c8c603e7e5f75e888240 | 9372aab5d0ff621ea203c8c603e7e5f75e888240 |
| linux | linux | >= 4fa52aa7a82f9226b3874a69816bda3af821f002 < db46cd1e0426f52999d50fa72cfa97fa39952885 | db46cd1e0426f52999d50fa72cfa97fa39952885 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 5.10.205-1 | 5.10.205-1 |
| linux | linux_kernel | >= 0 < 6.1.66-1 | 6.1.66-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 0 < 6.6.8-1 | 6.6.8-1 |
| linux | linux_kernel | >= 3.1 < 4.14.332 | 4.14.332 |
| linux | linux_kernel | >= 4.15 < 4.19.301 | 4.19.301 |
| linux | linux_kernel | >= 4.20 < 5.4.263 | 5.4.263 |
| linux | linux_kernel | >= 5.11 < 5.15.141 | 5.15.141 |
| linux | linux_kernel | >= 5.16 < 6.1.65 | 6.1.65 |
| linux | linux_kernel | >= 5.5 < 5.10.203 | 5.10.203 |
| linux | linux_kernel | >= 6.2 < 6.6.4 | 6.6.4 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
CISA ICS
Siemens SINEC OS
cisa_ics·2025-08-14
Siemens SINEC OS
ICS Advisory
##
Siemens SINEC OS
Release DateAugust 14, 2025
Alert CodeICSA-25-226-15
Related topics:
Industrial Control System Vulnerabilities, Industrial Control Systems
As of January 10, 2023, CISA will no longer be updating ICS security advisories for Siemens product vulnerabilities beyond the initial advisory. For the most up-to-date information on vulnerabilities in this advisory, please see Siemens' ProductCERT Security Advisories (CERT Services | Services | Siemens Global).
View CSAF
## 1. EXECUTIVE SUMMARY
- CVSS v3.1 9.1
- ATTENTION: Exploitable remotely/low attack complexity
- Vendor: Siemens
- Equipment: RUGGEDCOM, SCALANCE
- Vulnerabilities: NULL Pointer Dereference, Use After Free, Unchecked Input for Loop Condition, Out-of-bounds Write, Ou
Red Hat
kernel: s390/dasd: protect device queue against concurrent access
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52774 [MEDIUM] CWE-667 kernel: s390/dasd: protect device queue against concurrent access
kernel: s390/dasd: protect device queue against concurrent access
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start() the amount of requests on the device queue are
counted. The access to the device queue is unprotected against
concurrent access. With a lot of parallel I/O, especially with alias
devices enabled, the device queue can change while dasd_profile_start()
is accessing the queue. In the worst case this leads to a kernel panic
due to incorrect pointer accesses.
Fix this by taking the device lock before accessing the queue and
counting the requests. Additionally the check for a valid profile data
pointer can be done earlier to avoid unnecessary locking in a hot path.
Package: kernel
Debian
CVE-2023-52774: linux - In the Linux kernel, the following vulnerability has been resolved: s390/dasd: ...
vendor_debian·2023·CVSS 5.5
CVE-2023-52774 [MEDIUM] CVE-2023-52774: linux - In the Linux kernel, the following vulnerability has been resolved: s390/dasd: ...
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.
Scope: local
bookworm: resolved (fixed in 6.1.66-1)
bullseye: resolved (fixed in 5.1
OSV
CVE-2023-52774: In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start()
osv·2024-05-21·CVSS 5.5
CVE-2023-52774 [MEDIUM] CVE-2023-52774: In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start()
In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data pointer can be done earlier to avoid unnecessary locking in a hot path.
GHSA
GHSA-2j3v-48pv-mvcj: In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start(
ghsa_unreviewed·2024-05-21
CVE-2023-52774 [MEDIUM] CWE-476 GHSA-2j3v-48pv-mvcj: In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start(
In the Linux kernel, the following vulnerability has been resolved:
s390/dasd: protect device queue against concurrent access
In dasd_profile_start() the amount of requests on the device queue are
counted. The access to the device queue is unprotected against
concurrent access. With a lot of parallel I/O, especially with alias
devices enabled, the device queue can change while dasd_profile_start()
is accessing the queue. In the worst case this leads to a kernel panic
due to incorrect pointer accesses.
Fix this by taking the device lock before accessing the queue and
counting the requests. Additionally the check for a valid profile data
pointer can be done earlier to avoid unnecessary locking in a hot path.
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/6062c527d0403cef27c54b91ac8390c3a497b250https://git.kernel.org/stable/c/9372aab5d0ff621ea203c8c603e7e5f75e888240https://git.kernel.org/stable/c/c841de6247e94e07566d57163d3c0d8b29278f7ahttps://git.kernel.org/stable/c/db46cd1e0426f52999d50fa72cfa97fa39952885https://git.kernel.org/stable/c/dc96fde8fcb2b896fd6c64802a7f4ece2e69b0behttps://git.kernel.org/stable/c/ebdc569a07a3e8dbe66b4184922ad6f88ac0b96fhttps://git.kernel.org/stable/c/f1ac7789406e2ca9ac51c41ad2daa597f47bdd4dhttps://git.kernel.org/stable/c/f75617cc8df4155374132f0b500b0b3ebb967458https://git.kernel.org/stable/c/6062c527d0403cef27c54b91ac8390c3a497b250https://git.kernel.org/stable/c/9372aab5d0ff621ea203c8c603e7e5f75e888240https://git.kernel.org/stable/c/c841de6247e94e07566d57163d3c0d8b29278f7ahttps://git.kernel.org/stable/c/db46cd1e0426f52999d50fa72cfa97fa39952885https://git.kernel.org/stable/c/dc96fde8fcb2b896fd6c64802a7f4ece2e69b0behttps://git.kernel.org/stable/c/ebdc569a07a3e8dbe66b4184922ad6f88ac0b96fhttps://git.kernel.org/stable/c/f1ac7789406e2ca9ac51c41ad2daa597f47bdd4dhttps://git.kernel.org/stable/c/f75617cc8df4155374132f0b500b0b3ebb967458
2024-05-21
Published