cve/2024/CVE-2024-39469.md

20 lines
1.4 KiB
Markdown
Raw Normal View History

2025-09-29 21:09:30 +02:00
### [CVE-2024-39469](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39469)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=2.6.30%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=2ba466d74ed74f073257f86e61519cb8f8f46184%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)
### Description
In the Linux kernel, the following vulnerability has been resolved:nilfs2: fix nilfs_empty_dir() misjudgment and long loop on I/O errorsThe error handling in nilfs_empty_dir() when a directory folio/page readfails is incorrect, as in the old ext2 implementation, and if thefolio/page cannot be read or nilfs_check_folio() fails, it will falselydetermine the directory as empty and corrupt the file system.In addition, since nilfs_empty_dir() does not immediately return on afailed folio/page read, but continues to loop, this can cause a long loopwith I/O if i_size of the directory's inode is also corrupted, causing thelog writer thread to wait and hang, as reported by syzbot.Fix these issues by making nilfs_empty_dir() immediately return a falsevalue (0) if it fails to get a directory folio/page.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/fkie-cad/nvd-json-data-feeds