Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2021-47656 | First vendor Publication | 2025-02-26 |
Vendor | Cve | Last vendor Modification | 2025-03-24 |
Security-Database Scoring CVSS v3
Cvss vector : N/A | |||
---|---|---|---|
Overall CVSS Score | NA | ||
Base Score | NA | Environmental Score | NA |
impact SubScore | NA | Temporal Score | NA |
Exploitabality Sub Score | NA | ||
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
In the Linux kernel, the following vulnerability has been resolved: jffs2: fix use-after-free in jffs2_clear_xattr_subsystem When we mount a jffs2 image, assume that the first few blocks of the image are normal and contain at least one xattr-related inode, but the next block is abnormal. As a result, an error is returned in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then called in jffs2_build_filesystem() and then again in jffs2_do_fill_super(). Finally we can observe the following report: Call Trace: Allocated by task 719: Freed by task 719: The buggy address belongs to the object at ffff8881243384b8 The triggering of the BUG is shown in the following stack: ----------------------------------------------------------- jffs2_fill_super An error is returned in jffs2_do_mount_fs(). If the error is returned by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to be executed. If the error is returned by jffs2_build_filesystem(), the jffs2_clear_xattr_subsystem() also does not need to be executed again. So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root' to fix this UAF problem. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-47656 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2025-06-26 01:53:00 |
|
2025-06-25 12:17:14 |
|
2025-06-24 01:57:29 |
|
2025-05-27 01:52:35 |
|
2025-03-28 17:21:06 |
|
2025-03-28 13:28:36 |
|
2025-03-28 02:42:59 |
|
2025-03-25 00:21:46 |
|
2025-02-27 21:20:35 |
|
2025-02-26 17:20:34 |
|