fat: release buffer head after rebuilding parent
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f1e6fb0ab451dae8523fbb8c119a653b2730e938 · < 571ea4263d69df1b48578e4314a828ecd0604755| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fat: release buffer head after rebuilding parent
fat_scan_logstart() leaves the matching directory entry's buffer head in sinfo.bh for the caller to release, just like fat_scan().
fat_rebuild_parent() uses the directory entry to rebuild the parent inode for the nostale_ro NFS export path, but does not release sinfo.bh after a successful scan. Release it once fat_build_inode() has consumed the directory entry data.
From the CVE record · Linux
The FAT parent-rebuild path in the Linux kernel does not release a buffer head after a successful directory scan. This affects the nostale_ro NFS export path; the input does not describe an attacker action, authentication requirement, or user interaction.
Engineers running Linux kernels that use the FAT nostale_ro NFS export path should check their kernel versions; affected versions were not provided.