CVE-2023-53331
published 2025-09-16CVE-2023-53331: In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram…
PriorityP339high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.15%
4.4th percentile
In the Linux kernel, the following vulnerability has been resolved:
pstore/ram: Check start of empty przs during init
After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as
valid"), initialization would assume a prz was valid after seeing that
the buffer_size is zero (regardless of the buffer start position). This
unchecked start value means it could be outside the bounds of the buffer,
leading to future access panics when written to:
sysdump_panic_event+0x3b4/0x5b8
atomic_notifier_call_chain+0x54/0x90
panic+0x1c8/0x42c
die+0x29c/0x2a8
die_kernel_fault+0x68/0x78
__do_kernel_fault+0x1c4/0x1e0
do_bad_area+0x40/0x100
do_translation_fault+0x68/0x80
do_mem_abort+0x68/0xf8
el1_da+0x1c/0xc0
__raw_writeb+0x38/0x174
__memcpy_toio+0x40/0xac
persistent_ram_update+0x44/0x12c
persistent_ram_write+0x1a8/0x1b8
ramoops_pstore_write+0x198/0x1e8
pstore_console_write+0x94/0xe0
...
To avoid this, also check if the prz start is 0 during the initialization
phase. If not, the next prz sanity check case will discover it (start >
size) and zap the buffer back to a sane state.
[kees: update commit log with backtrace and clarifications]
Affected
36 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.55-1 (bookworm) | linux 6.1.55-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | — | — |
| linux | linux | >= 265242d82a3c6a8bd9120d06b4801f8d7ae9a346 < c807ccdd812d18985860504b503899f3140a9549 | c807ccdd812d18985860504b503899f3140a9549 |
| linux | linux | >= 3.18.133 < 3.19 | 3.19 |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < e972231db29b5d1dccc13bf9d5ba55b6979a69ed | e972231db29b5d1dccc13bf9d5ba55b6979a69ed |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < dc2f60de9a7d3efd982440117dab5579898d808c | dc2f60de9a7d3efd982440117dab5579898d808c |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < fedecaeef88899d940b69368c996e8b3b0b8650d | fedecaeef88899d940b69368c996e8b3b0b8650d |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < e95d7a8a6edd14f8fab44c777dd7281db91f6ae2 | e95d7a8a6edd14f8fab44c777dd7281db91f6ae2 |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < f77990358628b01bdc03752126ff5f716ea37615 | f77990358628b01bdc03752126ff5f716ea37615 |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < 25fb4e3402d46f425ec135ef6f09792a4c1b3003 | 25fb4e3402d46f425ec135ef6f09792a4c1b3003 |
| linux | linux | >= 30696378f68a9e3dad6bfe55938b112e72af00c2 < fe8c3623ab06603eb760444a032d426542212021 | fe8c3623ab06603eb760444a032d426542212021 |
| linux | linux | >= 4.14.96 < 4.14.326 | 4.14.326 |
| linux | linux | >= 4.19.18 < 4.19.295 | 4.19.295 |
| linux | linux | >= 4.20.5 < 4.21 | 4.21 |
| linux | linux | >= 4.4.172 < 4.5 | 4.5 |
| linux | linux | >= 4.9.153 < 4.10 | 4.10 |
| linux | linux | >= e1e3a46706bd4037e8b7407dc660ae6e05b8ac56 < 89312657337e6e03ad6e9ea1a462bd9c158c85c8 | 89312657337e6e03ad6e9ea1a462bd9c158c85c8 |
| linux | linux_kernel | >= 0 < 5.10.197-1 | 5.10.197-1 |
| linux | linux_kernel | >= 0 < 6.1.55-1 | 6.1.55-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
| linux | linux_kernel | >= 0 < 6.5.3-1 | 6.5.3-1 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
osv7.8HIGH
vendor_debian7.8HIGH
vendor_redhat7.8HIGH
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.
GHSA
GHSA-v4w9-9vv8-m7qj: In the Linux kernel, the following vulnerability has been resolved:
pstore/ram: Check start of empty przs during init
After commit 30696378f68a ("ps
ghsa_unreviewed·2025-09-16
CVE-2023-53331 [HIGH] CWE-787 GHSA-v4w9-9vv8-m7qj: In the Linux kernel, the following vulnerability has been resolved:
pstore/ram: Check start of empty przs during init
After commit 30696378f68a ("ps
In the Linux kernel, the following vulnerability has been resolved:
pstore/ram: Check start of empty przs during init
After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as
valid"), initialization would assume a prz was valid after seeing that
the buffer_size is zero (regardless of the buffer start position). This
unchecked start value means it could be outside the bounds of the buffer,
leading to future access panics when written to:
sysdump_panic_event+0x3b4/0x5b8
atomic_notifier_call_chain+0x54/0x90
panic+0x1c8/0x42c
die+0x29c/0x2a8
die_kernel_fault+0x68/0x78
__do_kernel_fault+0x1c4/0x1e0
do_bad_area+0x40/0x100
do_translation_fault+0x68/0x80
do_mem_abort+0x68/0xf8
el1_da+0x1c/0xc0
__raw_writeb+0x38/0x174
__memcpy_toio+0x40/0xac
persistent_ram_update+0x44/0x12c
persiste
OSV
CVE-2023-53331: In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("psto
osv·2025-09-16·CVSS 7.8
CVE-2023-53331 [HIGH] CVE-2023-53331: In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("psto
In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as valid"), initialization would assume a prz was valid after seeing that the buffer_size is zero (regardless of the buffer start position). This unchecked start value means it could be outside the bounds of the buffer, leading to future access panics when written to: sysdump_panic_event+0x3b4/0x5b8 atomic_notifier_call_chain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 die_kernel_fault+0x68/0x78 __do_kernel_fault+0x1c4/0x1e0 do_bad_area+0x40/0x100 do_translation_fault+0x68/0x80 do_mem_abort+0x68/0xf8 el1_da+0x1c/0xc0 __raw_writeb+0x38/0x174 __memcpy_toio+0x40/0xac persistent_ram_update+0x44/0x12c persistent_
Red Hat
kernel: pstore/ram: Check start of empty przs during init
vendor_redhat·2025-09-16·CVSS 7.8
CVE-2023-53331 [HIGH] CWE-129 kernel: pstore/ram: Check start of empty przs during init
kernel: pstore/ram: Check start of empty przs during init
In the Linux kernel, the following vulnerability has been resolved:
pstore/ram: Check start of empty przs during init
After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as
valid"), initialization would assume a prz was valid after seeing that
the buffer_size is zero (regardless of the buffer start position). This
unchecked start value means it could be outside the bounds of the buffer,
leading to future access panics when written to:
sysdump_panic_event+0x3b4/0x5b8
atomic_notifier_call_chain+0x54/0x90
panic+0x1c8/0x42c
die+0x29c/0x2a8
die_kernel_fault+0x68/0x78
__do_kernel_fault+0x1c4/0x1e0
do_bad_area+0x40/0x100
do_translation_fault+0x68/0x80
do_mem_abort+0x68/0xf8
el1_da+0x1c/0xc0
__raw_writeb+0x38/0x174
__memcpy_
Debian
CVE-2023-53331: linux - In the Linux kernel, the following vulnerability has been resolved: pstore/ram:...
vendor_debian·2023·CVSS 7.8
CVE-2023-53331 [HIGH] CVE-2023-53331: linux - In the Linux kernel, the following vulnerability has been resolved: pstore/ram:...
In the Linux kernel, the following vulnerability has been resolved: pstore/ram: Check start of empty przs during init After commit 30696378f68a ("pstore/ram: Do not treat empty buffers as valid"), initialization would assume a prz was valid after seeing that the buffer_size is zero (regardless of the buffer start position). This unchecked start value means it could be outside the bounds of the buffer, leading to future access panics when written to: sysdump_panic_event+0x3b4/0x5b8 atomic_notifier_call_chain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 die_kernel_fault+0x68/0x78 __do_kernel_fault+0x1c4/0x1e0 do_bad_area+0x40/0x100 do_translation_fault+0x68/0x80 do_mem_abort+0x68/0xf8 el1_da+0x1c/0xc0 __raw_writeb+0x38/0x174 __memcpy_toio+0x40/0xac persistent_ram_update+0x44/0x12c persistent_
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/25fb4e3402d46f425ec135ef6f09792a4c1b3003https://git.kernel.org/stable/c/89312657337e6e03ad6e9ea1a462bd9c158c85c8https://git.kernel.org/stable/c/c807ccdd812d18985860504b503899f3140a9549https://git.kernel.org/stable/c/dc2f60de9a7d3efd982440117dab5579898d808chttps://git.kernel.org/stable/c/e95d7a8a6edd14f8fab44c777dd7281db91f6ae2https://git.kernel.org/stable/c/e972231db29b5d1dccc13bf9d5ba55b6979a69edhttps://git.kernel.org/stable/c/f77990358628b01bdc03752126ff5f716ea37615https://git.kernel.org/stable/c/fe8c3623ab06603eb760444a032d426542212021https://git.kernel.org/stable/c/fedecaeef88899d940b69368c996e8b3b0b8650d
2025-09-16
Published