cbcvebase.
CVE-2024-47740
published 2024-10-21

CVE-2024-47740: In the Linux kernel, the following vulnerability has been resolved: f2fs: Require FMODE_WRITE for atomic write ioctls The F2FS ioctls for starting and…

PriorityP424medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.23%
14.3th percentile
In the Linux kernel, the following vulnerability has been resolved: f2fs: Require FMODE_WRITE for atomic write ioctls The F2FS ioctls for starting and committing atomic writes check for inode_owner_or_capable(), but this does not give LSMs like SELinux or Landlock an opportunity to deny the write access - if the caller's FSUID matches the inode's UID, inode_owner_or_capable() immediately returns true. There are scenarios where LSMs want to deny a process the ability to write particular files, even files that the FSUID of the process owns; but this can currently partially be bypassed using atomic write ioctls in two ways: - F2FS_IOC_START_ATOMIC_REPLACE + F2FS_IOC_COMMIT_ATOMIC_WRITE can truncate an inode to size 0 - F2FS_IOC_START_ATOMIC_WRITE + F2FS_IOC_ABORT_ATOMIC_WRITE can revert changes another process concurrently made to a file Fix it by requiring FMODE_WRITE for these operations, just like for F2FS_IOC_MOVE_RANGE. Since any legitimate caller should only be using these ioctls when intending to write into the file, that seems unlikely to break anything.

Affected

28 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.1.115-1 (bookworm)linux 6.1.115-1 (bookworm)
debianlinux-6.1< linux 6.1.115-1 (bookworm)linux 6.1.115-1 (bookworm)
linuxlinux
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 700f3a7c7fa5764c9f24bbf7c78e0b6e479fa653700f3a7c7fa5764c9f24bbf7c78e0b6e479fa653
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 4ce87674c3a6b4d3b3d45f85b584ab8618a3cece4ce87674c3a6b4d3b3d45f85b584ab8618a3cece
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 000bab8753ae29a259feb339b99ee759795a48ac000bab8753ae29a259feb339b99ee759795a48ac
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 88ff021e1fea2d9b40b2d5efd9013c89f7be04ac88ff021e1fea2d9b40b2d5efd9013c89f7be04ac
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 32f348ecc149e9ca70a1c424ae8fa9b6919d271332f348ecc149e9ca70a1c424ae8fa9b6919d2713
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 5e0de753bfe87768ebe6744d869caa92f35e57315e0de753bfe87768ebe6744d869caa92f35e5731
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < f3bfac2cabf5333506b263bc0c8497c95302f32df3bfac2cabf5333506b263bc0c8497c95302f32d
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 4583290898c13c2c2e5eb8773886d153c2c5121d4583290898c13c2c2e5eb8773886d153c2c5121d
linuxlinux>= 88b88a66797159949cec32eaab12b4968f6fae2d < 4f5a100f87f32cb65d4bb1ad282a08c92f6f591e4f5a100f87f32cb65d4bb1ad282a08c92f6f591e
linuxlinux_kernel>= 0 < 5.10.234-15.10.234-1
linuxlinux_kernel>= 0 < 6.1.115-16.1.115-1
linuxlinux_kernel>= 0 < 6.11.2-16.11.2-1
linuxlinux_kernel>= 0 < 6.11.2-16.11.2-1
linuxlinux_kernel>= 0 < 5.4.0-208.2285.4.0-208.228
linuxlinux_kernel>= 0 < 5.15.0-127.1375.15.0-127.137
linuxlinux_kernel>= 0 < 6.8.0-54.566.8.0-54.56
linuxlinux_kernel>= 0 < 6.11.0-18.186.11.0-18.18
linuxlinux_kernel>= 3.18 < 4.19.3234.19.323
linuxlinux_kernel>= 4.20 < 5.4.2855.4.285
linuxlinux_kernel>= 5.11 < 5.15.1685.15.168
linuxlinux_kernel>= 5.16 < 6.1.1136.1.113
linuxlinux_kernel>= 5.5 < 5.10.2275.10.227

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.