LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52464: EDAC/thunderx: Fix possible out-of-bounds string access

In the Linux kernel, the following vulnerability has been resolved: EDAC/thunderx: Fix possible out-of-bounds string access Enabling -Wstringop-overflow globally exposes a warning for a common bug in the usage of strncat(): drivers/edac/thunderx_edac.c: In function 'thunderx_ocx_com_threaded_isr': drivers/edac/thunderx_edac.c:1136:17: error: 'strncat' specified bound 1024 equals destination size [-Werror=stringop-overflow=] 1136 | strncat(msg, other, OCX_MESSAGE_SIZE); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... 1145 | strncat(msg, other, OCX_MESSAGE_SIZE); ... 1150 | strncat(msg, other, OCX_MESSAGE_SIZE); ... Apparently the author of this driver expected strncat() to behave the way that strlcat() does, which uses the size of the destination buffer as its third argument rather than the length of the source buffer. The result is that there is no check on the size of the allocated buffer. Change it to strlcat(). [ bp: Trim compiler output, fixup commit message. ]

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a memory-safety bug in the ThunderX EDAC driver. A string-building routine used the wrong size limit, creating a possible out-of-bounds access. The sources do not provide CVSS, impact, or active exploitation evidence, so urgency depends mainly on whether affected kernels and this driver are present.

Executive priority

Do not treat this as an emergency without exposure evidence, but include it in normal kernel patching. Escalate priority for systems using ThunderX EDAC on affected kernels or where kernel memory-safety issues are patched on accelerated timelines.

Technical view

The fix changes thunderx_edac.c from strncat() to strlcat() because strncat() was given the destination buffer size as a source-length bound. The CVE notes this left no check on the allocated buffer size. The affected surface is Linux kernels with the EDAC/thunderx code in affected versions.

Likely exposure

Exposure is most likely on Linux systems running affected kernel versions where the ThunderX EDAC driver is built or active. Generic Linux fleets may carry the vulnerable code, but practical exposure depends on kernel configuration, hardware, and distribution backports.

Exploitation context

The bundle shows no KEV listing and no cited source claiming exploitation in the wild. It also does not describe an attacker path, required privileges, or practical impact. Treat exploitation status and business impact as unproven from the provided evidence.

Researcher notes

Evidence is limited to the kernel fix rationale, affected Linux entries, stable commit references, and Debian LTS notices. No CVSS, CWE, exploitability assessment, or impact statement is present in the supplied bundle, so conclusions should remain conservative.

Mitigation direction

  • Update to a kernel release or distro package containing the upstream stable fix.
  • Prioritize affected systems where the ThunderX EDAC driver is enabled or loaded.
  • Use Debian LTS advisories for Debian systems covered by those notices.
  • Check vendor or distribution guidance if kernel backports obscure version matching.

Validation and detection

  • Inventory Linux kernel versions across servers and appliances.
  • Check kernel configuration or loaded modules for EDAC/thunderx presence.
  • Confirm the relevant stable fix commit is present in deployed kernel sources.
  • For Debian hosts, verify installed packages match the referenced LTS advisories.
Prepared
Confidence
medium
Sources
12

Public sources used

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.

cve · low confidence lookup

CVE-2023-52464 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

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

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
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3e, 41003396f932d7f027725c7acebb6a7caa41dc3eunaffected
LinuxLinux4.12, 0, 4.19.306, 5.4.268, 5.10.209, 5.15.148, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

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