LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53211: driver core: location: Free struct acpi_pld_info *pld before return false

In the Linux kernel, the following vulnerability has been resolved: driver core: location: Free struct acpi_pld_info *pld before return false struct acpi_pld_info *pld should be freed before the return of allocation failure, to prevent memory leak, add the ACPI_FREE() to fix it.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory leak in driver-core ACPI location handling. A local authenticated user could potentially trigger resource exhaustion affecting availability. The sources do not indicate data theft, integrity impact, remote access, or active exploitation.

Executive priority

Treat as a normal-priority kernel maintenance issue unless exposed on shared or multi-tenant Linux systems. It is not evidenced as remotely exploitable or actively exploited, but availability impact justifies timely patching through standard kernel update processes.

Technical view

CVE-2023-53211 is CWE-401 in the Linux kernel: struct acpi_pld_info *pld was not freed on an allocation-failure path before returning false. CVSS 3.1 is 5.5, local attack vector, low complexity, low privileges, no user interaction, availability impact high.

Likely exposure

Exposure is limited to systems running affected Linux kernel versions or builds that include the vulnerable driver-core location code before the stable fixes. The bundle does not map affected status to distributions, appliances, or cloud images.

Exploitation context

The provided CVE data marks CISA KEV as false and gives no cited evidence of active exploitation. Exploitation would require local privileges, so risk is highest on shared systems, multi-user hosts, or workloads accepting untrusted local code.

Researcher notes

The source bundle identifies the bug and upstream stable commits but does not provide a reproducer, distro matrix, or exploit evidence. Validate exposure by patch lineage rather than upstream version alone because vendors may backport fixes.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced stable fixes.
  • Check Linux distribution advisories for package-specific fixed versions.
  • Prioritize shared hosts and systems allowing untrusted local users.
  • Follow vendor guidance if backported fixes obscure upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions and vendor package release levels.
  • Confirm whether vendor changelogs include the referenced stable commits.
  • Review affected shared or multi-user systems before lower-risk single-purpose hosts.
  • Track CVE status for later exploitation or distribution-specific guidance.
Prepared
Confidence
medium
Sources
5

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-53211 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
4Source 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-53211Attack 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
LinuxLinuxbc443c31def574e3bfaed50cb493b8305ad79435, bc443c31def574e3bfaed50cb493b8305ad79435, bc443c31def574e3bfaed50cb493b8305ad79435unaffected
LinuxLinux5.19, 0, 6.1.16, 6.2.3, 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.