nday
CVE-2021-47656

jffs2: fix use-after-free in jffs2_clear_xattr_subsystem

Linux / Linux

Fecha de divulgación: . nday aún no tiene constancia de una corrección; eso no significa que no exista parche. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

use-after-free
CWE-416, stated by the ADP CISA-ADP y NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
no authentication required
PR:N in CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA Linux
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
etapa
DIS
divulgación
cvss
7.8 HIGH v3.1

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
2025-02-26T01:54Z
PATparcheada
sin registro aún
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

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:

==================================================================
BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac
Read of size 8 at addr ffff8881243384e0 by task mount/719

Call Trace:
 dump_stack+0x115/0x16b
 jffs2_clear_xattr_subsystem+0x95/0x6ac
 jffs2_do_fill_super+0x84f/0xc30
 jffs2_fill_super+0x2ea/0x4c0
 mtd_get_sb+0x254/0x400
 mtd_get_sb_by_nr+0x4f/0xd0
 get_tree_mtd+0x498/0x840
 jffs2_get_tree+0x25/0x30
 vfs_get_tree+0x8d/0x2e0
 path_mount+0x50f/0x1e50
 do_mount+0x107/0x130
 __se_sys_mount+0x1c5/0x2f0
 __x64_sys_mount+0xc7/0x160
 do_syscall_64+0x45/0x70
 entry_SYSCALL_64_after_hwframe+0x44/0xa9

Allocated by task 719:
 kasan_save_stack+0x23/0x60
 __kasan_kmalloc.constprop.0+0x10b/0x120
 kasan_slab_alloc+0x12/0x20
 kmem_cache_alloc+0x1c0/0x870
 jffs2_alloc_xattr_ref+0x2f/0xa0
 jffs2_scan_medium.cold+0x3713/0x4794
 jffs2_do_mount_fs.cold+0xa7/0x2253
 jffs2_do_fill_super+0x383/0xc30
 jffs2_fill_super+0x2ea/0x4c0
[...]

Freed by task 719:
 kmem_cache_free+0xcc/0x7b0
 jffs2_free_xattr_ref+0x78/0x98
 jffs2_clear_xattr_subsystem+0xa1/0x6ac
 jffs2_do_mount_fs.cold+0x5e6/0x2253
 jffs2_do_fill_super+0x383/0xc30
 jffs2_fill_super+0x2ea/0x4c0
[...]

The buggy address belongs to the object at ffff8881243384b8
 which belongs to the cache jffs2_xattr_ref of size 48
The buggy address is located 40 bytes inside of
 48-byte region [ffff8881243384b8, ffff8881243384e8)
[...]
==================================================================

The triggering of the BUG is shown in the following stack: ----------------------------------------------------------- jffs2_fill_super

jffs2_do_fill_super
  jffs2_do_mount_fs
    jffs2_build_filesystem
      jffs2_scan_medium
        jffs2_scan_eraseblock        <--- ERROR
      jffs2_clear_xattr_subsystem    <--- free
  jffs2_clear_xattr_subsystem        <--- free again

-----------------------------------------------------------

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 text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, scored by the CNA Linux.

Registro de eventos

+DISdivulgación

Linux publicó el registro CVE. CVSS 7.8, severidad alta.

fuente cvelist · nday , importación masiva · en bruto
{
  "id": 253422,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2021-47656",
  "occurred_at": "2025-02-26T01:54:20.069Z",
  "observed_at": "2026-11-13T05:37:31.591644Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-02-27T17:59:35.381270Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2025-02-26T01:54:20.069Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.