CVE-2023-53331pstore/ram: Check start of empty przs during init
- 7.8HighCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
Published
- 11 months later
· 11 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CISA-ADPADP (enrichment) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected e1e3a46706bd4037e8b7407dc660ae6e05b8ac56 – < 89312657337e6e03ad6e9ea1a462bd9c158c85c8
- affected 265242d82a3c6a8bd9120d06b4801f8d7ae9a346 – < c807ccdd812d18985860504b503899f3140a9549
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < e972231db29b5d1dccc13bf9d5ba55b6979a69ed
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < dc2f60de9a7d3efd982440117dab5579898d808c
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < fedecaeef88899d940b69368c996e8b3b0b8650d
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < e95d7a8a6edd14f8fab44c777dd7281db91f6ae2
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < f77990358628b01bdc03752126ff5f716ea37615
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < 25fb4e3402d46f425ec135ef6f09792a4c1b3003
- affected 30696378f68a9e3dad6bfe55938b112e72af00c2 – < fe8c3623ab06603eb760444a032d426542212021
- affected ec7f99261da9a20d63cbd273511a11a2efe698f2
- affected f250e4c562a3bd106575032666e9ef46f31231f8
- affected fffdbf586866e9500b53c9d4b061d3983720375a
- affected 9e969ba431b46b1891c88cea36f722f3bfe8a180
- affected 4.14.96 – < 4.14.326
- affected 4.19.18 – < 4.19.295
- affected 3.18.133 – < 3.19
- affected 4.4.172 – < 4.5
- affected 4.9.153 – < 4.10
- affected 4.20.5 – < 4.21
- affected 5.0
- unaffected < 5.0
- unaffected 4.14.326 – ≤ 4.14.*
- unaffected 4.19.295 – ≤ 4.19.*
- unaffected 5.4.257 – ≤ 5.4.*
- unaffected 5.10.195 – ≤ 5.10.*
- unaffected 5.15.132 – ≤ 5.15.*
- unaffected 6.1.53 – ≤ 6.1.*
- unaffected 6.4.16 – ≤ 6.4.*
- unaffected 6.5.3 – ≤ 6.5.*
- unaffected 6.6 – ≤ *
References
References9
- https://git.kernel.org/stable/c/89312657337e6e03ad6e9ea1a462bd9c158c85c8 (opens in a new tab)
- https://git.kernel.org/stable/c/c807ccdd812d18985860504b503899f3140a9549 (opens in a new tab)
- https://git.kernel.org/stable/c/e972231db29b5d1dccc13bf9d5ba55b6979a69ed (opens in a new tab)
- https://git.kernel.org/stable/c/dc2f60de9a7d3efd982440117dab5579898d808c (opens in a new tab)
- https://git.kernel.org/stable/c/fedecaeef88899d940b69368c996e8b3b0b8650d (opens in a new tab)
- https://git.kernel.org/stable/c/e95d7a8a6edd14f8fab44c777dd7281db91f6ae2 (opens in a new tab)
- https://git.kernel.org/stable/c/f77990358628b01bdc03752126ff5f716ea37615 (opens in a new tab)
- https://git.kernel.org/stable/c/25fb4e3402d46f425ec135ef6f09792a4c1b3003 (opens in a new tab)
- https://git.kernel.org/stable/c/fe8c3623ab06603eb760444a032d426542212021 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2023-59930 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2023-53331)Record last updated .