LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53423: objtool: Fix memory leak in create_static_call_sections()

In the Linux kernel, the following vulnerability has been resolved: objtool: Fix memory leak in create_static_call_sections() strdup() allocates memory for key_name. We need to release the memory in the following error paths. Add free() to avoid memory leak.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-53423 is a Linux kernel memory leak in objtool error handling. The sourced impact is availability only, with local low-privilege access required and no confidentiality or integrity impact stated. Treat it as a maintenance-priority kernel issue, not an emergency based on the provided evidence.

Executive priority

Schedule remediation through standard kernel update cycles. Escalate only for systems where local users can repeatedly trigger availability failures or where vendor guidance indicates broader operational impact.

Technical view

create_static_call_sections() allocated key_name with strdup() and failed to free it on some error paths, causing CWE-401 memory leak behavior. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, unchanged scope, and high availability impact.

Likely exposure

Exposure is limited to Linux versions identified in the source bundle, including 5.10-era through 6.3 entries. Because the source does not map distro packages, validate against your vendor kernel advisories and package metadata before declaring systems affected.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization. The attack requirements are local access with low privileges, and the documented impact is resource leakage leading to availability risk.

Researcher notes

The evidence is narrow: a memory leak fix in Linux objtool error paths, mapped to CWE-401 and CVSS 5.5. The source bundle does not provide distro package names, runtime trigger details, proof of exploitation, or compensating controls.

Mitigation direction

  • Update affected Linux kernels to vendor releases containing the referenced stable fixes.
  • Check your Linux distribution advisory for exact fixed package versions.
  • Prioritize build hosts and systems running affected kernel branches.
  • Track this through normal kernel patch management unless vendor guidance elevates urgency.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and build environments.
  • Compare installed kernel packages with vendor advisories for CVE-2023-53423.
  • Confirm whether referenced stable commits are present in maintained source trees.
  • Document systems still on affected branches for patch scheduling.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-53423 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-53423Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux1e7e47883830aae5e8246a22ca2fc6883c61acdf, 1e7e47883830aae5e8246a22ca2fc6883c61acdf, 1e7e47883830aae5e8246a22ca2fc6883c61acdf, 1e7e47883830aae5e8246a22ca2fc6883c61acdf, 1e7e47883830aae5e8246a22ca2fc6883c61acdfunaffected
LinuxLinux5.10, 0, 5.10.173, 5.15.100, 6.1.18, 6.2.5, 6.3affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-401 · source CWE mapping

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.