CVE-2023-52775 (GCVE-0-2023-52775)

Vulnerability from cvelistv5 – Published: 2024-05-21 15:30 – Updated: 2026-08-05 09:11
VLAI
Title
net/smc: avoid data corruption caused by decline
Summary
In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid data corruption caused by decline We found a data corruption issue during testing of SMC-R on Redis applications. The benchmark has a low probability of reporting a strange error as shown below. "Error: Protocol error, got "\xe2" as reply type byte" Finally, we found that the retrieved error data was as follows: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 It is quite obvious that this is a SMC DECLINE message, which means that the applications received SMC protocol message. We found that this was caused by the following situations: client server ¦ clc proposal -------------> ¦ clc accept <------------- ¦ clc confirm -------------> wait llc confirm send llc confirm ¦failed llc confirm ¦ x------ (after 2s)timeout wait llc confirm rsp wait decline (after 1s) timeout (after 2s) timeout ¦ decline --------------> ¦ decline <-------------- As a result, a decline message was sent in the implementation, and this message was read from TCP by the already-fallback connection. This patch double the client timeout as 2x of the server value, With this simple change, the Decline messages should never cross or collide (during Confirm link timeout). This issue requires an immediate solution, since the protocol updates involve a more long-term solution.
Severity
8.2 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 , < 5ada292b5c504720a0acef8cae9acc62a694d19c (git)
Affected: 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 , < 90072af9efe8c7bd7d086709014ddd44cebd5e7c (git)
Affected: 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 , < 94a0ae698b4d5d5bb598e23228002a1491c50add (git)
Affected: 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 , < 7234d2b5dffa5af77fd4e0deaebab509e130c6b1 (git)
Affected: 0fb0b02bd6fd26cba38002be4a6bbcae2228fd44 , < e6d71b437abc2f249e3b6a1ae1a7228e09c6e563 (git)
Create a notification for this product.
Linux Linux Affected: 5.8
Unaffected: 0 , < 5.8 (semver)
Unaffected: 5.10.203 , ≤ 5.10.* (semver)
Unaffected: 5.15.141 , ≤ 5.15.* (semver)
Unaffected: 6.1.65 , ≤ 6.1.* (semver)
Unaffected: 6.6.4 , ≤ 6.6.* (semver)
Unaffected: 6.7 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2023-52775",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-22T18:24:43.628155Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-04T17:22:47.888Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T23:11:35.820Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "5ada292b5c504720a0acef8cae9acc62a694d19c",
              "status": "affected",
              "version": "0fb0b02bd6fd26cba38002be4a6bbcae2228fd44",
              "versionType": "git"
            },
            {
              "lessThan": "90072af9efe8c7bd7d086709014ddd44cebd5e7c",
              "status": "affected",
              "version": "0fb0b02bd6fd26cba38002be4a6bbcae2228fd44",
              "versionType": "git"
            },
            {
              "lessThan": "94a0ae698b4d5d5bb598e23228002a1491c50add",
              "status": "affected",
              "version": "0fb0b02bd6fd26cba38002be4a6bbcae2228fd44",
              "versionType": "git"
            },
            {
              "lessThan": "7234d2b5dffa5af77fd4e0deaebab509e130c6b1",
              "status": "affected",
              "version": "0fb0b02bd6fd26cba38002be4a6bbcae2228fd44",
              "versionType": "git"
            },
            {
              "lessThan": "e6d71b437abc2f249e3b6a1ae1a7228e09c6e563",
              "status": "affected",
              "version": "0fb0b02bd6fd26cba38002be4a6bbcae2228fd44",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/smc/af_smc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.8"
            },
            {
              "lessThan": "5.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.203",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.141",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.65",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.7",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.203",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.141",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.65",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.4",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.7",
                  "versionStartIncluding": "5.8",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: avoid data corruption caused by decline\n\nWe found a data corruption issue during testing of SMC-R on Redis\napplications.\n\nThe benchmark has a low probability of reporting a strange error as\nshown below.\n\n\"Error: Protocol error, got \"\\xe2\" as reply type byte\"\n\nFinally, we found that the retrieved error data was as follows:\n\n0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C\n0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00\n0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2\n\nIt is quite obvious that this is a SMC DECLINE message, which means that\nthe applications received SMC protocol message.\nWe found that this was caused by the following situations:\n\nclient                  server\n        \u00a6  clc proposal\n        -------------\u003e\n        \u00a6  clc accept\n        \u003c-------------\n        \u00a6  clc confirm\n        -------------\u003e\nwait llc confirm\n\t\t\tsend llc confirm\n        \u00a6failed llc confirm\n        \u00a6   x------\n(after 2s)timeout\n                        wait llc confirm rsp\n\nwait decline\n\n(after 1s) timeout\n                        (after 2s) timeout\n        \u00a6   decline\n        --------------\u003e\n        \u00a6   decline\n        \u003c--------------\n\nAs a result, a decline message was sent in the implementation, and this\nmessage was read from TCP by the already-fallback connection.\n\nThis patch double the client timeout as 2x of the server value,\nWith this simple change, the Decline messages should never cross or\ncollide (during Confirm link timeout).\n\nThis issue requires an immediate solution, since the protocol updates\ninvolve a more long-term solution."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 8.2,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - SMC-R CLC handshake and DECLINE exchange run over TCP with a remote peer; a network attacker who speaks SMC to an SMC-enabled service (e.g. smc_run Redis/nginx) can drive the confirm-link timeout and fallback path.\nAC:L - A malicious SMC peer can withhold the RoCE LLC CONFIRM LINK response and thereby force both sides through the fixed timeout/decline sequence; the client/server wait asymmetry makes decline crossing a reliable consequence rather than an uncontrolled race.\nPR:N - The vulnerable path runs during unauthenticated SMC connection setup; no credentials or privileges are required beyond being able to complete the CLC handshake as a peer.\nUI:N - Exploitation does not need a victim user action; the attacker initiates or participates in the SMC connection and triggers the timeout/decline path directly.\nS:U - Impact stays within the same host kernel and the affected connection\u2019s application data; there is no VM, IOMMU, or other security-authority boundary crossing.\nC:N - The bug only injects a kernel-generated CLC DECLINE into the stream; it does not disclose arbitrary memory or other confidential data beyond ordinary peer protocol fields.\nI:H - CLC DECLINE bytes are delivered as application payload after TCP fallback, corrupting the data stream (e.g. Redis protocol errors), which is a serious integrity break of SMC\u2019s guarantee that CLC is consumed by the kernel.\nA:L - Corrupted messages cause application-level protocol failures and interrupted operations on affected connections, but there is no kernel oops/panic or complete host denial of service."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T09:11:22.428Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c"
        },
        {
          "url": "https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c"
        },
        {
          "url": "https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add"
        },
        {
          "url": "https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1"
        },
        {
          "url": "https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563"
        }
      ],
      "title": "net/smc: avoid data corruption caused by decline",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-52775",
    "datePublished": "2024-05-21T15:30:56.247Z",
    "dateReserved": "2024-05-21T15:19:24.239Z",
    "dateUpdated": "2026-08-05T09:11:22.428Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2023-52775",
      "date": "2026-08-09",
      "epss": "0.00664",
      "percentile": "0.48326"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: avoid data corruption caused by decline\\n\\nWe found a data corruption issue during testing of SMC-R on Redis\\napplications.\\n\\nThe benchmark has a low probability of reporting a strange error as\\nshown below.\\n\\n\\\"Error: Protocol error, got \\\"\\\\xe2\\\" as reply type byte\\\"\\n\\nFinally, we found that the retrieved error data was as follows:\\n\\n0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C\\n0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00\\n0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2\\n\\nIt is quite obvious that this is a SMC DECLINE message, which means that\\nthe applications received SMC protocol message.\\nWe found that this was caused by the following situations:\\n\\nclient                  server\\n        \\u00a6  clc proposal\\n        -------------\u003e\\n        \\u00a6  clc accept\\n        \u003c-------------\\n        \\u00a6  clc confirm\\n        -------------\u003e\\nwait llc confirm\\n\\t\\t\\tsend llc confirm\\n        \\u00a6failed llc confirm\\n        \\u00a6   x------\\n(after 2s)timeout\\n                        wait llc confirm rsp\\n\\nwait decline\\n\\n(after 1s) timeout\\n                        (after 2s) timeout\\n        \\u00a6   decline\\n        --------------\u003e\\n        \\u00a6   decline\\n        \u003c--------------\\n\\nAs a result, a decline message was sent in the implementation, and this\\nmessage was read from TCP by the already-fallback connection.\\n\\nThis patch double the client timeout as 2x of the server value,\\nWith this simple change, the Decline messages should never cross or\\ncollide (during Confirm link timeout).\\n\\nThis issue requires an immediate solution, since the protocol updates\\ninvolve a more long-term solution.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se resolvi\\u00f3 la siguiente vulnerabilidad: net/smc: evita la corrupci\\u00f3n de datos causada por el rechazo. Encontramos un problema de corrupci\\u00f3n de datos durante las pruebas de SMC-R en aplicaciones Redis. El punto de referencia tiene una baja probabilidad de informar un error extra\\u00f1o, como se muestra a continuaci\\u00f3n. \\\"Error: Error de protocolo, obtuve \\\"\\\\xe2\\\" como byte de tipo de respuesta\\\" Finalmente, encontramos que los datos de error recuperados eran los siguientes: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 1 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 Es bastante obvio que este es un mensaje SMC DECLINE, lo que significa que las aplicaciones recibieron un mensaje de protocolo SMC. Descubrimos que esto se deb\\u00eda a las siguientes situaciones: cliente servidor \\u00a6 propuesta clc -------------\u0026gt; \\u00a6 clc aceptar \u0026lt;------------- \\u00a6 clc confirmar -------------\u0026gt; esperar confirmaci\\u00f3n de llc enviar confirmaci\\u00f3n de llc \\u00a6 confirmaci\\u00f3n de llc fallida \\u00a6 x------ (despu\\u00e9s de 2 s) tiempo de espera de espera llc confirmar rsp esperar declinar (despu\\u00e9s de 1 s) tiempo de espera (despu\\u00e9s de 2s) tiempo de espera \\u00a6 rechazo --------------\u0026gt; \\u00a6 rechazo \u0026lt;-------------- Como resultado, se envi\\u00f3 un mensaje de rechazo en la implementaci\\u00f3n, y este mensaje fue le\\u00eddo desde TCP por la conexi\\u00f3n que ya estaba en reserva. Este parche duplica el tiempo de espera del cliente al doble del valor del servidor. Con este simple cambio, los mensajes de rechazo nunca deber\\u00edan cruzarse ni colisionar (durante el tiempo de espera de confirmaci\\u00f3n del enlace). Este problema requiere una soluci\\u00f3n inmediata, ya que las actualizaciones del protocolo implican una soluci\\u00f3n a m\\u00e1s largo plazo.\"}]",
      "id": "CVE-2023-52775",
      "lastModified": "2024-11-21T08:40:33.770",
      "published": "2024-05-21T16:15:16.610",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}, {\"url\": \"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\", \"source\": \"af854a3a-2127-422b-91ae-364da2661108\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-52775\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-21T16:15:16.610\",\"lastModified\":\"2026-08-04T10:18:41.190\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: avoid data corruption caused by decline\\n\\nWe found a data corruption issue during testing of SMC-R on Redis\\napplications.\\n\\nThe benchmark has a low probability of reporting a strange error as\\nshown below.\\n\\n\\\"Error: Protocol error, got \\\"\\\\xe2\\\" as reply type byte\\\"\\n\\nFinally, we found that the retrieved error data was as follows:\\n\\n0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C\\n0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00\\n0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2\\n\\nIt is quite obvious that this is a SMC DECLINE message, which means that\\nthe applications received SMC protocol message.\\nWe found that this was caused by the following situations:\\n\\nclient                  server\\n        \u00a6  clc proposal\\n        -------------\u003e\\n        \u00a6  clc accept\\n        \u003c-------------\\n        \u00a6  clc confirm\\n        -------------\u003e\\nwait llc confirm\\n\\t\\t\\tsend llc confirm\\n        \u00a6failed llc confirm\\n        \u00a6   x------\\n(after 2s)timeout\\n                        wait llc confirm rsp\\n\\nwait decline\\n\\n(after 1s) timeout\\n                        (after 2s) timeout\\n        \u00a6   decline\\n        --------------\u003e\\n        \u00a6   decline\\n        \u003c--------------\\n\\nAs a result, a decline message was sent in the implementation, and this\\nmessage was read from TCP by the already-fallback connection.\\n\\nThis patch double the client timeout as 2x of the server value,\\nWith this simple change, the Decline messages should never cross or\\ncollide (during Confirm link timeout).\\n\\nThis issue requires an immediate solution, since the protocol updates\\ninvolve a more long-term solution.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: net/smc: evita la corrupci\u00f3n de datos causada por el rechazo. Encontramos un problema de corrupci\u00f3n de datos durante las pruebas de SMC-R en aplicaciones Redis. El punto de referencia tiene una baja probabilidad de informar un error extra\u00f1o, como se muestra a continuaci\u00f3n. \\\"Error: Error de protocolo, obtuve \\\"\\\\xe2\\\" como byte de tipo de respuesta\\\" Finalmente, encontramos que los datos de error recuperados eran los siguientes: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 1 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 Es bastante obvio que este es un mensaje SMC DECLINE, lo que significa que las aplicaciones recibieron un mensaje de protocolo SMC. Descubrimos que esto se deb\u00eda a las siguientes situaciones: cliente servidor \u00a6 propuesta clc -------------\u0026gt; \u00a6 clc aceptar \u0026lt;------------- \u00a6 clc confirmar -------------\u0026gt; esperar confirmaci\u00f3n de llc enviar confirmaci\u00f3n de llc \u00a6 confirmaci\u00f3n de llc fallida \u00a6 x------ (despu\u00e9s de 2 s) tiempo de espera de espera llc confirmar rsp esperar declinar (despu\u00e9s de 1 s) tiempo de espera (despu\u00e9s de 2s) tiempo de espera \u00a6 rechazo --------------\u0026gt; \u00a6 rechazo \u0026lt;-------------- Como resultado, se envi\u00f3 un mensaje de rechazo en la implementaci\u00f3n, y este mensaje fue le\u00eddo desde TCP por la conexi\u00f3n que ya estaba en reserva. Este parche duplica el tiempo de espera del cliente al doble del valor del servidor. Con este simple cambio, los mensajes de rechazo nunca deber\u00edan cruzarse ni colisionar (durante el tiempo de espera de confirmaci\u00f3n del enlace). Este problema requiere una soluci\u00f3n inmediata, ya que las actualizaciones del protocolo implican una soluci\u00f3n a m\u00e1s largo plazo.\"}],\"affected\":[{\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"affectedData\":[{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"unaffected\",\"programFiles\":[\"net/smc/af_smc.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\",\"lessThan\":\"5ada292b5c504720a0acef8cae9acc62a694d19c\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\",\"lessThan\":\"90072af9efe8c7bd7d086709014ddd44cebd5e7c\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\",\"lessThan\":\"94a0ae698b4d5d5bb598e23228002a1491c50add\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\",\"lessThan\":\"7234d2b5dffa5af77fd4e0deaebab509e130c6b1\",\"versionType\":\"git\",\"status\":\"affected\"},{\"version\":\"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\",\"lessThan\":\"e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\",\"versionType\":\"git\",\"status\":\"affected\"}]},{\"vendor\":\"Linux\",\"product\":\"Linux\",\"defaultStatus\":\"affected\",\"programFiles\":[\"net/smc/af_smc.c\"],\"repo\":\"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\",\"versions\":[{\"version\":\"5.8\",\"status\":\"affected\"},{\"version\":\"0\",\"lessThan\":\"5.8\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.10.203\",\"lessThanOrEqual\":\"5.10.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"5.15.141\",\"lessThanOrEqual\":\"5.15.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.1.65\",\"lessThanOrEqual\":\"6.1.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.6.4\",\"lessThanOrEqual\":\"6.6.*\",\"versionType\":\"semver\",\"status\":\"unaffected\"},{\"version\":\"6.7\",\"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:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L\",\"baseScore\":8.2,\"baseSeverity\":\"HIGH\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":3.9,\"impactScore\":4.2},{\"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: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}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2024-05-22T18:24:43.628155Z\",\"id\":\"CVE-2023-52775\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-787\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.8\",\"versionEndExcluding\":\"5.10.203\",\"matchCriteriaId\":\"1D81473A-DAF9-4437-B25B-46E4E0D99C37\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.11\",\"versionEndExcluding\":\"5.15.141\",\"matchCriteriaId\":\"9B851604-748F-41E0-8B31-403CEA01E99D\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"6.1.65\",\"matchCriteriaId\":\"8A758252-8804-4E23-91B5-E0B5BAC3E15A\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.4\",\"matchCriteriaId\":\"86E0B7DD-2E2D-461D-996C-8E941AFE171F\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"3A0038DE-E183-4958-A6E3-CE3821FEAFBF\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"E31AD4FC-436C-44AB-BCAB-3A0B37F69EE0\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Patch\"]}]}}",
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-08-04T19:22:58+00:00",
      "cve": "CVE-2023-52775",
      "id": "CVE-2023-52775",
      "initial_release_date": "2023-01-01T00:00:00+00:00",
      "product_status:fixed": "679",
      "product_status:known_affected": "38",
      "product_status:known_not_affected": "50",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: net/smc: avoid data corruption caused by decline",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2023/cve-2023-52775.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-07-26T16:47:50Z",
      "cve": "CVE-2023-52775",
      "id": "CVE-2023-52775",
      "initial_release_date": "2024-06-07T02:30:33Z",
      "product_status:known_affected": "330",
      "product_status:known_not_affected": "138",
      "product_status:recommended": "676",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2023-52775",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2023-52775.json",
      "version": "77"
    },
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-02T23:11:35.820Z\"}}, {\"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2023-52775\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-05-22T18:24:43.628155Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-05-23T19:01:25.668Z\"}, \"title\": \"CISA ADP Vulnrichment\"}], \"cna\": {\"title\": \"net/smc: avoid data corruption caused by decline\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.1\", \"baseScore\": 8.2, \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:N - SMC-R CLC handshake and DECLINE exchange run over TCP with a remote peer; a network attacker who speaks SMC to an SMC-enabled service (e.g. smc_run Redis/nginx) can drive the confirm-link timeout and fallback path.\\nAC:L - A malicious SMC peer can withhold the RoCE LLC CONFIRM LINK response and thereby force both sides through the fixed timeout/decline sequence; the client/server wait asymmetry makes decline crossing a reliable consequence rather than an uncontrolled race.\\nPR:N - The vulnerable path runs during unauthenticated SMC connection setup; no credentials or privileges are required beyond being able to complete the CLC handshake as a peer.\\nUI:N - Exploitation does not need a victim user action; the attacker initiates or participates in the SMC connection and triggers the timeout/decline path directly.\\nS:U - Impact stays within the same host kernel and the affected connection\\u2019s application data; there is no VM, IOMMU, or other security-authority boundary crossing.\\nC:N - The bug only injects a kernel-generated CLC DECLINE into the stream; it does not disclose arbitrary memory or other confidential data beyond ordinary peer protocol fields.\\nI:H - CLC DECLINE bytes are delivered as application payload after TCP fallback, corrupting the data stream (e.g. Redis protocol errors), which is a serious integrity break of SMC\\u2019s guarantee that CLC is consumed by the kernel.\\nA:L - Corrupted messages cause application-level protocol failures and interrupted operations on affected connections, but there is no kernel oops/panic or complete host denial of service.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\", \"lessThan\": \"5ada292b5c504720a0acef8cae9acc62a694d19c\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\", \"lessThan\": \"90072af9efe8c7bd7d086709014ddd44cebd5e7c\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\", \"lessThan\": \"94a0ae698b4d5d5bb598e23228002a1491c50add\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\", \"lessThan\": \"7234d2b5dffa5af77fd4e0deaebab509e130c6b1\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"0fb0b02bd6fd26cba38002be4a6bbcae2228fd44\", \"lessThan\": \"e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\", \"versionType\": \"git\"}], \"programFiles\": [\"net/smc/af_smc.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.8\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.8\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.10.203\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.10.*\"}, {\"status\": \"unaffected\", \"version\": \"5.15.141\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"6.1.65\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.4\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.7\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"net/smc/af_smc.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/5ada292b5c504720a0acef8cae9acc62a694d19c\"}, {\"url\": \"https://git.kernel.org/stable/c/90072af9efe8c7bd7d086709014ddd44cebd5e7c\"}, {\"url\": \"https://git.kernel.org/stable/c/94a0ae698b4d5d5bb598e23228002a1491c50add\"}, {\"url\": \"https://git.kernel.org/stable/c/7234d2b5dffa5af77fd4e0deaebab509e130c6b1\"}, {\"url\": \"https://git.kernel.org/stable/c/e6d71b437abc2f249e3b6a1ae1a7228e09c6e563\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nnet/smc: avoid data corruption caused by decline\\n\\nWe found a data corruption issue during testing of SMC-R on Redis\\napplications.\\n\\nThe benchmark has a low probability of reporting a strange error as\\nshown below.\\n\\n\\\"Error: Protocol error, got \\\"\\\\xe2\\\" as reply type byte\\\"\\n\\nFinally, we found that the retrieved error data was as follows:\\n\\n0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C\\n0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00\\n0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2\\n\\nIt is quite obvious that this is a SMC DECLINE message, which means that\\nthe applications received SMC protocol message.\\nWe found that this was caused by the following situations:\\n\\nclient                  server\\n        \\u00a6  clc proposal\\n        -------------\u003e\\n        \\u00a6  clc accept\\n        \u003c-------------\\n        \\u00a6  clc confirm\\n        -------------\u003e\\nwait llc confirm\\n\\t\\t\\tsend llc confirm\\n        \\u00a6failed llc confirm\\n        \\u00a6   x------\\n(after 2s)timeout\\n                        wait llc confirm rsp\\n\\nwait decline\\n\\n(after 1s) timeout\\n                        (after 2s) timeout\\n        \\u00a6   decline\\n        --------------\u003e\\n        \\u00a6   decline\\n        \u003c--------------\\n\\nAs a result, a decline message was sent in the implementation, and this\\nmessage was read from TCP by the already-fallback connection.\\n\\nThis patch double the client timeout as 2x of the server value,\\nWith this simple change, the Decline messages should never cross or\\ncollide (during Confirm link timeout).\\n\\nThis issue requires an immediate solution, since the protocol updates\\ninvolve a more long-term solution.\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.10.203\", \"versionStartIncluding\": \"5.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"5.15.141\", \"versionStartIncluding\": \"5.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.65\", \"versionStartIncluding\": \"5.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.4\", \"versionStartIncluding\": \"5.8\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.7\", \"versionStartIncluding\": \"5.8\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T09:11:22.428Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2023-52775\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T09:11:22.428Z\", \"dateReserved\": \"2024-05-21T15:19:24.239Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-05-21T15:30:56.247Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



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.