CVE-2026-45942 (GCVE-0-2026-45942)

Vulnerability from cvelistv5 – Published: 2026-05-27 12:17 – Updated: 2026-08-05 12:28
VLAI
Title
ext4: fix e4b bitmap inconsistency reports
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: fix e4b bitmap inconsistency reports A bitmap inconsistency issue was observed during stress tests under mixed huge-page workloads. Ext4 reported multiple e4b bitmap check failures like: ext4_mb_complex_scan_group:2508: group 350, 8179 free clusters as per group info. But got 8192 blocks Analysis and experimentation confirmed that the issue is caused by a race condition between page migration and bitmap modification. Although this timing window is extremely narrow, it is still hit in practice: folio_lock ext4_mb_load_buddy __migrate_folio check ref count folio_mc_copy __filemap_get_folio folio_try_get(folio) ...... mb_mark_used ext4_mb_unload_buddy __folio_migrate_mapping folio_ref_freeze folio_unlock The root cause of this issue is that the fast path of load_buddy only increments the folio's reference count, which is insufficient to prevent concurrent folio migration. We observed that the folio migration process acquires the folio lock. Therefore, we can determine whether to take the fast path in load_buddy by checking the lock status. If the folio is locked, we opt for the slow path (which acquires the lock) to close this concurrency window. Additionally, this change addresses the following issues: When the DOUBLE_CHECK macro is enabled to inspect bitmap-related issues, the following error may be triggered: corruption in group 324 at byte 784(6272): f in copy != ff on disk/prealloc Analysis reveals that this is a false positive. There is a specific race window where the bitmap and the group descriptor become momentarily inconsistent, leading to this error report: ext4_mb_load_buddy ext4_mb_load_buddy __filemap_get_folio(create|lock) folio_lock ext4_mb_init_cache folio_mark_uptodate __filemap_get_folio(no lock) ...... mb_mark_used mb_mark_used_double mb_cmp_bitmaps mb_set_bits(e4b->bd_bitmap) folio_unlock The original logic assumed that since mb_cmp_bitmaps is called when the bitmap is newly loaded from disk, the folio lock would be sufficient to prevent concurrent access. However, this overlooks a specific race condition: if another process attempts to load buddy and finds the folio is already in an uptodate state, it will immediately begin using it without holding folio lock.
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: c9de560ded61faa5b754137b7753da252391c55a , < 57e83bfbe1e412ac42daced2086f3c6f9a17bba0 (git)
Affected: c9de560ded61faa5b754137b7753da252391c55a , < c05033cfc5c7699cd4df8d48cef94d01da755f24 (git)
Affected: c9de560ded61faa5b754137b7753da252391c55a , < 29a07d691d282faf38c33d4b61839b89399110f9 (git)
Affected: c9de560ded61faa5b754137b7753da252391c55a , < f29709a7a3fc38f5015d850504762cdef0e151f9 (git)
Affected: c9de560ded61faa5b754137b7753da252391c55a , < bdc56a9c46b2a99c12313122b9352b619a2e719e (git)
Create a notification for this product.
Linux Linux Affected: 2.6.25
Unaffected: 0 , < 2.6.25 (semver)
Unaffected: 6.6.130 , ≤ 6.6.* (semver)
Unaffected: 6.12.75 , ≤ 6.12.* (semver)
Unaffected: 6.18.14 , ≤ 6.18.* (semver)
Unaffected: 6.19.4 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/mballoc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "57e83bfbe1e412ac42daced2086f3c6f9a17bba0",
              "status": "affected",
              "version": "c9de560ded61faa5b754137b7753da252391c55a",
              "versionType": "git"
            },
            {
              "lessThan": "c05033cfc5c7699cd4df8d48cef94d01da755f24",
              "status": "affected",
              "version": "c9de560ded61faa5b754137b7753da252391c55a",
              "versionType": "git"
            },
            {
              "lessThan": "29a07d691d282faf38c33d4b61839b89399110f9",
              "status": "affected",
              "version": "c9de560ded61faa5b754137b7753da252391c55a",
              "versionType": "git"
            },
            {
              "lessThan": "f29709a7a3fc38f5015d850504762cdef0e151f9",
              "status": "affected",
              "version": "c9de560ded61faa5b754137b7753da252391c55a",
              "versionType": "git"
            },
            {
              "lessThan": "bdc56a9c46b2a99c12313122b9352b619a2e719e",
              "status": "affected",
              "version": "c9de560ded61faa5b754137b7753da252391c55a",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/mballoc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.25"
            },
            {
              "lessThan": "2.6.25",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.130",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.75",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.14",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.130",
                  "versionStartIncluding": "2.6.25",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.75",
                  "versionStartIncluding": "2.6.25",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.14",
                  "versionStartIncluding": "2.6.25",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.4",
                  "versionStartIncluding": "2.6.25",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "2.6.25",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: fix e4b bitmap inconsistency reports\n\nA bitmap inconsistency issue was observed during stress tests under\nmixed huge-page workloads. Ext4 reported multiple e4b bitmap check\nfailures like:\n\next4_mb_complex_scan_group:2508: group 350, 8179 free clusters as\nper group info. But got 8192 blocks\n\nAnalysis and experimentation confirmed that the issue is caused by a\nrace condition between page migration and bitmap modification. Although\nthis timing window is extremely narrow, it is still hit in practice:\n\nfolio_lock                        ext4_mb_load_buddy\n__migrate_folio\n  check ref count\n  folio_mc_copy                     __filemap_get_folio\n                                      folio_try_get(folio)\n                                  ......\n                                  mb_mark_used\n                                  ext4_mb_unload_buddy\n  __folio_migrate_mapping\n    folio_ref_freeze\nfolio_unlock\n\nThe root cause of this issue is that the fast path of load_buddy only\nincrements the folio\u0027s reference count, which is insufficient to prevent\nconcurrent folio migration. We observed that the folio migration process\nacquires the folio lock. Therefore, we can determine whether to take the\nfast path in load_buddy by checking the lock status. If the folio is\nlocked, we opt for the slow path (which acquires the lock) to close this\nconcurrency window.\n\nAdditionally, this change addresses the following issues:\n\nWhen the DOUBLE_CHECK macro is enabled to inspect bitmap-related\nissues, the following error may be triggered:\n\ncorruption in group 324 at byte 784(6272): f in copy != ff on\ndisk/prealloc\n\nAnalysis reveals that this is a false positive. There is a specific race\nwindow where the bitmap and the group descriptor become momentarily\ninconsistent, leading to this error report:\n\next4_mb_load_buddy                   ext4_mb_load_buddy\n  __filemap_get_folio(create|lock)\n    folio_lock\n  ext4_mb_init_cache\n    folio_mark_uptodate\n                                     __filemap_get_folio(no lock)\n                                     ......\n                                     mb_mark_used\n                                       mb_mark_used_double\n  mb_cmp_bitmaps\n                                       mb_set_bits(e4b-\u003ebd_bitmap)\n  folio_unlock\n\nThe original logic assumed that since mb_cmp_bitmaps is called when the\nbitmap is newly loaded from disk, the folio lock would be sufficient to\nprevent concurrent access. However, this overlooks a specific race\ncondition: if another process attempts to load buddy and finds the folio\nis already in an uptodate state, it will immediately begin using it without\nholding folio lock."
        }
      ],
      "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 vulnerability is reached through local filesystem block-allocation activity combined with local folio migration (compaction/NUMA/huge-page reclaim), which is a kernel memory-management event an attacker induces locally; there is no remote path that controls the migration side of the race.\nAC:L - The attacker controls both sides of the race\u2014heavy block-allocation I/O plus memory pressure that forces folio migration\u2014and the commit confirms the window \"is still hit in practice\" under sustained workloads, so it is reliably reproducible by an attacker-constructed workload.\nPR:L - An ordinary unprivileged local user with write access to any ext4 filesystem (e.g., /tmp or /home) can drive block allocation and induce memory migration; no elevated capabilities are required.\nUI:N - The attacker performs all actions (file writes plus memory pressure) on an already-mounted filesystem with no action by any other user.\nS:U - The corruption is confined to the ext4 filesystem and kernel within the same security authority; no VM, sandbox, or IOMMU boundary is crossed.\nC:H - A lost bitmap update can cause block double-allocation, assigning the same physical block to two inodes so one user can read data written by another on a shared filesystem, constituting significant information disclosure.\nI:H - The race corrupts buddy-bitmap/group-descriptor consistency and can double-allocate blocks, leading to file-data corruption (one file\u0027s writes overwriting another\u0027s) and persistent on-disk metadata inconsistency.\nA:H - Detected inconsistency invokes ext4_grp_locked_error()/ext4_handle_error(), which aborts the journal and remounts the filesystem read-only (or panics the kernel with errors=panic), rendering the filesystem\u2014potentially the root filesystem\u2014unavailable."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:28:49.964Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/57e83bfbe1e412ac42daced2086f3c6f9a17bba0"
        },
        {
          "url": "https://git.kernel.org/stable/c/c05033cfc5c7699cd4df8d48cef94d01da755f24"
        },
        {
          "url": "https://git.kernel.org/stable/c/29a07d691d282faf38c33d4b61839b89399110f9"
        },
        {
          "url": "https://git.kernel.org/stable/c/f29709a7a3fc38f5015d850504762cdef0e151f9"
        },
        {
          "url": "https://git.kernel.org/stable/c/bdc56a9c46b2a99c12313122b9352b619a2e719e"
        }
      ],
      "title": "ext4: fix e4b bitmap inconsistency reports",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-45942",
    "datePublished": "2026-05-27T12:17:57.950Z",
    "dateReserved": "2026-05-13T15:03:33.087Z",
    "dateUpdated": "2026-08-05T12:28:49.964Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-45942",
      "date": "2026-08-05",
      "epss": "0.00099",
      "percentile": "0.00969"
    },
    "microsoft_vex": {
      "current_release_date": "2026-05-28T14:52:16.000Z",
      "cve": "CVE-2026-45942",
      "id": "msrc_CVE-2026-45942",
      "initial_release_date": "2026-05-02T00:00:00.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "ext4: fix e4b bitmap inconsistency reports",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-45942.json",
      "version": "2"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-45942\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-05-27T14:17:10.427\",\"lastModified\":\"2026-06-24T17:09:10.047\",\"vulnStatus\":\"Undergoing Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\next4: fix e4b bitmap inconsistency reports\\n\\nA bitmap inconsistency issue was observed during stress tests under\\nmixed huge-page workloads. Ext4 reported multiple e4b bitmap check\\nfailures like:\\n\\next4_mb_complex_scan_group:2508: group 350, 8179 free clusters as\\nper group info. But got 8192 blocks\\n\\nAnalysis and experimentation confirmed that the issue is caused by a\\nrace condition between page migration and bitmap modification. Although\\nthis timing window is extremely narrow, it is still hit in practice:\\n\\nfolio_lock                        ext4_mb_load_buddy\\n__migrate_folio\\n  check ref count\\n  folio_mc_copy                     __filemap_get_folio\\n                                      folio_try_get(folio)\\n                                  ......\\n                                  mb_mark_used\\n                                  ext4_mb_unload_buddy\\n  __folio_migrate_mapping\\n    folio_ref_freeze\\nfolio_unlock\\n\\nThe root cause of this issue is that the fast path of load_buddy only\\nincrements the folio\u0027s reference count, which is insufficient to prevent\\nconcurrent folio migration. We observed that the folio migration process\\nacquires the folio lock. Therefore, we can determine whether to take the\\nfast path in load_buddy by checking the lock status. If the folio is\\nlocked, we opt for the slow path (which acquires the lock) to close this\\nconcurrency window.\\n\\nAdditionally, this change addresses the following issues:\\n\\nWhen the DOUBLE_CHECK macro is enabled to inspect bitmap-related\\nissues, the following error may be triggered:\\n\\ncorruption in group 324 at byte 784(6272): f in copy != ff on\\ndisk/prealloc\\n\\nAnalysis reveals that this is a false positive. There is a specific race\\nwindow where the bitmap and the group descriptor become momentarily\\ninconsistent, leading to this error report:\\n\\next4_mb_load_buddy                   ext4_mb_load_buddy\\n  __filemap_get_folio(create|lock)\\n    folio_lock\\n  ext4_mb_init_cache\\n    folio_mark_uptodate\\n                                     __filemap_get_folio(no lock)\\n                                     ......\\n                                     mb_mark_used\\n                                       mb_mark_used_double\\n  mb_cmp_bitmaps\\n                                       mb_set_bits(e4b-\u003ebd_bitmap)\\n  folio_unlock\\n\\nThe original logic assumed that since mb_cmp_bitmaps is called when the\\nbitmap is newly loaded from disk, the folio lock would be sufficient to\\nprevent concurrent access. However, this overlooks a specific race\\ncondition: if another process attempts to load buddy and finds the folio\\nis already in an uptodate state, it will immediately begin using it without\\nholding folio lock.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"fs/ext4/mballoc.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"c9de560ded61faa5b754137b7753da252391c55a\",\"lessThan\":\"57e83bfbe1e412ac42daced2086f3c6f9a17bba0\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"c9de560ded61faa5b754137b7753da252391c55a\",\"lessThan\":\"c05033cfc5c7699cd4df8d48cef94d01da755f24\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"c9de560ded61faa5b754137b7753da252391c55a\",\"lessThan\":\"29a07d691d282faf38c33d4b61839b89399110f9\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"c9de560ded61faa5b754137b7753da252391c55a\",\"lessThan\":\"f29709a7a3fc38f5015d850504762cdef0e151f9\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"c9de560ded61faa5b754137b7753da252391c55a\",\"lessThan\":\"bdc56a9c46b2a99c12313122b9352b619a2e719e\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"fs/ext4/mballoc.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"2.6.25\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"2.6.25\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.130\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.75\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.18.14\",\"lessThanOrEqual\":\"6.18.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.19.4\",\"lessThanOrEqual\":\"6.19.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"7.0\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-362\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"2.6.25\",\"versionEndExcluding\":\"6.6.130\",\"matchCriteriaId\":\"F63C0224-D6A0-4E52-A75A-D9016CE6983E\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.12.75\",\"matchCriteriaId\":\"BCE16369-98ED-41CF-8995-DFDC10B288D2\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.13\",\"versionEndExcluding\":\"6.18.14\",\"matchCriteriaId\":\"BF463CB7-1F58-4607-B847-77ED23E4B9B7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.19\",\"versionEndExcluding\":\"6.19.4\",\"matchCriteriaId\":\"672A3E79-EC03-479D-8503-361DFBDC8092\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/29a07d691d282faf38c33d4b61839b89399110f9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/57e83bfbe1e412ac42daced2086f3c6f9a17bba0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/bdc56a9c46b2a99c12313122b9352b619a2e719e\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c05033cfc5c7699cd4df8d48cef94d01da755f24\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/f29709a7a3fc38f5015d850504762cdef0e151f9\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-05T14:51:04+00:00",
      "cve": "CVE-2026-45942",
      "id": "CVE-2026-45942",
      "initial_release_date": "2026-05-27T00:00:00+00:00",
      "product_status:known_affected": "274",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: ext4: fix e4b bitmap inconsistency reports",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45942.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-15T05:08:58Z",
      "cve": "CVE-2026-45942",
      "id": "CVE-2026-45942",
      "initial_release_date": "2026-05-28T03:55:44Z",
      "product_status:first_fixed": "2",
      "product_status:known_affected": "411",
      "product_status:known_not_affected": "276",
      "product_status:recommended": "145",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-45942",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-45942.json",
      "version": "5"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.