jffs2: fix memory leak in jffs2_scan_medium

Description

In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_scan_medium If an error is returned in jffs2_scan_eraseblock() and some memory has been added to the jffs2_summary *s, we can observe the following kmemleak report: -------------------------------------------- unreferenced object 0xffff88812b889c40 (size 64): comm "mount", pid 692, jiffies 4294838325 (age 34.288s) hex dump (first 32 bytes): 40 48 b5 14 81 88 ff ff 01 e0 31 00 00 00 50 00 @H........1...P. 00 00 01 00 00 00 01 00 00 00 02 00 00 00 09 08 ................ backtrace: [<ffffffffae93a3a3>] __kmalloc+0x613/0x910 [<ffffffffaf423b9c>] jffs2_sum_add_dirent_mem+0x5c/0xa0 [<ffffffffb0f3afa8>] jffs2_scan_medium.cold+0x36e5/0x4794 [<ffffffffb0f3dbe1>] jffs2_do_mount_fs.cold+0xa7/0x2267 [<ffffffffaf40acf3>] jffs2_do_fill_super+0x383/0xc30 [<ffffffffaf40c00a>] jffs2_fill_super+0x2ea/0x4c0 [<ffffffffb0315d64>] mtd_get_sb+0x254/0x400 [<ffffffffb0315f5f>] mtd_get_sb_by_nr+0x4f/0xd0 [<ffffffffb0316478>] get_tree_mtd+0x498/0x840 [<ffffffffaf40bd15>] jffs2_get_tree+0x25/0x30 [<ffffffffae9f358d>] vfs_get_tree+0x8d/0x2e0 [<ffffffffaea7a98f>] path_mount+0x50f/0x1e50 [<ffffffffaea7c3d7>] do_mount+0x107/0x130 [<ffffffffaea7c5c5>] __se_sys_mount+0x1c5/0x2f0 [<ffffffffaea7c917>] __x64_sys_mount+0xc7/0x160 [<ffffffffb10142f5>] do_syscall_64+0x45/0x70 unreferenced object 0xffff888114b54840 (size 32): comm "mount", pid 692, jiffies 4294838325 (age 34.288s) hex dump (first 32 bytes): c0 75 b5 14 81 88 ff ff 02 e0 02 00 00 00 02 00 .u.............. 00 00 84 00 00 00 44 00 00 00 6b 6b 6b 6b 6b a5 ......D...kkkkk. backtrace: [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880 [<ffffffffaf423b04>] jffs2_sum_add_inode_mem+0x54/0x90 [<ffffffffb0f3bd44>] jffs2_scan_medium.cold+0x4481/0x4794 [...] unreferenced object 0xffff888114b57280 (size 32): comm "mount", pid 692, jiffies 4294838393 (age 34.357s) hex dump (first 32 bytes): 10 d5 6c 11 81 88 ff ff 08 e0 05 00 00 00 01 00 ..l............. 00 00 38 02 00 00 28 00 00 00 6b 6b 6b 6b 6b a5 ..8...(...kkkkk. backtrace: [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880 [<ffffffffaf423c34>] jffs2_sum_add_xattr_mem+0x54/0x90 [<ffffffffb0f3a24f>] jffs2_scan_medium.cold+0x298c/0x4794 [...] unreferenced object 0xffff8881116cd510 (size 16): comm "mount", pid 692, jiffies 4294838395 (age 34.355s) hex dump (first 16 bytes): 00 00 00 00 00 00 00 00 09 e0 60 02 00 00 6b a5 ..........`...k. backtrace: [<ffffffffae93be24>] kmem_cache_alloc_trace+0x584/0x880 [<ffffffffaf423cc4>] jffs2_sum_add_xref_mem+0x54/0x90 [<ffffffffb0f3b2e3>] jffs2_scan_medium.cold+0x3a20/0x4794 [...] -------------------------------------------- Therefore, we should call jffs2_sum_reset_collected(s) on exit to release the memory added in s. In addition, a new tag "out_buf" is added to prevent the NULL pointer reference caused by s being NULL. (thanks to Zhang Yi for this analysis)

Timeline

Scores

EPSS (exploitation in 30 days)

0.27% · top 81% of all CVEs (7 Nov 2026)

CISA SSVC

Exploitation: none · Automatable: no · Technical impact: partial

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

• CWE-401 Missing Release of Memory after Effective Lifetime (opens in a new tab)All about CWE-401 and its CVEs

Affected products

• Linux · Linux

  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 9b0c69182f09b70779817af4dcf89780955d5c4c
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < b36bccb04e14cc0c1e2d0e92d477fe220314fad6
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < e711913463af916d777a4873068f415f1fe2ad33
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 455f4a23490bfcbedc8e5c245c463a59b19e5ddd
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 51dbb5e36d59f62e34d462b801c1068248149cfe
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 52ba0ab4f0a606f02a6163493378989faa1ec10a
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < b26bbc0c122cad038831f226a4cb4de702225e16
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 82462324bf35b6b553400af1c1aa265069cee28f
  • affected e631ddba588783edd521c5a89f7b2902772fb691 – < 9cdd3128874f5fe759e2c4e1360ab7fb96a8d1df

• Linux · Linux

  • affected 2.6.15
  • unaffected < 2.6.15
  • unaffected 4.9.311 – ≤ 4.9.*
  • unaffected 4.14.276 – ≤ 4.14.*
  • unaffected 4.19.238 – ≤ 4.19.*
  • unaffected 5.4.189 – ≤ 5.4.*
  • unaffected 5.10.110 – ≤ 5.10.*
  • unaffected 5.15.33 – ≤ 5.15.*
  • unaffected 5.16.19 – ≤ 5.16.*
  • unaffected 5.17.2 – ≤ 5.17.*
  • unaffected 5.18 – ≤ *

References (9)

• https://git.kernel.org/stable/c/9b0c69182f09b70779817af4dcf89780955d5c4c (opens in a new tab)
• https://git.kernel.org/stable/c/b36bccb04e14cc0c1e2d0e92d477fe220314fad6 (opens in a new tab)
• https://git.kernel.org/stable/c/e711913463af916d777a4873068f415f1fe2ad33 (opens in a new tab)
• https://git.kernel.org/stable/c/455f4a23490bfcbedc8e5c245c463a59b19e5ddd (opens in a new tab)
• https://git.kernel.org/stable/c/51dbb5e36d59f62e34d462b801c1068248149cfe (opens in a new tab)
• https://git.kernel.org/stable/c/52ba0ab4f0a606f02a6163493378989faa1ec10a (opens in a new tab)
• https://git.kernel.org/stable/c/b26bbc0c122cad038831f226a4cb4de702225e16 (opens in a new tab)
• https://git.kernel.org/stable/c/82462324bf35b6b553400af1c1aa265069cee28f (opens in a new tab)
• https://git.kernel.org/stable/c/9cdd3128874f5fe759e2c4e1360ab7fb96a8d1df (opens in a new tab)

Sources

The same CVE in the primary databases and aggregators, to check against.

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2022-49276](https://trackcve.app/badge/CVE-2022-49276.svg)](https://trackcve.app/cve/CVE-2022-49276)

Record last updated 11 May 2026, 18:56 UTC.