LSM write bypass via atomic-write ioctls
Published Oct 21, 2024 · Updated Aug 5, 2026
Improper access control in affected Linux kernels allows local users to alter owned F2FS files despite LSM write restrictions. The atomic-write ioctl handlers rely on inode_owner_or_capable(), which accepts a matching FSUID without asking SELinux or Landlock to authorize write access. A local process must own the target inode and reach an F2FS mount; it can truncate the file to zero bytes or revert another process's concurrent changes.
Summary
What happened
Improper access control in affected Linux kernels allows local users to alter owned F2FS files despite LSM write restrictions. The atomic-write ioctl handlers rely on inode_owner_or_capable(), which accepts a matching FSUID without asking SELinux or Landlock to authorize write access. A local process must own the target inode and reach an F2FS mount; it can truncate the file to zero bytes or revert another process's concurrent changes.
The record
- CVE
- CVE-2024-47740
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.18
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <000bab8753ae29a259feb339b99ee759795a48ac
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <32f348ecc149e9ca70a1c424ae8fa9b6919d2713
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <4583290898c13c2c2e5eb8773886d153c2c5121d
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <4ce87674c3a6b4d3b3d45f85b584ab8618a3cece
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <4f5a100f87f32cb65d4bb1ad282a08c92f6f591e
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <5e0de753bfe87768ebe6744d869caa92f35e5731
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <700f3a7c7fa5764c9f24bbf7c78e0b6e479fa653
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <88ff021e1fea2d9b40b2d5efd9013c89f7be04ac
- Affected versionversion=88b88a66797159949cec32eaab12b4968f6fae2d <f3bfac2cabf5333506b263bc0c8497c95302f32d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo