- Vulnerability/
- CVE-2024-57924
CVE-2024-57924: fs: relax assertions on failure to encode file handles
First published: Sun Jan 19 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: fs: relax assertions on failure to encode file handles Encoding file handles is usually performed by a filesystem >encode_fh() method that may fail for various reasons. The legacy users of exportfs_encode_fh(), namely, nfsd and name_to_handle_at(2) syscall are ready to cope with the possibility of failure to encode a file handle. There are a few other users of exportfs_encode_{fh,fid}() that currently have a WARN_ON() assertion when ->encode_fh() fails. Relax those assertions because they are wrong. The second linked bug report states commit 16aac5ad1fa9 ("ovl: support encoding non-decodable file handles") in v6.6 as the regressing commit, but this is not accurate. The aforementioned commit only increases the chances of the assertion and allows triggering the assertion with the reproducer using overlayfs, inotify and drop_caches. Triggering this assertion was always possible with other filesystems and other reasons of ->encode_fh() failures and more particularly, it was also possible with the exact same reproducer using overlayfs that is mounted with options index=on,nfs_export=on also on kernels < v6.6. Therefore, I am not listing the aforementioned commit as a Fixes commit. Backport hint: this patch will have a trivial conflict applying to v6.6.y, and other trivial conflicts applying to stable kernels < v6.6.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=6.6 | |
| debian/linux | <=5.10.223-1<=5.10.234-1<=6.1.129-1<=6.1.128-1 | 6.12.20-1 6.12.21-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/974e3fe0ac61de85015bbe5a4990cf4127b304b2
- https://git.kernel.org/stable/c/adcde2872f8fc399b249758ae1990dcd53b694ea
- https://git.kernel.org/stable/c/f47c834a9131ae64bee3c462f4e610c67b0a000f
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-57924
- https://nvd.nist.gov/vuln/detail/CVE-2024-57924
- https://launchpad.net/bugs/cve/CVE-2024-57924
- https://security-tracker.debian.org/tracker/CVE-2024-57924
- https://ubuntu.com/security/CVE-2024-57924
- https://git.kernel.org/linus/974e3fe0ac61de85015bbe5a4990cf4127b304b2
Frequently Asked Questions
What is the severity of CVE-2024-57924?
The severity of CVE-2024-57924 has been classified as moderate due to its potential impact on file handle encoding in the Linux kernel.
How do I fix CVE-2024-57924?
To fix CVE-2024-57924, upgrading to the latest version of the Linux kernel that incorporates the patch is recommended.
Which versions of the Linux kernel are affected by CVE-2024-57924?
CVE-2024-57924 affects Linux kernel versions from 6.6 and earlier.
What does CVE-2024-57924 exploit?
CVE-2024-57924 exploits the failure in encoding file handles, which could lead to potential security issues in filesystems utilizing exportfs_encode_fh().
What are the implications of CVE-2024-57924?
The implications of CVE-2024-57924 include potential unauthorized access or behavior alterations due to faulty file handle encoding in the Linux kernel.
- agent/type
- agent/first-publish-date
- agent/title
- agent/author
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- collector/mitre-cve
- source/MITRE
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/source
- agent/description
- agent/tags
- agent/softwarecombine
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian