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-53506udf: Do not bother merging very long extents

Description

In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 13 months 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-53506, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < d52252a1de4cf96a34f722b0cd8902d8ff78eb57
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 5d029799d381a9ee06209a222cae75f04c5d5304
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 3d20e3b768aff32112bdce8d3219d923ae75f9f1
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 965982feb333aefa9256c0fe188b5f1b958aef63
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 9a8d602f0723586e668bae7e65c832ceb9bcc8bc
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < adac9ac6d2e04ea0782b91a00ba10706002f3ec4
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 7a965da79f2d22601f329cbfce588386b0847544
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced
  • Linux · Linux

    • affected 2.6.12
    • unaffected < 2.6.12
    • unaffected 4.14.308 – ≤ 4.14.*
    • unaffected 4.19.276 – ≤ 4.19.*
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .