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]

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity High

Privileges Required Low

Scope Unchanged

Confidentiality Impact High

Integrity Impact High

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Key SSVC decision points have not yet been added.

Affected Vendors & Products

Vendors Products
Linux
  • Linux Kernel

No data.

No data.

References
Link Providers
https://git.kernel.org/stable/c/25fb4e3402d46f425ec135ef6f09792a4c1b3003 cve-icon cve-icon
https://git.kernel.org/stable/c/89312657337e6e03ad6e9ea1a462bd9c158c85c8 cve-icon cve-icon
https://git.kernel.org/stable/c/c807ccdd812d18985860504b503899f3140a9549 cve-icon cve-icon
https://git.kernel.org/stable/c/dc2f60de9a7d3efd982440117dab5579898d808c cve-icon cve-icon
https://git.kernel.org/stable/c/e95d7a8a6edd14f8fab44c777dd7281db91f6ae2 cve-icon cve-icon
https://git.kernel.org/stable/c/e972231db29b5d1dccc13bf9d5ba55b6979a69ed cve-icon cve-icon
https://git.kernel.org/stable/c/f77990358628b01bdc03752126ff5f716ea37615 cve-icon cve-icon
https://git.kernel.org/stable/c/fe8c3623ab06603eb760444a032d426542212021 cve-icon cve-icon
https://git.kernel.org/stable/c/fedecaeef88899d940b69368c996e8b3b0b8650d cve-icon cve-icon
https://lore.kernel.org/linux-cve-announce/2025091645-CVE-2023-53331-50a3@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2023-53331 cve-icon
https://www.cve.org/CVERecord?id=CVE-2023-53331 cve-icon
History

Wed, 17 Sep 2025 11:00:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Vendors & Products Linux
Linux linux Kernel

Wed, 17 Sep 2025 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 7.0, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

threat_severity

Moderate

Tue, 16 Sep 2025 16:30:00 +0000

Type Values Removed Values Added
Description 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]
Title pstore/ram: Check start of empty przs during init
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2025-09-16T16:12:06.788Z

Updated: 2025-09-16T16:12:06.788Z

Reserved: 2025-09-16T16:08:59.564Z

Link: CVE-2023-53331

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-09-16T17:15:39.597

Modified: 2025-09-17T14:18:55.093

Link: CVE-2023-53331

cve-icon Redhat

Severity : Moderate

Publid Date: 2025-09-16T00:00:00Z

Links: CVE-2023-53331 - Bugzilla