CVE-2026-89525 Linux CVE debrief

Who should care

Linux kernel maintainers, Linux distribution maintainers, and users of Linux systems that utilize UDF filesystems should assess exposure and prioritize verification of UDF implementation integrity.

Why it matters

A vulnerability in the Linux kernel's UDF implementation has been addressed. Linux kernel maintainers and users should assess exposure and prioritize verification of UDF implementation integrity.

• Potential slab-out-of-bounds read in the Linux kernel's UDF implementation.
• Verification of UDF implementation integrity is necessary to prevent potential issues.
• Monitoring kernel logs for slab-out-of-bounds read attempts may be required.

Technical summary

The Linux kernel's UDF implementation has a vulnerability in the `udf_get_pblock_virt15()` function. The function did not properly handle VAT indexes, allowing for a potential slab-out-of-bounds read. The fix changes the bounds check to treat `s_num_entries` as an exclusive upper bound. Linux kernel maintainers and users should assess exposure and prioritize verification of UDF implementation integrity. A crafted UDF image can request index `s_num_entries`, potentially leading to a slab-out-of-bounds read. The CVE record and associated source references provide details on the vulnerability and its fix.

Defensive priority

Linux kernel maintainers and users should assess exposure and prioritize verification of UDF implementation integrity.

Recommended defensive actions

• Review and apply the provided kernel patches to ensure UDF implementation integrity.
• Verify UDF usage and configuration in Linux kernel deployments.
• Monitor for potential slab-out-of-bounds read attempts in kernel logs.
• Perform a thorough review of UDF implementation integrity.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and associated source references provide details on the vulnerability and its fix. However, the corpus does not establish versions, exploitation, impact, or remediation beyond the provided technical details.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.