udf: refactor inode_bmap() to handle error
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.6.596.11.66.12In 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.
From the CVE record · Linux
The Linux kernel’s UDF inode_bmap() did not handle errors from udf_next_aext(), which could affect file operations such as ftruncate. The input does not specify what an attacker could do or whether access, authentication, or user interaction is required.
Engineers running the Linux kernel should check their version against the vendor advisory; affected versions are not specified.