Affects the Linux kernel's UDF driver used across servers, desktops, and devices; allows media-based bypass of integrity checks and risks broad compromise.
CVE-2026-53369
Linux kernel UDF parsing allows CRC bypass via crafted UDF images
Is CVE-2026-53369 being exploited?
Not confirmed. CVE-2026-53369 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.15% probability of exploitation in the next 30 days.
How severe is CVE-2026-53369?
CVE-2026-53369 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53369?
Yes. A fix has been recorded for CVE-2026-53369. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53369 affect?
CVE-2026-53369 affects Linux kernel (UDF filesystem driver), Linux desktops/servers mounting UDF ISOs/USB/DVD images, Embedded devices using UDF for media/firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53369?
Install vendor kernel updates and avoid mounting untrusted UDF/ISO media
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Bypass UDF CRC validation when mounting crafted UDF images, allowing malformed descriptors that can cause kernel memory corruption and possible privilege escalation.
Patch when possible
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 832ab4a882dc9b3c0155490d9993642ef545fd22
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 7d1b6adbf90df6c8941090d5646fbeca25ba9770
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 3dede76d525919bb966f9213e131af685de5ff99
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 50dfaf4a027742b4fcdc3e9305e7199ece9bc6a6
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 31605bbe94557bff721eaf041001169d44ac6f98
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 1873eb81c65d3f849418d7386baa39c439c9fc38
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < fdb26e628d2a211a23815d375bd33bdf863344e2
- affected>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and < 55d41b0a20128e86b9e960dd2e3f0a2d69a18df7
- affected2.6.12
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.