Skip to content
Heist/ feed
Back to feed
HighFix available

nilfs2: fix state management in error path of log writing function

Type: advisorySources: OSV

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix state management in error path of log writing function After commit a694291a6211 ("nilfs2: separate wait function from nilfs_segctor_write") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling. First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang. Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the "sc_dirty_files" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping. Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages a

Products
Kernel
Affected versions
Not specified
Fixed versions
4.19.322, 5.10.226, 5.15.167, 5.4.284, 6.1.110, 6.10.10, 6.6.51
CVEs
CVE-2024-47669
Confirmed fixed CVEs
Not specified
Updated in this feed
7 Nov 2026, 08:00 UTC · Revision 1

Source evidence

nilfs2: fix state management in error path of log writing function

core-osv · Original source

Published 9 Oct 2024, 14:14 UTC

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix state management in error path of log writing function After commit a694291a6211 ("nilfs2: separate wait function from nilfs_segctor_write") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling. First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang. Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the "sc_dirty_files" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping. Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages a

osv:CVE-2024-47669

Kernel

Fixed versions: 4.19.322, 5.4.284, 5.10.226, 5.15.167, 6.1.110, 6.6.51, 6.10.10

Complete source record
{
  "id": "9a977da4fbd3bfe3c669f7dbbc9c081a8743c28223fe9352816f430ce98545ba",
  "url": "https://osv.dev/vulnerability/CVE-2024-47669",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "nilfs2: fix state management in error path of log writing function",
    "summary": "In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix state management in error path of log writing function After commit a694291a6211 (\"nilfs2: separate wait function from nilfs_segctor_write\") was applied, the log writing function nilfs_segctor_do_construct() was able to issue I/O requests continuously even if user data blocks were split into multiple logs across segments, but two potential flaws were introduced in its error handling. First, if nilfs_segctor_begin_construction() fails while creating the second or subsequent logs, the log writing function returns without calling nilfs_segctor_abort_construction(), so the writeback flag set on pages/folios will remain uncleared. This causes page cache operations to hang waiting for the writeback flag. For example, truncate_inode_pages_final(), which is called via nilfs_evict_inode() when an inode is evicted from memory, will hang. Second, the NILFS_I_COLLECTED flag set on normal inodes remain uncleared. As a result, if the next log write involves checkpoint creation, that's fine, but if a partial log write is performed that does not, inodes with NILFS_I_COLLECTED set are erroneously removed from the \"sc_dirty_files\" list, and their data and b-tree blocks may not be written to the device, corrupting the block mapping. Fix these issues by uniformly calling nilfs_segctor_abort_construction() on failure of each step in the loop in nilfs_segctor_do_construct(), having it clean up logs and segment usages a",
    "evidence": "osv:CVE-2024-47669",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "4.19.322",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.4.284",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.10.226",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "5.15.167",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.1.110",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.51",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.10.10",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2024-47669",
      "aliases": [
        "CVE-2024-47669"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "a694291a6211537189c6080f77f63cdabfc9b63e"
                },
                {
                  "fixed": "40a2757de2c376ef8a08d9ee9c81e77f3c750adf"
                },
                {
                  "fixed": "036441e8438b29111fa75008f0ce305fb4e83c0a"
                },
                {
                  "fixed": "efdde00d4a1ef10bb71e09ebc67823a3d3ad725b"
                },
                {
                  "fixed": "3e349d7191f0688fc9808ef24fd4e4b4ef5ca876"
                },
                {
                  "fixed": "30562eff4a6dd35c4b5be9699ef61ad9f5f20a06"
                },
                {
                  "fixed": "0a1a961bde4351dc047ffdeb2f1311ca16a700cc"
                },
                {
                  "fixed": "74866c16ea2183f52925fa5d76061a1fe7f7737b"
                },
                {
                  "fixed": "6576dd6695f2afca3f4954029ac4a64f82ba60ab"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47669.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "2.6.33"
                },
                {
                  "fixed": "4.19.322"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "4.20.0"
                },
                {
                  "fixed": "5.4.284"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.5.0"
                },
                {
                  "fixed": "5.10.226"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.11.0"
                },
                {
                  "fixed": "5.15.167"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.16.0"
                },
                {
                  "fixed": "6.1.110"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.51"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.10.10"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-47669.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:50.372639501Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/036441e8438b29111fa75008f0ce305fb4e83c0a",
        "https://git.kernel.org/stable/c/0a1a961bde4351dc047ffdeb2f1311ca16a700cc",
        "https://git.kernel.org/stable/c/30562eff4a6dd35c4b5be9699ef61ad9f5f20a06",
        "https://git.kernel.org/stable/c/3e349d7191f0688fc9808ef24fd4e4b4ef5ca876",
        "https://git.kernel.org/stable/c/40a2757de2c376ef8a08d9ee9c81e77f3c750adf",
        "https://git.kernel.org/stable/c/6576dd6695f2afca3f4954029ac4a64f82ba60ab",
        "https://git.kernel.org/stable/c/74866c16ea2183f52925fa5d76061a1fe7f7737b",
        "https://git.kernel.org/stable/c/efdde00d4a1ef10bb71e09ebc67823a3d3ad725b",
        "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47669.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2024-47669",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/47xxx/CVE-2024-47669.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2024-47669",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 518690,
  "published_at": "2024-10-09T14:14:01.139+00:00"
}