Nidhi77777 / linux-4.19.72_CVE-2022-29581

Other
0 stars 0 forks source link

CVE-2023-52444 (High) detected in linuxlinux-4.19.269 - autoclosed #521

Closed mend-bolt-for-github[bot] closed 6 months ago

mend-bolt-for-github[bot] commented 7 months ago

CVE-2023-52444 - High Severity Vulnerability

Vulnerable Library - linuxlinux-4.19.269

The Linux Kernel

Library home page: https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux

Found in base branch: master

Vulnerable Source Files (1)

Vulnerability Details

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to avoid dirent corruption As Al reported in link[1]: f2fs_rename() ... if (old_dir != new_dir && !whiteout) f2fs_set_link(old_inode, old_dir_entry, old_dir_page, new_dir); else f2fs_put_page(old_dir_page, 0); You want correct inumber in the ".." link. And cross-directory rename does move the source to new parent, even if you'd been asked to leave a whiteout in the old place. [1] https://lore.kernel.org/all/20231017055040.GN800259@ZenIV/ With below testcase, it may cause dirent corruption, due to it missed to call f2fs_set_link() to update ".." link to new directory. - mkdir -p dir/foo - renameat2 -w dir/foo bar [ASSERT] (__chk_dots_dentries:1421) --> Bad inode number[0x4] for '..', parent parent ino is [0x3] [FSCK] other corrupted bugs [Fail]

Publish Date: 2024-02-22

URL: CVE-2023-52444

CVSS 3 Score Details (7.8)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.linuxkernelcves.com/cves/CVE-2023-52444

Release Date: 2024-02-22

Fix Resolution: v4.19.306,v5.4.268,v5.10.209,v5.15.148,v6.1.75,v6.6.14,v6.7.2


Step up your Open Source Security Game with Mend here

mend-bolt-for-github[bot] commented 6 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.