CVE-2024-38599— jffs2: prevent xattr node from overflowing the eraseblock
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2024-38599
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
jffs2: prevent xattr node from overflowing the eraseblock
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: jffs2: prevent xattr node from overflowing the eraseblock Add a check to make sure that the requested xattr node size is no larger than the eraseblock minus the cleanmarker. Unlike the usual inode nodes, the xattr nodes aren't split into parts and spread across multiple eraseblocks, which means that a xattr node must not occupy more than one eraseblock. If the requested xattr value is too large, the xattr node can spill onto the next eraseblock, overwriting the nodes and causing errors such as: jffs2: argh. node added in wrong place at 0x0000b050(2) jffs2: nextblock 0x0000a000, expected at 0000b00c jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050, read=0xfc892c93, calc=0x000000 jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed at 0x01e00c. {848f,2fc4,0fef511f,59a3d171} jffs2: Node at 0x0000000c with length 0x00001044 would run over the end of the erase block jffs2: Perhaps the file system was created with the wrong erase size? jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x1044 instead This breaks the filesystem and can lead to KASAN crashes such as: BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0 Read of size 4 at addr ffff88802c31e914 by task repro/830 CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0xc6/0x120 print_report+0xc4/0x620 ? __virt_addr_valid+0x308/0x5b0 kasan_report+0xc1/0xf0 ? jffs2_sum_add_kvec+0x125e/0x15d0 ? jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_flash_direct_writev+0xa8/0xd0 jffs2_flash_writev+0x9c9/0xef0 ? __x64_sys_setxattr+0xc4/0x160 ? do_syscall_64+0x69/0x140 ? entry_SYSCALL_64_after_hwframe+0x76/0x7e [...] Found by Linux Verification Center (linuxtesting.org) with Syzkaller.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞。攻击者利用该漏洞破坏文件系统并导致 KASAN 崩溃。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
II. Public POCs for CVE-2024-38599
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2024-38599
请登录查看更多情报信息。
Same Patch Batch · Linux · 2024-06-19 · 122 CVEs total
| CVE-2024-38611 | media: i2c: et8ek8: Don't strip remove function when driver is builtin | |
| CVE-2021-47585 | btrfs: fix memory leak in __add_inode_ref() | |
| CVE-2021-47584 | iocost: Fix divide-by-zero on donation from low hweight cgroup | |
| CVE-2021-47582 | USB: core: Make do_proc_control() and do_proc_bulk() killable | |
| CVE-2021-47583 | media: mxl111sf: change mutex_init() location | |
| CVE-2021-47579 | ovl: fix warning in ovl_create_real() | |
| CVE-2021-47580 | scsi: scsi_debug: Fix type in min_t to avoid stack OOB | |
| CVE-2021-47578 | scsi: scsi_debug: Don't call kcalloc() if size arg is zero | |
| CVE-2021-47576 | scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select() | |
| CVE-2021-47577 | io-wq: check for wq exit after adding new worker task_work | |
| CVE-2024-38617 | kunit/fortify: Fix mismatched kvalloc()/vfree() usage | |
| CVE-2024-38618 | ALSA: timer: Set lower bound of start tick time | |
| CVE-2024-38616 | wifi: carl9170: re-fix fortified-memset warning | |
| CVE-2024-38615 | cpufreq: exit() callback is optional | |
| CVE-2024-38614 | openrisc: traps: Don't send signals to kernel mode threads | |
| CVE-2024-38613 | m68k: Fix spinlock race in kernel thread creation | |
| CVE-2024-38602 | ax25: Fix reference count leak issues of ax25_dev | |
| CVE-2024-38603 | drivers/perf: hisi: hns3: Actually use devm_add_action_or_reset() | |
| CVE-2024-38601 | ring-buffer: Fix a race between readers and resize checks | |
| CVE-2024-38604 | block: refine the EOF check in blkdev_iomap_begin |
Showing top 20 of 122 CVEs. View all on vendor page → →
IV. Related Vulnerabilities
Same product: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
Same vendor: Linux
- CVE-2026-43500
rxrpc: Also unshare DATA/RESPONSE packets when paged frags a - CVE-2026-43475
scsi: storvsc: Fix scheduling while atomic on PREEMPT_RT - CVE-2026-43474
fs: init flags_valid before calling vfs_fileattr_get - CVE-2026-43473
scsi: mpi3mr: Add NULL checks when resetting request and rep - CVE-2026-43472
unshare: fix unshare_fs() handling
V. Comments for CVE-2024-38599
No comments yet