hfs: 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.116.19.17.0In the Linux kernel, the following vulnerability has been resolved:
hfs: ensure sb->s_fs_info is always cleaned up
When hfs 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 hfs_fill_super() takes ownership of the filesystem-specific s_fs_info data it was leaked.
Fix this by freeing sb->s_fs_info in hfs_kill_super().
From the CVE record · Linux
The Linux kernel's hfs filesystem can leak filesystem-specific memory when a mount fails after a new superblock is allocated but before hfs_fill_super() takes ownership of that memory. The input does not establish whether an attacker can trigger this condition or whether authentication or user interaction is required.
Operators running Linux kernels with hfs support should check their kernel versions against the vendor advisory; affected versions are not specified.