Security readout for executives and security teams
Plain-English summary
This is a Linux kernel memory-leak vulnerability in recordmcount. The available CVE data rates it medium because exploitation requires local access and low privileges, but the modeled impact is loss of availability. There is no cited evidence of active exploitation.
Executive priority
Handle through normal kernel patch governance, with higher priority for shared systems, build infrastructure, and environments with many local users. No source provided supports emergency internet-facing remediation.
Technical view
The issue is CWE-401 in recordmcount's uwrite function: a realloc failure path can null file_append without freeing it. The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact and no confidentiality or integrity impact.
Likely exposure
Exposure appears limited to affected Linux kernel versions listed in the CVE data. The CVSS vector indicates a local authenticated attacker model, not remote unauthenticated exposure. Public-facing services are not directly identified in the supplied sources.
Exploitation context
CISA KEV status is false, and the supplied sources do not cite active exploitation, public exploit use, or weaponized techniques. Treat exploitation evidence as unconfirmed unless vendor or threat-intelligence sources add new information.
Researcher notes
The supplied evidence identifies the bug class, affected Linux versions, CVSS vector, and upstream stable commits. It does not provide distribution mapping, proof-of-concept details, exploit telemetry, or operational indicators. Avoid assuming runtime reachability beyond the local attack model stated by CVSS.
Mitigation direction
- Identify Linux systems running affected kernel versions listed in the CVE record.
- Prioritize kernel updates from the Linux stable branches or your OS vendor.
- Use vendor advisories for distribution-specific package names and backport status.
- Restrict local shell access on systems where patching is delayed.
Validation and detection
- Inventory kernel versions across servers, workstations, and build hosts.
- Compare installed kernels with the affected and fixed versions in vendor guidance.
- Confirm patched systems include the relevant Linux stable recordmcount fixes.
- Monitor vendor advisories for distribution-specific remediation notes.
Public sources used
- CVE Program
- CVE List V5
- Linux stable commit bd39f68a309a947670379bf9a39b16c584f86ddb
- Linux stable commit 444ec005404cead222ebce2561a9451c9ee5ad89
- Linux stable commit 3ed95a6f6c646e8bb15c354536e0ab10e8f39c08
- Linux stable commit 2d9ca5f62f2ba160ff9c9be4adf401c46c04edef
- Linux stable commit ff70ad9159fbb566b2c15724f44207e8deccd527
- Linux stable commit 895130e63c93926f07caf5db286b97bd27b81de9
- Linux stable commit 25c9b185f121812cbc215fdaa1192c6b9025b428
- Linux stable commit fa359d068574d29e7d2f0fdd0ebe4c6a12b5cfb9
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-53318 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/bd39f68a309a947670379bf9a39b16c584f86ddbCVE reference, Linux
- https://git.kernel.org/stable/c/444ec005404cead222ebce2561a9451c9ee5ad89CVE reference, Linux
- https://git.kernel.org/stable/c/3ed95a6f6c646e8bb15c354536e0ab10e8f39c08CVE reference, Linux
- https://git.kernel.org/stable/c/2d9ca5f62f2ba160ff9c9be4adf401c46c04edefCVE reference, Linux
- https://git.kernel.org/stable/c/ff70ad9159fbb566b2c15724f44207e8deccd527CVE reference, Linux
- https://git.kernel.org/stable/c/895130e63c93926f07caf5db286b97bd27b81de9CVE reference, Linux
- https://git.kernel.org/stable/c/25c9b185f121812cbc215fdaa1192c6b9025b428CVE reference, Linux
- https://git.kernel.org/stable/c/fa359d068574d29e7d2f0fdd0ebe4c6a12b5cfb9CVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.