GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration

CVE-2024-53152 (GCVE-0-2024-53152)

Vulnerability from cvelistv5 – Published: 2024-12-24 11:28 – Updated: 2026-05-11 20:51
VLAI
Title
PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()
Summary
In the Linux kernel, the following vulnerability has been resolved: PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert() Currently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF deinit notify function pci_epc_deinit_notify() are called during the execution of pex_ep_event_pex_rst_assert() i.e., when the host has asserted PERST#. But quickly after this step, refclk will also be disabled by the host. All of the tegra194 endpoint SoCs supported as of now depend on the refclk from the host for keeping the controller operational. Due to this limitation, any access to the hardware registers in the absence of refclk will result in a whole endpoint crash. Unfortunately, most of the controller cleanups require accessing the hardware registers (like eDMA cleanup performed in dw_pcie_ep_cleanup(), etc...). So these cleanup functions can cause the crash in the endpoint SoC once host asserts PERST#. One way to address this issue is by generating the refclk in the endpoint itself and not depending on the host. But that is not always possible as some of the endpoint designs do require the endpoint to consume refclk from the host. Thus, fix this crash by moving the controller cleanups to the start of the pex_ep_event_pex_rst_deassert() function. This function is called whenever the host has deasserted PERST# and it is guaranteed that the refclk would be active at this point. So at the start of this function (after enabling resources) the controller cleanup can be performed. Once finished, rest of the code execution for PERST# deassert can continue as usual.
Severity
5.5 (Medium)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Assigner
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: 570d7715eed8a29ac5bd96c7694f060a991e5a31 , < 70212c2300971506e986d95000d2745529cac9d7 (git)
Affected: 570d7715eed8a29ac5bd96c7694f060a991e5a31 , < 72034050ccf4202cd6558b0afd2474f756ea3b9b (git)
Affected: 570d7715eed8a29ac5bd96c7694f060a991e5a31 , < 40e2125381dc11379112485e3eefdd25c6df5375 (git)
guessed Create a notification for this product.
Linux Linux Affected: 6.10
Unaffected: 0 , < 6.10 (semver)
Unaffected: 6.11.11 , ≤ 6.11.* (semver)
Unaffected: 6.12.2 , ≤ 6.12.* (semver)
Unaffected: 6.13 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/pci/controller/dwc/pcie-tegra194.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "70212c2300971506e986d95000d2745529cac9d7",
              "status": "affected",
              "version": "570d7715eed8a29ac5bd96c7694f060a991e5a31",
              "versionType": "git"
            },
            {
              "lessThan": "72034050ccf4202cd6558b0afd2474f756ea3b9b",
              "status": "affected",
              "version": "570d7715eed8a29ac5bd96c7694f060a991e5a31",
              "versionType": "git"
            },
            {
              "lessThan": "40e2125381dc11379112485e3eefdd25c6df5375",
              "status": "affected",
              "version": "570d7715eed8a29ac5bd96c7694f060a991e5a31",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/pci/controller/dwc/pcie-tegra194.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "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.11.11",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.2",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nPCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()\n\nCurrently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF\ndeinit notify function pci_epc_deinit_notify() are called during the\nexecution of pex_ep_event_pex_rst_assert() i.e., when the host has asserted\nPERST#. But quickly after this step, refclk will also be disabled by the\nhost.\n\nAll of the tegra194 endpoint SoCs supported as of now depend on the refclk\nfrom the host for keeping the controller operational. Due to this\nlimitation, any access to the hardware registers in the absence of refclk\nwill result in a whole endpoint crash. Unfortunately, most of the\ncontroller cleanups require accessing the hardware registers (like eDMA\ncleanup performed in dw_pcie_ep_cleanup(), etc...). So these cleanup\nfunctions can cause the crash in the endpoint SoC once host asserts PERST#.\n\nOne way to address this issue is by generating the refclk in the endpoint\nitself and not depending on the host. But that is not always possible as\nsome of the endpoint designs do require the endpoint to consume refclk from\nthe host.\n\nThus, fix this crash by moving the controller cleanups to the start of\nthe pex_ep_event_pex_rst_deassert() function. This function is called\nwhenever the host has deasserted PERST# and it is guaranteed that the\nrefclk would be active at this point. So at the start of this function\n(after enabling resources) the controller cleanup can be performed. Once\nfinished, rest of the code execution for PERST# deassert can continue as\nusual."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:51:51.816Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/70212c2300971506e986d95000d2745529cac9d7"
        },
        {
          "url": "https://git.kernel.org/stable/c/72034050ccf4202cd6558b0afd2474f756ea3b9b"
        },
        {
          "url": "https://git.kernel.org/stable/c/40e2125381dc11379112485e3eefdd25c6df5375"
        }
      ],
      "title": "PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-53152",
    "datePublished": "2024-12-24T11:28:51.610Z",
    "dateReserved": "2024-11-19T17:17:25.000Z",
    "dateUpdated": "2026-05-11T20:51:51.816Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-53152",
      "date": "2026-09-16",
      "epss": "0.00272",
      "percentile": "0.19696"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nPCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()\\n\\nCurrently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF\\ndeinit notify function pci_epc_deinit_notify() are called during the\\nexecution of pex_ep_event_pex_rst_assert() i.e., when the host has asserted\\nPERST#. But quickly after this step, refclk will also be disabled by the\\nhost.\\n\\nAll of the tegra194 endpoint SoCs supported as of now depend on the refclk\\nfrom the host for keeping the controller operational. Due to this\\nlimitation, any access to the hardware registers in the absence of refclk\\nwill result in a whole endpoint crash. Unfortunately, most of the\\ncontroller cleanups require accessing the hardware registers (like eDMA\\ncleanup performed in dw_pcie_ep_cleanup(), etc...). So these cleanup\\nfunctions can cause the crash in the endpoint SoC once host asserts PERST#.\\n\\nOne way to address this issue is by generating the refclk in the endpoint\\nitself and not depending on the host. But that is not always possible as\\nsome of the endpoint designs do require the endpoint to consume refclk from\\nthe host.\\n\\nThus, fix this crash by moving the controller cleanups to the start of\\nthe pex_ep_event_pex_rst_deassert() function. This function is called\\nwhenever the host has deasserted PERST# and it is guaranteed that the\\nrefclk would be active at this point. So at the start of this function\\n(after enabling resources) the controller cleanup can be performed. Once\\nfinished, rest of the code execution for PERST# deassert can continue as\\nusual.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: PCI: tegra194: Mover las desinfecciones del controlador a pex_ep_event_pex_rst_deassert(). Actualmente, la funci\\u00f3n de desinfecci\\u00f3n de endpoints dw_pcie_ep_cleanup() y la funci\\u00f3n de notificaci\\u00f3n deinit de EPF pci_epc_deinit_notify() se llaman durante la ejecuci\\u00f3n de pex_ep_event_pex_rst_assert(), es decir , cuando el anfitri\\u00f3n tiene afirm\\u00f3 PREST#. Pero poco despu\\u00e9s de este paso, el host tambi\\u00e9n desactivar\\u00e1 refclk. Todos los SoC de endpoint tegra194 admitidos a partir de ahora dependen de la refclk del host para mantener el controlador operativo. Debido a esta limitaci\\u00f3n, cualquier acceso a los registros de hardware en ausencia de refclk resultar\\u00e1 en una falla completa del endpoint. Desafortunadamente, la mayor\\u00eda de las desinfecciones del controlador requieren acceder a los registros de hardware (como la desinfecci\\u00f3n eDMA realizada en dw_pcie_ep_cleanup(), etc...). Por lo tanto, estas funciones de desinfecci\\u00f3n pueden provocar el bloqueo del SoC del endpoint una vez que el host afirma el n\\u00famero PREST. Una forma de abordar este problema es generando el refclk en el propio endpoint y sin depender del host. Pero eso no siempre es posible ya que algunos de los dise\\u00f1os de terminales requieren que el terminal consuma refclk del host. Por lo tanto, solucione este bloqueo moviendo las desinfecciones del controlador al inicio de la funci\\u00f3n pex_ep_event_pex_rst_deassert(). Esta funci\\u00f3n se llama siempre que el host ha anulado PERST# y se garantiza que refclk estar\\u00e1 activo en este punto. Entonces, al inicio de esta funci\\u00f3n (despu\\u00e9s de habilitar los recursos), se puede realizar la desinfecci\\u00f3n del controlador. Una vez finalizado, el resto de la ejecuci\\u00f3n del c\\u00f3digo para la desactivaci\\u00f3n de PERST# puede continuar como de costumbre.\"}]",
      "id": "CVE-2024-53152",
      "lastModified": "2024-12-24T12:15:23.353",
      "published": "2024-12-24T12:15:23.353",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/40e2125381dc11379112485e3eefdd25c6df5375\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/70212c2300971506e986d95000d2745529cac9d7\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/72034050ccf4202cd6558b0afd2474f756ea3b9b\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-53152\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-24T12:15:23.353\",\"lastModified\":\"2026-06-17T08:08:25.980\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nPCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()\\n\\nCurrently, the endpoint cleanup function dw_pcie_ep_cleanup() and EPF\\ndeinit notify function pci_epc_deinit_notify() are called during the\\nexecution of pex_ep_event_pex_rst_assert() i.e., when the host has asserted\\nPERST#. But quickly after this step, refclk will also be disabled by the\\nhost.\\n\\nAll of the tegra194 endpoint SoCs supported as of now depend on the refclk\\nfrom the host for keeping the controller operational. Due to this\\nlimitation, any access to the hardware registers in the absence of refclk\\nwill result in a whole endpoint crash. Unfortunately, most of the\\ncontroller cleanups require accessing the hardware registers (like eDMA\\ncleanup performed in dw_pcie_ep_cleanup(), etc...). So these cleanup\\nfunctions can cause the crash in the endpoint SoC once host asserts PERST#.\\n\\nOne way to address this issue is by generating the refclk in the endpoint\\nitself and not depending on the host. But that is not always possible as\\nsome of the endpoint designs do require the endpoint to consume refclk from\\nthe host.\\n\\nThus, fix this crash by moving the controller cleanups to the start of\\nthe pex_ep_event_pex_rst_deassert() function. This function is called\\nwhenever the host has deasserted PERST# and it is guaranteed that the\\nrefclk would be active at this point. So at the start of this function\\n(after enabling resources) the controller cleanup can be performed. Once\\nfinished, rest of the code execution for PERST# deassert can continue as\\nusual.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: PCI: tegra194: Mover las desinfecciones del controlador a pex_ep_event_pex_rst_deassert(). Actualmente, la funci\u00f3n de desinfecci\u00f3n de endpoints dw_pcie_ep_cleanup() y la funci\u00f3n de notificaci\u00f3n deinit de EPF pci_epc_deinit_notify() se llaman durante la ejecuci\u00f3n de pex_ep_event_pex_rst_assert(), es decir , cuando el anfitri\u00f3n tiene afirm\u00f3 PREST#. Pero poco despu\u00e9s de este paso, el host tambi\u00e9n desactivar\u00e1 refclk. Todos los SoC de endpoint tegra194 admitidos a partir de ahora dependen de la refclk del host para mantener el controlador operativo. Debido a esta limitaci\u00f3n, cualquier acceso a los registros de hardware en ausencia de refclk resultar\u00e1 en una falla completa del endpoint. Desafortunadamente, la mayor\u00eda de las desinfecciones del controlador requieren acceder a los registros de hardware (como la desinfecci\u00f3n eDMA realizada en dw_pcie_ep_cleanup(), etc...). Por lo tanto, estas funciones de desinfecci\u00f3n pueden provocar el bloqueo del SoC del endpoint una vez que el host afirma el n\u00famero PREST. Una forma de abordar este problema es generando el refclk en el propio endpoint y sin depender del host. Pero eso no siempre es posible ya que algunos de los dise\u00f1os de terminales requieren que el terminal consuma refclk del host. Por lo tanto, solucione este bloqueo moviendo las desinfecciones del controlador al inicio de la funci\u00f3n pex_ep_event_pex_rst_deassert(). Esta funci\u00f3n se llama siempre que el host ha anulado PERST# y se garantiza que refclk estar\u00e1 activo en este punto. Entonces, al inicio de esta funci\u00f3n (despu\u00e9s de habilitar los recursos), se puede realizar la desinfecci\u00f3n del controlador. Una vez finalizado, el resto de la ejecuci\u00f3n del c\u00f3digo para la desactivaci\u00f3n de PERST# puede continuar como de costumbre.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"drivers/pci/controller/dwc/pcie-tegra194.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"570d7715eed8a29ac5bd96c7694f060a991e5a31\",\"lessThan\":\"70212c2300971506e986d95000d2745529cac9d7\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"570d7715eed8a29ac5bd96c7694f060a991e5a31\",\"lessThan\":\"72034050ccf4202cd6558b0afd2474f756ea3b9b\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"570d7715eed8a29ac5bd96c7694f060a991e5a31\",\"lessThan\":\"40e2125381dc11379112485e3eefdd25c6df5375\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"drivers/pci/controller/dwc/pcie-tegra194.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"6.10\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"6.10\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.11.11\",\"lessThanOrEqual\":\"6.11.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.12.2\",\"lessThanOrEqual\":\"6.12.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.13\",\"lessThanOrEqual\":\"*\",\"versionType\":\"original_commit_for_fix\",\"status\":\"unaffected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.10\",\"versionEndExcluding\":\"6.11.11\",\"matchCriteriaId\":\"158A6B22-9260-41D7-965A-A81798A5A969\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.12\",\"versionEndExcluding\":\"6.12.2\",\"matchCriteriaId\":\"D8882B1B-2ABC-4838-AC1D-DBDBB5764776\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/40e2125381dc11379112485e3eefdd25c6df5375\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/70212c2300971506e986d95000d2745529cac9d7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/72034050ccf4202cd6558b0afd2474f756ea3b9b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-06-28T08:15:00+00:00",
      "cve": "CVE-2024-53152",
      "id": "CVE-2024-53152",
      "initial_release_date": "2024-12-24T00:00:00+00:00",
      "product_status:fixed": "305",
      "product_status:known_affected": "22",
      "product_status:known_not_affected": "90",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: PCI: tegra194: Move controller cleanups to pex_ep_event_pex_rst_deassert()",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-53152.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-08-31T00:27:18Z",
      "cve": "CVE-2024-53152",
      "id": "CVE-2024-53152",
      "initial_release_date": "2024-12-27T00:16:59Z",
      "product_status:known_not_affected": "547",
      "product_status:recommended": "121",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2024-53152",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2024-53152.json",
      "version": "27"
    }
  }
}



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.


Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.