CVE-2021-47469 (GCVE-0-2021-47469)

Vulnerability from cvelistv5 – Published: 2024-05-22 06:23 – Updated: 2025-03-03 08:16
VLAI

This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "providerMetadata": {
        "dateUpdated": "2025-03-03T08:16:40.401Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "rejectedReasons": [
        {
          "lang": "en",
          "value": "This CVE ID has been rejected or withdrawn by its CVE Numbering Authority."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2021-47469",
    "datePublished": "2024-05-22T06:23:27.629Z",
    "dateRejected": "2025-03-03T08:16:40.401Z",
    "dateReserved": "2024-05-22T06:20:56.199Z",
    "dateUpdated": "2025-03-03T08:16:40.401Z",
    "state": "REJECTED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "fkie_nvd": {
      "configurations": "[{\"nodes\": [{\"operator\": \"OR\", \"negate\": false, \"cpeMatch\": [{\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionEndExcluding\": \"5.4.286\", \"matchCriteriaId\": \"861FB0F9-099B-45A4-AB6A-737DEFA1490E\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.5\", \"versionEndExcluding\": \"5.10.230\", \"matchCriteriaId\": \"BF5B32D0-72C9-41C3-A0BB-D4946153C134\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"versionStartIncluding\": \"5.11\", \"versionEndExcluding\": \"5.14.15\", \"matchCriteriaId\": \"63BD46C4-473F-45F9-93E9-F67D955321D8\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:5.15:rc1:*:*:*:*:*:*\", \"matchCriteriaId\": \"E46C74C6-B76B-4C94-A6A4-FD2FFF62D644\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:5.15:rc2:*:*:*:*:*:*\", \"matchCriteriaId\": \"60134C3A-06E4-48C1-B04F-2903732A4E56\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:5.15:rc3:*:*:*:*:*:*\", \"matchCriteriaId\": \"0460DA88-8FE1-46A2-9DDA-1F1ABA552E71\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:5.15:rc4:*:*:*:*:*:*\", \"matchCriteriaId\": \"AF55383D-4DF2-45DC-93F7-571F4F978EAB\"}, {\"vulnerable\": true, \"criteria\": \"cpe:2.3:o:linux:linux_kernel:5.15:rc5:*:*:*:*:*:*\", \"matchCriteriaId\": \"9E9481B2-8AA6-4CBD-B5D3-C10F51FF6D01\"}]}]}]",
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nspi: Fix deadlock when adding SPI controllers on SPI buses\\n\\nCurrently we have a global spi_add_lock which we take when adding new\\ndevices so that we can check that we\u0027re not trying to reuse a chip\\nselect that\u0027s already controlled.  This means that if the SPI device is\\nitself a SPI controller and triggers the instantiation of further SPI\\ndevices we trigger a deadlock as we try to register and instantiate\\nthose devices while in the process of doing so for the parent controller\\nand hence already holding the global spi_add_lock.  Since we only care\\nabout concurrency within a single SPI bus move the lock to be per\\ncontroller, avoiding the deadlock.\\n\\nThis can be easily triggered in the case of spi-mux.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: spi: soluciona el punto muerto al agregar controladores SPI en buses SPI. Actualmente tenemos un spi_add_lock global que utilizamos cuando agregamos nuevos dispositivos para que podamos verificar que no estamos intentando reutilizar un selecci\\u00f3n de chip que ya est\\u00e1 controlado. Esto significa que si el dispositivo SPI es en s\\u00ed mismo un controlador SPI y activa la creaci\\u00f3n de instancias de otros dispositivos SPI, desencadenaremos un punto muerto cuando intentamos registrar y crear instancias de esos dispositivos mientras estamos en el proceso de hacerlo para el controlador principal y, por lo tanto, ya tenemos el control global. spi_add_lock. Dado que solo nos importa la concurrencia dentro de un \\u00fanico bus SPI, mueva el bloqueo para que sea por controlador, evitando el punto muerto. Esto se puede activar f\\u00e1cilmente en el caso de spi-mux.\"}]",
      "id": "CVE-2021-47469",
      "lastModified": "2025-01-10T18:17:53.087",
      "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}]}",
      "published": "2024-05-22T07:15:11.690",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/6098475d4cb48d821bdf453c61118c56e26294f0\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/722ef19a161ce3fffb3d1b01ce2301c306639bdd\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/aa3f3d7bef59583f2d3234173105a27ff61ef8fe\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/c8dce228db6f81dbc897a018dfc5c418e917cf64\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/6098475d4cb48d821bdf453c61118c56e26294f0\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\"]}, {\"url\": \"https://git.kernel.org/stable/c/722ef19a161ce3fffb3d1b01ce2301c306639bdd\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\", \"tags\": [\"Patch\"]}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Analyzed",
      "weaknesses": "[{\"source\": \"nvd@nist.gov\", \"type\": \"Primary\", \"description\": [{\"lang\": \"en\", \"value\": \"CWE-667\"}]}]"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-47469\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-22T07:15:11.690\",\"lastModified\":\"2025-03-03T09:15:09.473\",\"vulnStatus\":\"Rejected\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}],\"metrics\":{},\"references\":[]}}",
    "vulnrichment": {
      "containers": "{\"cna\": {\"rejectedReasons\": [{\"lang\": \"en\", \"value\": \"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2025-03-03T08:16:40.401Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2021-47469\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"state\": \"REJECTED\", \"assignerShortName\": \"Linux\", \"dateReserved\": \"2024-05-22T06:20:56.199Z\", \"datePublished\": \"2024-05-22T06:23:27.629Z\", \"dateUpdated\": \"2025-03-03T08:16:40.401Z\", \"dateRejected\": \"2025-03-03T08:16:40.401Z\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}


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.