Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 3 days later

    Published

  3. · 3 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-52458, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < 8f6dfa1f1efe6dcca2d43e575491d8fcbe922f62
    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < 5010c27120962c85d2f421d2cf211791c9603503
    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < ef31cc87794731ffcb578a195a2c47d744e25fb8
    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < cb16cc1abda18a9514106d2ac8c8d7abc0be5ed8
    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < bcdc288e7bc008daf38ef0401b53e4a8bb61bbe5
    • affected 633395b67bb222f85bb8f825c7751a54b9ec84ee – < 6f64f866aa1ae6975c95d805ed51d7e9433a0016
  • Linux · Linux

    • affected 4.10
    • unaffected < 4.10
    • unaffected 5.10.215 – ≤ 5.10.*
    • unaffected 5.15.148 – ≤ 5.15.*
    • unaffected 6.1.75 – ≤ 6.1.*
    • unaffected 6.6.14 – ≤ 6.6.*
    • unaffected 6.7.2 – ≤ 6.7.*
    • unaffected 6.8 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-52458 badge
[![CVE-2023-52458](https://cveledger.app/badge/CVE-2023-52458.svg)](https://cveledger.app/cve/CVE-2023-52458)

Record last updated .