LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52458: block: add check that partition length needs to be aligned with block size

In the Linux kernel, the following vulnerability has been resolved: block: add check that partition length needs to be aligned with block size Before calling add partition or resize partition, there is no check on whether the length is aligned with the logical block size. If the logical block size of the disk is larger than 512 bytes, then the partition size maybe not the multiple of the logical block size, and when the last sector is read, bio_truncate() will adjust the bio size, resulting in an IO error if the size of the read command is smaller than the logical block size.If integrity data is supported, this will also result in a null pointer dereference when calling bio_integrity_free.

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

Security readout for executives and security teams

Plain-English summary

CVE-2023-52458 is a Linux kernel storage bug. Certain partition sizes could be accepted even when they do not match the disk's logical block size. On affected systems this can cause I/O errors and, where integrity data is supported, a kernel null pointer dereference.

Executive priority

Treat this as a moderate operational risk until vendor exposure is confirmed. It affects kernel storage handling and may disrupt systems in specific configurations, but the provided evidence does not show active exploitation or broad remote attackability.

Technical view

The block layer allowed add or resize partition operations without checking partition length alignment against logical block size. For disks with logical block sizes above 512 bytes, later reads near the partition end may be truncated. With integrity data enabled, the described failure path can dereference a null pointer during bio integrity cleanup.

Likely exposure

Exposure is most likely on Linux systems, appliances, or embedded products using affected kernel builds with disks or virtual block devices whose logical block size is larger than 512 bytes. Debian LTS and Siemens both published downstream references, indicating vendor-packaged products should be checked.

Exploitation context

The source bundle does not show CISA KEV listing, public exploitation, exploit code, or a CVSS score. Evidence supports a reliability and kernel fault risk in specific storage configurations, not confirmed active exploitation.

Researcher notes

Focus validation on the partition add/resize path, logical block size alignment, and integrity-data handling. The affected version data in the bundle is incomplete for precise fleet matching, so vendor package advisories and kernel commit backports are the authoritative remediation source.

Mitigation direction

  • Update to vendor-supported Linux kernel packages containing the referenced stable fixes.
  • Check Debian LTS, Siemens, and other vendor advisories for product-specific guidance.
  • Prioritize storage-heavy servers, appliances, and embedded systems with non-512-byte logical block devices.
  • Avoid unsupported kernel builds where vendor fix status cannot be confirmed.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded products.
  • Identify systems using block devices with logical block sizes greater than 512 bytes.
  • Confirm installed kernels include the relevant stable kernel fix commits or vendor backports.
  • Review storage logs for unusual partition resize, final-sector read, or I/O errors.
Prepared
Confidence
medium
Sources
10

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-52458 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
3ADP providers
9Source 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
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux633395b67bb222f85bb8f825c7751a54b9ec84ee, 633395b67bb222f85bb8f825c7751a54b9ec84ee, 633395b67bb222f85bb8f825c7751a54b9ec84ee, 633395b67bb222f85bb8f825c7751a54b9ec84ee, 633395b67bb222f85bb8f825c7751a54b9ec84ee, 633395b67bb222f85bb8f825c7751a54b9ec84eeunaffected
LinuxLinux4.10, 0, 5.10.215, 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.