CVE-2024-56692 (GCVE-0-2024-56692)
Vulnerability from cvelistv5
Published
2024-12-28 09:46
Modified
2026-08-05 11:46
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on node blkaddr in truncate_node() syzbot reports a f2fs bug as below: ------------[ cut here ]------------ kernel BUG at fs/f2fs/segment.c:2534! RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 Call Trace: truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909 f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288 f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856 evict+0x4e8/0x9b0 fs/inode.c:723 f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986 f2fs_create+0x357/0x530 fs/f2fs/namei.c:394 lookup_open fs/namei.c:3595 [inline] open_last_lookups fs/namei.c:3694 [inline] path_openat+0x1c03/0x3590 fs/namei.c:3930 do_filp_open+0x235/0x490 fs/namei.c:3960 do_sys_openat2+0x13e/0x1d0 fs/open.c:1415 do_sys_open fs/open.c:1430 [inline] __do_sys_openat fs/open.c:1446 [inline] __se_sys_openat fs/open.c:1441 [inline] __x64_sys_openat+0x247/0x2a0 fs/open.c:1441 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534 The root cause is: on a fuzzed image, blkaddr in nat entry may be corrupted, then it will cause system panic when using it in f2fs_invalidate_blocks(), to avoid this, let's add sanity check on nat blkaddr in truncate_node().
References
Impacted products
Vendor Product Version
Linux Linux Version: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4
Version: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4
Version: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4
Version: 98e4da8ca301e062d79ae168c67e56f3c3de3ce4
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-56692",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T19:59:11.953057Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-754",
                "description": "CWE-754 Improper Check for Unusual or Exceptional Conditions",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:07:08.292Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/node.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "27d6e7eff07f8cce8e83b162d8f21a07458c860d",
              "status": "affected",
              "version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
              "versionType": "git"
            },
            {
              "lessThan": "c1077078ce4589b5e5387f6b0aaa0d4534b9eb57",
              "status": "affected",
              "version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
              "versionType": "git"
            },
            {
              "lessThan": "0a5c8b3fbf6200f1c66062d307c9a52084917788",
              "status": "affected",
              "version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
              "versionType": "git"
            },
            {
              "lessThan": "6babe00ccd34fc65b78ef8b99754e32b4385f23d",
              "status": "affected",
              "version": "98e4da8ca301e062d79ae168c67e56f3c3de3ce4",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/f2fs/node.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "3.8"
            },
            {
              "lessThan": "3.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.64",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.11",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.2",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "3.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to do sanity check on node blkaddr in truncate_node()\n\nsyzbot reports a f2fs bug as below:\n\n------------[ cut here ]------------\nkernel BUG at fs/f2fs/segment.c:2534!\nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534\nCall Trace:\n truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909\n f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288\n f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856\n evict+0x4e8/0x9b0 fs/inode.c:723\n f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986\n f2fs_create+0x357/0x530 fs/f2fs/namei.c:394\n lookup_open fs/namei.c:3595 [inline]\n open_last_lookups fs/namei.c:3694 [inline]\n path_openat+0x1c03/0x3590 fs/namei.c:3930\n do_filp_open+0x235/0x490 fs/namei.c:3960\n do_sys_openat2+0x13e/0x1d0 fs/open.c:1415\n do_sys_open fs/open.c:1430 [inline]\n __do_sys_openat fs/open.c:1446 [inline]\n __se_sys_openat fs/open.c:1441 [inline]\n __x64_sys_openat+0x247/0x2a0 fs/open.c:1441\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534\n\nThe root cause is: on a fuzzed image, blkaddr in nat entry may be\ncorrupted, then it will cause system panic when using it in\nf2fs_invalidate_blocks(), to avoid this, let\u0027s add sanity check on\nnat blkaddr in truncate_node()."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The attack requires a crafted f2fs image to be mounted on the local system and is then triggered through ordinary local filesystem syscalls (`openat`, `unlink`, `truncate`) reaching `truncate_node()`; no network protocol is involved.\nAC:L - The corrupted `block_addr` is a static, fully attacker-chosen field in the on-disk NAT journal that `remove_nats_in_journal()` copies into the NAT cache verbatim, so `truncate_node()` picks it up deterministically on every node truncation \u2014 no race, no timing window, and no dependence on memory layout the attacker cannot influence.\nPR:L - Once the malicious volume is mounted \u2014 automatically by udisks2 on desktops/kiosks or by vold for Android SD-card/adoptable storage, since f2fs is Android\u0027s primary filesystem \u2014 any unprivileged user with access to the mount triggers the path with a plain file create, unlink, or truncate; no capability check stands between that user and `truncate_node()`.\nUI:N - The attacker performs both halves of the attack: the volume is mounted automatically on media insertion by the automounter, and the trigger is the attacker\u0027s own ordinary file operation, requiring no action by any victim.\nS:U - The out-of-bounds accesses and the resulting corruption are confined to kernel memory of the same machine; no VM, IOMMU, or other security-authority boundary is crossed.\nC:H - `get_seg_entry()` indexes `sit_i-\u003esentries[]` with an unbounded `segno` derived from the attacker\u0027s 32-bit blkaddr and performs no bounds check, so `update_segment_mtime()`/`update_sit_entry()` read `struct seg_entry` fields \u2014 including the `cur_valid_map`/`ckpt_valid_map`/`discard_map` pointers \u2014 from arbitrary kernel memory far outside the array.\nI:H - The same unbounded index produces out-of-bounds writes to `se-\u003emtime`, `se-\u003evalid_blocks`, the `dirty_sentries_bitmap` bit set by `__mark_sit_entry_dirty()`, and `get_sec_entry()-\u003evalid_blocks`, plus a bit-clear performed through `se-\u003ecur_valid_map` \u2014 a pointer that was itself read out of bounds \u2014 giving a wild-pointer write primitive suitable for control-flow hijacking.\nA:H - The reported symptom is an outright kernel panic at `f2fs_bug_on(sbi, addr == NULL_ADDR)` in `f2fs_invalidate_blocks()` (`BUG_ON` under `CONFIG_F2FS_CHECK_FS`, `WARN_ON` elsewhere, fatal with `panic_on_warn`), and the out-of-bounds pointer dereferences oops the kernel independently."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:46:06.025Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/27d6e7eff07f8cce8e83b162d8f21a07458c860d"
        },
        {
          "url": "https://git.kernel.org/stable/c/c1077078ce4589b5e5387f6b0aaa0d4534b9eb57"
        },
        {
          "url": "https://git.kernel.org/stable/c/0a5c8b3fbf6200f1c66062d307c9a52084917788"
        },
        {
          "url": "https://git.kernel.org/stable/c/6babe00ccd34fc65b78ef8b99754e32b4385f23d"
        }
      ],
      "title": "f2fs: fix to do sanity check on node blkaddr in truncate_node()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-56692",
    "datePublished": "2024-12-28T09:46:17.539Z",
    "dateReserved": "2024-12-27T15:00:39.849Z",
    "dateUpdated": "2026-08-05T11:46:06.025Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-56692\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T19:59:11.953057Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-754\", \"description\": \"CWE-754 Improper Check for Unusual or Exceptional Conditions\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:46:42.625Z\"}}], \"cna\": {\"title\": \"f2fs: fix to do sanity check on node blkaddr in truncate_node()\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.8, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The attack requires a crafted f2fs image to be mounted on the local system and is then triggered through ordinary local filesystem syscalls (`openat`, `unlink`, `truncate`) reaching `truncate_node()`; no network protocol is involved.\\nAC:L - The corrupted `block_addr` is a static, fully attacker-chosen field in the on-disk NAT journal that `remove_nats_in_journal()` copies into the NAT cache verbatim, so `truncate_node()` picks it up deterministically on every node truncation \\u2014 no race, no timing window, and no dependence on memory layout the attacker cannot influence.\\nPR:L - Once the malicious volume is mounted \\u2014 automatically by udisks2 on desktops/kiosks or by vold for Android SD-card/adoptable storage, since f2fs is Android\u0027s primary filesystem \\u2014 any unprivileged user with access to the mount triggers the path with a plain file create, unlink, or truncate; no capability check stands between that user and `truncate_node()`.\\nUI:N - The attacker performs both halves of the attack: the volume is mounted automatically on media insertion by the automounter, and the trigger is the attacker\u0027s own ordinary file operation, requiring no action by any victim.\\nS:U - The out-of-bounds accesses and the resulting corruption are confined to kernel memory of the same machine; no VM, IOMMU, or other security-authority boundary is crossed.\\nC:H - `get_seg_entry()` indexes `sit_i-\u003esentries[]` with an unbounded `segno` derived from the attacker\u0027s 32-bit blkaddr and performs no bounds check, so `update_segment_mtime()`/`update_sit_entry()` read `struct seg_entry` fields \\u2014 including the `cur_valid_map`/`ckpt_valid_map`/`discard_map` pointers \\u2014 from arbitrary kernel memory far outside the array.\\nI:H - The same unbounded index produces out-of-bounds writes to `se-\u003emtime`, `se-\u003evalid_blocks`, the `dirty_sentries_bitmap` bit set by `__mark_sit_entry_dirty()`, and `get_sec_entry()-\u003evalid_blocks`, plus a bit-clear performed through `se-\u003ecur_valid_map` \\u2014 a pointer that was itself read out of bounds \\u2014 giving a wild-pointer write primitive suitable for control-flow hijacking.\\nA:H - The reported symptom is an outright kernel panic at `f2fs_bug_on(sbi, addr == NULL_ADDR)` in `f2fs_invalidate_blocks()` (`BUG_ON` under `CONFIG_F2FS_CHECK_FS`, `WARN_ON` elsewhere, fatal with `panic_on_warn`), and the out-of-bounds pointer dereferences oops the kernel independently.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"98e4da8ca301e062d79ae168c67e56f3c3de3ce4\", \"lessThan\": \"27d6e7eff07f8cce8e83b162d8f21a07458c860d\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"98e4da8ca301e062d79ae168c67e56f3c3de3ce4\", \"lessThan\": \"c1077078ce4589b5e5387f6b0aaa0d4534b9eb57\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"98e4da8ca301e062d79ae168c67e56f3c3de3ce4\", \"lessThan\": \"0a5c8b3fbf6200f1c66062d307c9a52084917788\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"98e4da8ca301e062d79ae168c67e56f3c3de3ce4\", \"lessThan\": \"6babe00ccd34fc65b78ef8b99754e32b4385f23d\", \"versionType\": \"git\"}], \"programFiles\": [\"fs/f2fs/node.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"3.8\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"3.8\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.6.64\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.11\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12.2\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.12.*\"}, {\"status\": \"unaffected\", \"version\": \"6.13\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"fs/f2fs/node.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/27d6e7eff07f8cce8e83b162d8f21a07458c860d\"}, {\"url\": \"https://git.kernel.org/stable/c/c1077078ce4589b5e5387f6b0aaa0d4534b9eb57\"}, {\"url\": \"https://git.kernel.org/stable/c/0a5c8b3fbf6200f1c66062d307c9a52084917788\"}, {\"url\": \"https://git.kernel.org/stable/c/6babe00ccd34fc65b78ef8b99754e32b4385f23d\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nf2fs: fix to do sanity check on node blkaddr in truncate_node()\\n\\nsyzbot reports a f2fs bug as below:\\n\\n------------[ cut here ]------------\\nkernel BUG at fs/f2fs/segment.c:2534!\\nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534\\nCall Trace:\\n truncate_node+0x1ae/0x8c0 fs/f2fs/node.c:909\\n f2fs_remove_inode_page+0x5c2/0x870 fs/f2fs/node.c:1288\\n f2fs_evict_inode+0x879/0x15c0 fs/f2fs/inode.c:856\\n evict+0x4e8/0x9b0 fs/inode.c:723\\n f2fs_handle_failed_inode+0x271/0x2e0 fs/f2fs/inode.c:986\\n f2fs_create+0x357/0x530 fs/f2fs/namei.c:394\\n lookup_open fs/namei.c:3595 [inline]\\n open_last_lookups fs/namei.c:3694 [inline]\\n path_openat+0x1c03/0x3590 fs/namei.c:3930\\n do_filp_open+0x235/0x490 fs/namei.c:3960\\n do_sys_openat2+0x13e/0x1d0 fs/open.c:1415\\n do_sys_open fs/open.c:1430 [inline]\\n __do_sys_openat fs/open.c:1446 [inline]\\n __se_sys_openat fs/open.c:1441 [inline]\\n __x64_sys_openat+0x247/0x2a0 fs/open.c:1441\\n do_syscall_x64 arch/x86/entry/common.c:52 [inline]\\n do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83\\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\\nRIP: 0010:f2fs_invalidate_blocks+0x35f/0x370 fs/f2fs/segment.c:2534\\n\\nThe root cause is: on a fuzzed image, blkaddr in nat entry may be\\ncorrupted, then it will cause system panic when using it in\\nf2fs_invalidate_blocks(), to avoid this, let\u0027s add sanity check on\\nnat blkaddr in truncate_node().\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.64\", \"versionStartIncluding\": \"3.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.11\", \"versionStartIncluding\": \"3.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12.2\", \"versionStartIncluding\": \"3.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.13\", \"versionStartIncluding\": \"3.8\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:46:06.025Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-56692\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:46:06.025Z\", \"dateReserved\": \"2024-12-27T15:00:39.849Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-12-28T09:46:17.539Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.