eventfs: Initialize ei->children and ei->list in init_ei()
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.157, 6.12.109, 6.18.50, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: eventfs: Initialize ei->children and ei->list in init_ei() eventfs_create_dir() allocates the eventfs_inode and initializes it with init_ei(). But this does not initialize the eventfs_inode list_heads. If the eventfs_create_dir() fails due to memory pressure, it will call free_ei() before it initialized the lists, and that checks to make sure the eventfs_inode has no children. But because the list wasn't initialized, it will give a false warning. Fix it by moving the list initialization into init_ei(). [ Rewrote change log ]
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 35ee34c0f6d578c9d245438ca29bf2e7024a5a65 · fixed in 069729282fbecfaa8a54062266c338ed23f08005; From 5790b1fb3d672d9a1fe3881a7181dfdbe741568f · fixed in c480f8af173d5b19c6d9c4311df6bbe352face9e; From 5790b1fb3d672d9a1fe3881a7181dfdbe741568f · fixed in 5333e18e6b425fcc39c7fea89e3949a2a98bc5e4; From 5790b1fb3d672d9a1fe3881a7181dfdbe741568f · fixed in 76e0f85f650738d768449dbccbc7c55d05f5b609; From 5790b1fb3d672d9a1fe3881a7181dfdbe741568f · fixed in 1704aaaf5d22bc765c168402350d191e24e245bc; From 6.6.18 · fixed in 6.6.157
- Linux Linux
6.7
- KernelLinux
fixed in 6.6.157; From 6.7.0 · fixed in 6.12.109; fixed in 6.18.50; From 6.13.0 · fixed in 7.2.4