CVE-2023-52791
published 2024-05-21CVE-2023-52791: In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers are…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.24%
15.2th percentile
In the Linux kernel, the following vulnerability has been resolved:
i2c: core: Run atomic i2c xfer when !preemptible
Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is
disabled. However, non-atomic i2c transfers require preemption (e.g. in
wait_for_completion() while waiting for the DMA).
panic() calls preempt_disable_notrace() before calling
emergency_restart(). Therefore, if an i2c device is used for the
restart, the xfer should be atomic. This avoids warnings like:
[ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0
[ 12.676926] Voluntary context switch within RCU read-side critical section!
...
[ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114
[ 12.749179] wait_for_completion_timeout from tegra_i2c_wait_completion+0x40/0x70
...
[ 12.994527] atomic_notifier_call_chain from machine_restart+0x34/0x58
[ 13.001050] machine_restart from panic+0x2a8/0x32c
Use !preemptible() instead, which is basically the same check as
pre-v5.2.
Affected
19 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.64-1 (bookworm) | linux 6.1.64-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < 25eb381a736e7ae39a4245ef5c96484eb1073809 | 25eb381a736e7ae39a4245ef5c96484eb1073809 |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < 25284c46b657f48c0f3880a2e0706c70d81182c0 | 25284c46b657f48c0f3880a2e0706c70d81182c0 |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < f6237afabc349c1c7909db00e15d2816519e0d2b | f6237afabc349c1c7909db00e15d2816519e0d2b |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < 185f3617adc8fe45e40489b458f03911f0dec46c | 185f3617adc8fe45e40489b458f03911f0dec46c |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < 8c3fa52a46ff4d208cefb1a462ec94e0043a91e1 | 8c3fa52a46ff4d208cefb1a462ec94e0043a91e1 |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < 3473cf43b9068b9dfef2f545f833f33c6a544b91 | 3473cf43b9068b9dfef2f545f833f33c6a544b91 |
| linux | linux | >= bae1d3a05a8b99bd748168bbf8155a1d047c562e < aa49c90894d06e18a1ee7c095edbd2f37c232d02 | aa49c90894d06e18a1ee7c095edbd2f37c232d02 |
| linux | linux_kernel | >= 0 < 5.10.205-1 | 5.10.205-1 |
| linux | linux_kernel | >= 0 < 6.1.64-1 | 6.1.64-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 | >= 5.11 < 5.15.140 | 5.15.140 |
| linux | linux_kernel | >= 5.16 < 6.1.64 | 6.1.64 |
| linux | linux_kernel | >= 5.2 < 5.4.262 | 5.4.262 |
| linux | linux_kernel | >= 5.5 < 5.10.202 | 5.10.202 |
| linux | linux_kernel | >= 6.2 < 6.5.13 | 6.5.13 |
| linux | linux_kernel | >= 6.6 < 6.6.3 | 6.6.3 |
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: i2c: core: Run atomic i2c xfer when !preemptible
vendor_redhat·2024-05-21·CVSS 5.5
CVE-2023-52791 [MEDIUM] CWE-459 kernel: i2c: core: Run atomic i2c xfer when !preemptible
kernel: i2c: core: Run atomic i2c xfer when !preemptible
In the Linux kernel, the following vulnerability has been resolved:
i2c: core: Run atomic i2c xfer when !preemptible
Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is
disabled. However, non-atomic i2c transfers require preemption (e.g. in
wait_for_completion() while waiting for the DMA).
panic() calls preempt_disable_notrace() before calling
emergency_restart(). Therefore, if an i2c device is used for the
restart, the xfer should be atomic. This avoids warnings like:
[ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0
[ 12.676926] Voluntary context switch within RCU read-side critical section!
...
[ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0
Debian
CVE-2023-52791: linux - In the Linux kernel, the following vulnerability has been resolved: i2c: core: ...
vendor_debian·2023·CVSS 5.5
CVE-2023-52791 [MEDIUM] CVE-2023-52791: linux - In the Linux kernel, the following vulnerability has been resolved: i2c: core: ...
In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is disabled. However, non-atomic i2c transfers require preemption (e.g. in wait_for_completion() while waiting for the DMA). panic() calls preempt_disable_notrace() before calling emergency_restart(). Therefore, if an i2c device is used for the restart, the xfer should be atomic. This avoids warnings like: [ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0 [ 12.676926] Voluntary context switch within RCU read-side critical section! ... [ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114 [ 12.749179] wait_for_completion_timeout from tegra_i
GHSA
GHSA-pcw4-494r-vqvf: In the Linux kernel, the following vulnerability has been resolved:
i2c: core: Run atomic i2c xfer when !preemptible
Since bae1d3a05a8b, i2c transfe
ghsa_unreviewed·2024-05-21
CVE-2023-52791 [MEDIUM] GHSA-pcw4-494r-vqvf: In the Linux kernel, the following vulnerability has been resolved:
i2c: core: Run atomic i2c xfer when !preemptible
Since bae1d3a05a8b, i2c transfe
In the Linux kernel, the following vulnerability has been resolved:
i2c: core: Run atomic i2c xfer when !preemptible
Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is
disabled. However, non-atomic i2c transfers require preemption (e.g. in
wait_for_completion() while waiting for the DMA).
panic() calls preempt_disable_notrace() before calling
emergency_restart(). Therefore, if an i2c device is used for the
restart, the xfer should be atomic. This avoids warnings like:
[ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0
[ 12.676926] Voluntary context switch within RCU read-side critical section!
...
[ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114
[ 12.749179] wait_for_completion_timeout from teg
OSV
CVE-2023-52791: In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers
osv·2024-05-21·CVSS 5.5
CVE-2023-52791 [MEDIUM] CVE-2023-52791: In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers
In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is disabled. However, non-atomic i2c transfers require preemption (e.g. in wait_for_completion() while waiting for the DMA). panic() calls preempt_disable_notrace() before calling emergency_restart(). Therefore, if an i2c device is used for the restart, the xfer should be atomic. This avoids warnings like: [ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0 [ 12.676926] Voluntary context switch within RCU read-side critical section! ... [ 12.742376] schedule_timeout from wait_for_completion_timeout+0x90/0x114 [ 12.749179] wait_for_completion_timeout from tegra_i
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/185f3617adc8fe45e40489b458f03911f0dec46chttps://git.kernel.org/stable/c/25284c46b657f48c0f3880a2e0706c70d81182c0https://git.kernel.org/stable/c/25eb381a736e7ae39a4245ef5c96484eb1073809https://git.kernel.org/stable/c/3473cf43b9068b9dfef2f545f833f33c6a544b91https://git.kernel.org/stable/c/8c3fa52a46ff4d208cefb1a462ec94e0043a91e1https://git.kernel.org/stable/c/aa49c90894d06e18a1ee7c095edbd2f37c232d02https://git.kernel.org/stable/c/f6237afabc349c1c7909db00e15d2816519e0d2bhttps://git.kernel.org/stable/c/185f3617adc8fe45e40489b458f03911f0dec46chttps://git.kernel.org/stable/c/25284c46b657f48c0f3880a2e0706c70d81182c0https://git.kernel.org/stable/c/25eb381a736e7ae39a4245ef5c96484eb1073809https://git.kernel.org/stable/c/3473cf43b9068b9dfef2f545f833f33c6a544b91https://git.kernel.org/stable/c/8c3fa52a46ff4d208cefb1a462ec94e0043a91e1https://git.kernel.org/stable/c/aa49c90894d06e18a1ee7c095edbd2f37c232d02https://git.kernel.org/stable/c/f6237afabc349c1c7909db00e15d2816519e0d2b
2024-05-21
Published