CVE-2023-53318 json
recordmcount: Fix memory leaks in the uwrite function
published 2025-09-16 13 mo ago modified 2026-06-17 4 mo ago also EUVD-2023-59943
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
recordmcount: Fix memory leaks in the uwrite function
Common realloc mistake: 'file_append' nulled but not freed upon failure
Patch / fix
- Linux Linux 3.3, 3.5, 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.113, 6.1.30, 6.3.4, 6.4
- linux Debian 12 6.1.37-1
- linux Debian 14, Debian 13 6.3.7-1
debian advisories DEBIAN-CVE-2023-53318
- linux Ubuntu 20.04 LTS 5.4.0-162.179
- linux Ubuntu 22.04 LTS 5.15.0-83.92
- linux-aws Ubuntu 20.04 LTS 5.4.0-1109.118
- linux-aws Ubuntu 22.04 LTS 5.15.0-1044.49
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1112.121
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1041.49
- linux-gke Ubuntu 22.04 LTS 5.15.0-1041.46
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1056.61
ubuntu advisories UBUNTU-CVE-2023-53318
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/bd39f68a309a947670379bf9a39b16c584f86ddb commit
- git.kernel.org/stable/c/444ec005404cead222ebce2561a9451c9ee5ad89 commit
- git.kernel.org/stable/c/3ed95a6f6c646e8bb15c354536e0ab10e8f39c08 commit
- git.kernel.org/stable/c/2d9ca5f62f2ba160ff9c9be4adf401c46c04edef commit
- git.kernel.org/stable/c/ff70ad9159fbb566b2c15724f44207e8deccd527 commit
- git.kernel.org/stable/c/895130e63c93926f07caf5db286b97bd27b81de9 commit
- git.kernel.org/stable/c/25c9b185f121812cbc215fdaa1192c6b9025b428 commit
- git.kernel.org/stable/c/fa359d068574d29e7d2f0fdd0ebe4c6a12b5cfb9 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53318 updated
kernel: recordmcount: Fix memory leaks in the uwrite function
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 9 mo ago
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/bd39f68a309a947670379bf9a39b16c584f86ddb
patch
-
git.kernel.org
/stable/c/444ec005404cead222ebce2561a9451c9ee5ad89
patch
-
git.kernel.org
/stable/c/3ed95a6f6c646e8bb15c354536e0ab10e8f39c08
patch
-
git.kernel.org
/stable/c/2d9ca5f62f2ba160ff9c9be4adf401c46c04edef
patch
-
git.kernel.org
/stable/c/ff70ad9159fbb566b2c15724f44207e8deccd527
patch
-
git.kernel.org
/stable/c/895130e63c93926f07caf5db286b97bd27b81de9
patch
-
git.kernel.org
/stable/c/25c9b185f121812cbc215fdaa1192c6b9025b428
patch
-
git.kernel.org
/stable/c/fa359d068574d29e7d2f0fdd0ebe4c6a12b5cfb9
patch
Sources
- CVE List CVE-2023-53318
- NVD CVE-2023-53318
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.