hfsplus: ensure sb->s_fs_info is always cleaned up
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.18.166.19.67.0In the Linux kernel, the following vulnerability has been resolved:
hfsplus: ensure sb->s_fs_info is always cleaned up
When hfsplus was converted to the new mount api a bug was introduced by changing the allocation pattern of sb->s_fs_info. If setup_bdev_super() fails after a new superblock has been allocated by sget_fc(), but before hfsplus_fill_super() takes ownership of the filesystem-specific s_fs_info data it was leaked.
Fix this by freeing sb->s_fs_info in hfsplus_kill_super().
From the CVE record · Linux
The Linux kernel's hfsplus filesystem can leak filesystem-specific data if setup_bdev_super() fails during mount setup, after a new superblock is allocated but before hfsplus_fill_super() takes ownership of the data. The input does not specify whether an attacker can trigger this failure, or what access or user interaction would be required.
Engineers running Linux kernels with hfsplus support should check their versions; affected versions are not specified.