CVE-2023-53331

See a problem?
Please try reporting it to the source first.
Source
https://cve.org/CVERecord?id=CVE-2023-53331
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53331.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2023-53331
Downstream
Related
Published
2025-09-16T16:12:06.788Z
Modified
2026-03-11T07:44:40.513509Z
Severity
  • 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
Summary
pstore/ram: Check start of empty przs during init
Details

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:

sysdumppanicevent+0x3b4/0x5b8 atomicnotifiercallchain+0x54/0x90 panic+0x1c8/0x42c die+0x29c/0x2a8 diekernel_fault+0x68/0x78 __dokernelfault+0x1c4/0x1e0 dobadarea+0x40/0x100 dotranslationfault+0x68/0x80 domemabort+0x68/0xf8 el1_da+0x1c/0xc0 __raw_writeb+0x38/0x174 _memcpytoio+0x40/0xac persistentramupdate+0x44/0x12c persistentramwrite+0x1a8/0x1b8 ramoopspstorewrite+0x198/0x1e8 pstoreconsolewrite+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]

Database specific 
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53331.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
e1e3a46706bd4037e8b7407dc660ae6e05b8ac56
Fixed
89312657337e6e03ad6e9ea1a462bd9c158c85c8
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
265242d82a3c6a8bd9120d06b4801f8d7ae9a346
Fixed
c807ccdd812d18985860504b503899f3140a9549
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
30696378f68a9e3dad6bfe55938b112e72af00c2
Fixed
e972231db29b5d1dccc13bf9d5ba55b6979a69ed
Fixed
dc2f60de9a7d3efd982440117dab5579898d808c
Fixed
fedecaeef88899d940b69368c996e8b3b0b8650d
Fixed
e95d7a8a6edd14f8fab44c777dd7281db91f6ae2
Fixed
f77990358628b01bdc03752126ff5f716ea37615
Fixed
25fb4e3402d46f425ec135ef6f09792a4c1b3003
Fixed
fe8c3623ab06603eb760444a032d426542212021
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Last affected
ec7f99261da9a20d63cbd273511a11a2efe698f2
Last affected
f250e4c562a3bd106575032666e9ef46f31231f8
Last affected
fffdbf586866e9500b53c9d4b061d3983720375a
Last affected
9e969ba431b46b1891c88cea36f722f3bfe8a180

Database specific

source 
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53331.json"