CVE-2024-27435 (GCVE-0-2024-27435)
Vulnerability from cvelistv5
Published
2024-05-17 12:12
Modified
2026-08-05 11:29
Severity ?
7.5 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme: fix reconnection fail due to reserved tag allocation We found a issue on production environment while using NVMe over RDMA, admin_q reconnect failed forever while remote target and network is ok. After dig into it, we found it may caused by a ABBA deadlock due to tag allocation. In my case, the tag was hold by a keep alive request waiting inside admin_q, as we quiesced admin_q while reset ctrl, so the request maked as idle and will not process before reset success. As fabric_q shares tagset with admin_q, while reconnect remote target, we need a tag for connect command, but the only one reserved tag was held by keep alive command which waiting inside admin_q. As a result, we failed to reconnect admin_q forever. In order to fix this issue, I think we should keep two reserved tags for admin queue.
References
Impacted products
Vendor Product Version
Linux Linux Version: ed01fee283a067c72b2d6500046080dbc1bb9dae
Version: ed01fee283a067c72b2d6500046080dbc1bb9dae
Version: ed01fee283a067c72b2d6500046080dbc1bb9dae
Version: ed01fee283a067c72b2d6500046080dbc1bb9dae
Version: ed01fee283a067c72b2d6500046080dbc1bb9dae
 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-27435",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-31T18:39:12.435774Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "description": "CWE-noinfo Not enough information",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-11-06T16:36:56.843Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T00:34:52.327Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/ff2f90f88d78559802466ad1c84ac5bda4416b3a"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/6851778504cdb49431809b4ba061903d5f592c96"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/262da920896e2f2ab0e3947d9dbee0aa09045818"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/de105068fead55ed5c07ade75e9c8e7f86a00d1d"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/core.c",
            "drivers/nvme/host/fabrics.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8",
              "status": "affected",
              "version": "ed01fee283a067c72b2d6500046080dbc1bb9dae",
              "versionType": "git"
            },
            {
              "lessThan": "ff2f90f88d78559802466ad1c84ac5bda4416b3a",
              "status": "affected",
              "version": "ed01fee283a067c72b2d6500046080dbc1bb9dae",
              "versionType": "git"
            },
            {
              "lessThan": "6851778504cdb49431809b4ba061903d5f592c96",
              "status": "affected",
              "version": "ed01fee283a067c72b2d6500046080dbc1bb9dae",
              "versionType": "git"
            },
            {
              "lessThan": "262da920896e2f2ab0e3947d9dbee0aa09045818",
              "status": "affected",
              "version": "ed01fee283a067c72b2d6500046080dbc1bb9dae",
              "versionType": "git"
            },
            {
              "lessThan": "de105068fead55ed5c07ade75e9c8e7f86a00d1d",
              "status": "affected",
              "version": "ed01fee283a067c72b2d6500046080dbc1bb9dae",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/nvme/host/core.c",
            "drivers/nvme/host/fabrics.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.12"
            },
            {
              "lessThan": "5.12",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.83",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.23",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.7.*",
              "status": "unaffected",
              "version": "6.7.11",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.8.*",
              "status": "unaffected",
              "version": "6.8.2",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.9",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.83",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.23",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.7.11",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.8.2",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.9",
                  "versionStartIncluding": "5.12",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix reconnection fail due to reserved tag allocation\n\nWe found a issue on production environment while using NVMe over RDMA,\nadmin_q reconnect failed forever while remote target and network is ok.\nAfter dig into it, we found it may caused by a ABBA deadlock due to tag\nallocation. In my case, the tag was hold by a keep alive request\nwaiting inside admin_q, as we quiesced admin_q while reset ctrl, so the\nrequest maked as idle and will not process before reset success. As\nfabric_q shares tagset with admin_q, while reconnect remote target, we\nneed a tag for connect command, but the only one reserved tag was held\nby keep alive command which waiting inside admin_q. As a result, we\nfailed to reconnect admin_q forever. In order to fix this issue, I\nthink we should keep two reserved tags for admin queue."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The affected code is the NVMe-over-Fabrics host driver (nvme-tcp/nvme-rdma/nvme-fc), and the controller reset that opens the race window is triggered directly from remote peer input \u2014 `nvme_tcp_state_change()` fires error recovery on a peer FIN/RST, and the receive path calls `nvme_tcp_error_recovery()` on any malformed PDU. A remote or on-path attacker against the NVMe/TCP connection (port 4420) can drive the vulnerable path without local access.\nAC:L - The attacker controls the reset side of the race and can force error recovery/reconnect cycles arbitrarily many times (reconnect re-arms the keep-alive timer each round), while the keep-alive period is deterministic at kato/2, so the window can be hit by retry and by timing; the bug was also observed occurring spontaneously in production. Once won, the leaked reserved tag is permanent \u2014 no further conditions are needed.\nPR:N - No credentials on the victim host are required \u2014 the triggering events (TCP FIN/RST, malformed NVMe/TCP PDU, unresponsive target) are handled by `nvme_tcp_state_change()` and the recv path before or independent of any NVMe-level authentication, and NVMe/TCP deployments commonly run with no DH-HMAC-CHAP or TLS at all.\nUI:N - Exploitation requires no action from any user or administrator; an already-established NVMe-oF connection is a system configuration precondition, not victim interaction, and the keep-alive/reset machinery runs autonomously in kernel workqueues.\nS:U - The impact is confined to the kernel and the host\u0027s own storage stack \u2014 no security authority boundary such as a VM, IOMMU, or sandbox is crossed.\nC:N - The defect is a reserved-tag leak causing an ABBA allocation deadlock; no memory is read out of bounds, no freed object is accessed, and no kernel data is disclosed to the attacker.\nI:N - There is no memory corruption, out-of-bounds write, or control-flow primitive \u2014 the only consequence is that a blk-mq tag is never returned, so no attacker-influenced data modification is possible.\nA:H - The admin queue can never reconnect (\"failed to reconnect admin_q forever\"), because the admin tagset is not reallocated on reconnect and the connect command\u0027s reserved tag allocation fails with -EAGAIN indefinitely, producing a permanent loss of the NVMe-oF storage path plus eventual controller deletion (and a hung, unkillable teardown worker blocked on queue freeze) \u2014 total availability loss for storage that is frequently the system\u0027s root or primary data volume."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:29:48.601Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8"
        },
        {
          "url": "https://git.kernel.org/stable/c/ff2f90f88d78559802466ad1c84ac5bda4416b3a"
        },
        {
          "url": "https://git.kernel.org/stable/c/6851778504cdb49431809b4ba061903d5f592c96"
        },
        {
          "url": "https://git.kernel.org/stable/c/262da920896e2f2ab0e3947d9dbee0aa09045818"
        },
        {
          "url": "https://git.kernel.org/stable/c/de105068fead55ed5c07ade75e9c8e7f86a00d1d"
        }
      ],
      "title": "nvme: fix reconnection fail due to reserved tag allocation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-27435",
    "datePublished": "2024-05-17T12:12:36.439Z",
    "dateReserved": "2024-02-25T13:47:42.687Z",
    "dateUpdated": "2026-08-05T11:29:48.601Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/ff2f90f88d78559802466ad1c84ac5bda4416b3a\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/6851778504cdb49431809b4ba061903d5f592c96\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/262da920896e2f2ab0e3947d9dbee0aa09045818\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/de105068fead55ed5c07ade75e9c8e7f86a00d1d\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T00:34:52.327Z\"}}, {\"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-27435\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-31T18:39:12.435774Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"description\": \"CWE-noinfo Not enough information\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-31T18:39:16.216Z\"}}], \"cna\": {\"title\": \"nvme: fix reconnection fail due to reserved tag allocation\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 7.5, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:N - The affected code is the NVMe-over-Fabrics host driver (nvme-tcp/nvme-rdma/nvme-fc), and the controller reset that opens the race window is triggered directly from remote peer input \\u2014 `nvme_tcp_state_change()` fires error recovery on a peer FIN/RST, and the receive path calls `nvme_tcp_error_recovery()` on any malformed PDU. A remote or on-path attacker against the NVMe/TCP connection (port 4420) can drive the vulnerable path without local access.\\nAC:L - The attacker controls the reset side of the race and can force error recovery/reconnect cycles arbitrarily many times (reconnect re-arms the keep-alive timer each round), while the keep-alive period is deterministic at kato/2, so the window can be hit by retry and by timing; the bug was also observed occurring spontaneously in production. Once won, the leaked reserved tag is permanent \\u2014 no further conditions are needed.\\nPR:N - No credentials on the victim host are required \\u2014 the triggering events (TCP FIN/RST, malformed NVMe/TCP PDU, unresponsive target) are handled by `nvme_tcp_state_change()` and the recv path before or independent of any NVMe-level authentication, and NVMe/TCP deployments commonly run with no DH-HMAC-CHAP or TLS at all.\\nUI:N - Exploitation requires no action from any user or administrator; an already-established NVMe-oF connection is a system configuration precondition, not victim interaction, and the keep-alive/reset machinery runs autonomously in kernel workqueues.\\nS:U - The impact is confined to the kernel and the host\u0027s own storage stack \\u2014 no security authority boundary such as a VM, IOMMU, or sandbox is crossed.\\nC:N - The defect is a reserved-tag leak causing an ABBA allocation deadlock; no memory is read out of bounds, no freed object is accessed, and no kernel data is disclosed to the attacker.\\nI:N - There is no memory corruption, out-of-bounds write, or control-flow primitive \\u2014 the only consequence is that a blk-mq tag is never returned, so no attacker-influenced data modification is possible.\\nA:H - The admin queue can never reconnect (\\\"failed to reconnect admin_q forever\\\"), because the admin tagset is not reallocated on reconnect and the connect command\u0027s reserved tag allocation fails with -EAGAIN indefinitely, producing a permanent loss of the NVMe-oF storage path plus eventual controller deletion (and a hung, unkillable teardown worker blocked on queue freeze) \\u2014 total availability loss for storage that is frequently the system\u0027s root or primary data volume.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"ed01fee283a067c72b2d6500046080dbc1bb9dae\", \"lessThan\": \"149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ed01fee283a067c72b2d6500046080dbc1bb9dae\", \"lessThan\": \"ff2f90f88d78559802466ad1c84ac5bda4416b3a\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ed01fee283a067c72b2d6500046080dbc1bb9dae\", \"lessThan\": \"6851778504cdb49431809b4ba061903d5f592c96\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ed01fee283a067c72b2d6500046080dbc1bb9dae\", \"lessThan\": \"262da920896e2f2ab0e3947d9dbee0aa09045818\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"ed01fee283a067c72b2d6500046080dbc1bb9dae\", \"lessThan\": \"de105068fead55ed5c07ade75e9c8e7f86a00d1d\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/nvme/host/core.c\", \"drivers/nvme/host/fabrics.h\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.12\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.12\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.1.83\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.23\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.7.11\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.7.*\"}, {\"status\": \"unaffected\", \"version\": \"6.8.2\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.8.*\"}, {\"status\": \"unaffected\", \"version\": \"6.9\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/nvme/host/core.c\", \"drivers/nvme/host/fabrics.h\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/149afee5c7418ec5db9d7387b9c9a5c1eb7ea2a8\"}, {\"url\": \"https://git.kernel.org/stable/c/ff2f90f88d78559802466ad1c84ac5bda4416b3a\"}, {\"url\": \"https://git.kernel.org/stable/c/6851778504cdb49431809b4ba061903d5f592c96\"}, {\"url\": \"https://git.kernel.org/stable/c/262da920896e2f2ab0e3947d9dbee0aa09045818\"}, {\"url\": \"https://git.kernel.org/stable/c/de105068fead55ed5c07ade75e9c8e7f86a00d1d\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnvme: fix reconnection fail due to reserved tag allocation\\n\\nWe found a issue on production environment while using NVMe over RDMA,\\nadmin_q reconnect failed forever while remote target and network is ok.\\nAfter dig into it, we found it may caused by a ABBA deadlock due to tag\\nallocation. In my case, the tag was hold by a keep alive request\\nwaiting inside admin_q, as we quiesced admin_q while reset ctrl, so the\\nrequest maked as idle and will not process before reset success. As\\nfabric_q shares tagset with admin_q, while reconnect remote target, we\\nneed a tag for connect command, but the only one reserved tag was held\\nby keep alive command which waiting inside admin_q. As a result, we\\nfailed to reconnect admin_q forever. In order to fix this issue, I\\nthink we should keep two reserved tags for admin queue.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.83\", \"versionStartIncluding\": \"5.12\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.23\", \"versionStartIncluding\": \"5.12\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.7.11\", \"versionStartIncluding\": \"5.12\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.8.2\", \"versionStartIncluding\": \"5.12\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.9\", \"versionStartIncluding\": \"5.12\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:29:48.601Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-27435\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:29:48.601Z\", \"dateReserved\": \"2024-02-25T13:47:42.687Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-05-17T12:12:36.439Z\", \"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.