Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2023-53270— ext4: fix i_disksize exceeding i_size problem in paritally written case

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于i_disksize可能超过i_size,可能导致数据不一致问题。

AI Predicted 5.5 Difficulty: Hard EPSS 0.16% · P5

Possible ATT&CK Techniques 1 AI

T1068 · Exploitation for Privilege Escalation

Affected Version Matrix 12

VendorProduct Version RangeStatus
Linux Linux 64769240bd07f446f83660bb143bb609d8ab4910< 18eb23891aeae3229baf8c7c23b76be3364e1967 affected
64769240bd07f446f83660bb143bb609d8ab4910< d30090eb546d993ea3f3023452540c476ea614a5 affected
64769240bd07f446f83660bb143bb609d8ab4910< 3ecea2fee14227712694c8b54ad99d471e61de92 affected
64769240bd07f446f83660bb143bb609d8ab4910< 53877ed201baa6b58f7ce9df92664a839113c30e affected
64769240bd07f446f83660bb143bb609d8ab4910< 1dedde690303c05ef732b7c5c8356fdf60a4ade3 affected
2.6.27 affected
< 2.6.27 unaffected
5.15.111≤ 5.15.* unaffected
… +4 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2023-53270

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
ext4: fix i_disksize exceeding i_size problem in paritally written case
Source: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: ext4: fix i_disksize exceeding i_size problem in paritally written case It is possible for i_disksize can exceed i_size, triggering a warning. generic_perform_write copied = iov_iter_copy_from_user_atomic(len) // copied < len ext4_da_write_end | ext4_update_i_disksize | new_i_size = pos + copied; | WRITE_ONCE(EXT4_I(inode)->i_disksize, newsize) // update i_disksize | generic_write_end | copied = block_write_end(copied, len) // copied = 0 | if (unlikely(copied < len)) | if (!PageUptodate(page)) | copied = 0; | if (pos + copied > inode->i_size) // return false if (unlikely(copied == 0)) goto again; if (unlikely(iov_iter_fault_in_readable(i, bytes))) { status = -EFAULT; break; } We get i_disksize greater than i_size here, which could trigger WARNING check 'i_size_read(inode) < EXT4_I(inode)->i_disksize' while doing dio: ext4_dio_write_iter iomap_dio_rw __iomap_dio_rw // return err, length is not aligned to 512 ext4_handle_inode_extension WARN_ON_ONCE(i_size_read(inode) < EXT4_I(inode)->i_disksize) // Oops WARNING: CPU: 2 PID: 2609 at fs/ext4/file.c:319 CPU: 2 PID: 2609 Comm: aa Not tainted 6.3.0-rc2 RIP: 0010:ext4_file_write_iter+0xbc7 Call Trace: vfs_write+0x3b1 ksys_write+0x77 do_syscall_64+0x39 Fix it by updating 'copied' value before updating i_disksize just like ext4_write_inline_data_end() does. A reproducer can be found in the buganizer link below.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于i_disksize可能超过i_size,可能导致数据不一致问题。
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

Vendor Product Affected Versions CPE Subscribe
Linux Linux 64769240bd07f446f83660bb143bb609d8ab4910 ~ 18eb23891aeae3229baf8c7c23b76be3364e1967 -
Linux Linux 2.6.27 -

II. Public POCs for CVE-2023-53270

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2023-53270

请登录查看更多情报信息。

Same Patch Batch · Linux · 2025-09-16 · 115 CVEs total

CVE-2022-50350 9.8 CRITICAL scsi: target: iscsi: Fix a race condition between login_work and the login thread
CVE-2025-39806 8.8 HIGH HID: multitouch: fix slab out-of-bounds access in mt_report_fixup()
CVE-2023-53315 8.8 HIGH wifi: ath11k: Fix SKB corruption in REO destination ring
CVE-2023-53305 8.8 HIGH Bluetooth: L2CAP: Fix use-after-free
CVE-2025-39827 8.8 HIGH net: rose: include node references in rose_neigh refcount
CVE-2025-39826 8.8 HIGH net: rose: convert 'use' field to refcount_t
CVE-2023-53322 8.8 HIGH scsi: qla2xxx: Wait for io return on terminate rport
CVE-2023-53297 8.8 HIGH Bluetooth: L2CAP: fix "bad unlock balance" in l2cap_disconnect_rsp
CVE-2025-39809 8.4 HIGH HID: intel-thc-hid: intel-quicki2c: Fix ACPI dsd ICRS/ISUB length
CVE-2023-53333 8.2 HIGH netfilter: conntrack: dccp: copy entire header to stack buffer, not just basic one
CVE-2023-53314 7.8 HIGH fbdev/ep93xx-fb: Do not assign to struct fb_info.dev
CVE-2025-39818 7.8 HIGH HID: intel-thc-hid: intel-thc: Fix incorrect pointer arithmetic in I2C regs save
CVE-2025-39815 7.8 HIGH RISC-V: KVM: fix stack overrun when loading vlenb
CVE-2023-53286 7.8 HIGH RDMA/mlx5: Return the firmware result upon destroying QP/RQ
CVE-2023-53311 7.8 HIGH nilfs2: fix use-after-free of nilfs_root in dirtying inodes via iput
CVE-2022-50341 7.8 HIGH cifs: fix oops during encryption
CVE-2025-39825 7.8 HIGH smb: client: fix race with concurrent opens in rename(2)
CVE-2023-53274 7.8 HIGH clk: mediatek: mt8183: Add back SSPM related clocks
CVE-2025-39810 7.8 HIGH bnxt_en: Fix memory corruption when FW resources change during ifdown
CVE-2023-53331 7.8 HIGH pstore/ram: Check start of empty przs during init

Showing top 20 of 115 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2023-53270

No comments yet


Leave a comment