Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-47740

f2fs: Require FMODE_WRITE for atomic write ioctls

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47740, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 700f3a7c7fa5764c9f24bbf7c78e0b6e479fa653
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 4ce87674c3a6b4d3b3d45f85b584ab8618a3cece
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 000bab8753ae29a259feb339b99ee759795a48ac
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 88ff021e1fea2d9b40b2d5efd9013c89f7be04ac
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 32f348ecc149e9ca70a1c424ae8fa9b6919d2713
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 5e0de753bfe87768ebe6744d869caa92f35e5731
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < f3bfac2cabf5333506b263bc0c8497c95302f32d
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 4583290898c13c2c2e5eb8773886d153c2c5121d
    • affected 88b88a66797159949cec32eaab12b4968f6fae2d – < 4f5a100f87f32cb65d4bb1ad282a08c92f6f591e
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 4.19.323 – ≤ 4.19.*
    • unaffected 5.4.285 – ≤ 5.4.*
    • unaffected 5.10.227 – ≤ 5.10.*
    • unaffected 5.15.168 – ≤ 5.15.*
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References11

Sources

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

Badge for a README or a ticket

CVE-2024-47740 badge
[![CVE-2024-47740](https://cveledger.app/badge/CVE-2024-47740.svg)](https://cveledger.app/cve/CVE-2024-47740)

Record last updated .