CVE-2026-23322 (GCVE-0-2026-23322)

Vulnerability from cvelistv5 – Published: 2026-03-25 10:27 – Updated: 2026-04-13 06:04
VLAI?
Title
ipmi: Fix use-after-free and list corruption on sender error
Summary
In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix use-after-free and list corruption on sender error The analysis from Breno: When the SMI sender returns an error, smi_work() delivers an error response but then jumps back to restart without cleaning up properly: 1. intf->curr_msg is not cleared, so no new message is pulled 2. newmsg still points to the message, causing sender() to be called again with the same message 3. If sender() fails again, deliver_err_response() is called with the same recv_msg that was already queued for delivery This causes list_add corruption ("list_add double add") because the recv_msg is added to the user_msgs list twice. Subsequently, the corrupted list leads to use-after-free when the memory is freed and reused, and eventually a NULL pointer dereference when accessing recv_msg->done. The buggy sequence: sender() fails -> deliver_err_response(recv_msg) // recv_msg queued for delivery -> goto restart // curr_msg not cleared! sender() fails again (same message!) -> deliver_err_response(recv_msg) // tries to queue same recv_msg -> LIST CORRUPTION Fix this by freeing the message and setting it to NULL on a send error. Also, always free the newmsg on a send error, otherwise it will leak.
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 , < c08ec55617cb9674a060a3392ea08391ab2a4f74 (git)
Affected: 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 , < 65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53 (git)
Affected: 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 , < 594c11d0e1d445f580898a2b8c850f2e3f099368 (git)
Create a notification for this product.
    Linux Linux Affected: 6.18
Unaffected: 0 , < 6.18 (semver)
Unaffected: 6.18.17 , ≤ 6.18.* (semver)
Unaffected: 6.19.7 , ≤ 6.19.* (semver)
Unaffected: 7.0 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/char/ipmi/ipmi_msghandler.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "c08ec55617cb9674a060a3392ea08391ab2a4f74",
              "status": "affected",
              "version": "9cf93a8fa9513c6d3cc65bdd50e05c1355cef322",
              "versionType": "git"
            },
            {
              "lessThan": "65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53",
              "status": "affected",
              "version": "9cf93a8fa9513c6d3cc65bdd50e05c1355cef322",
              "versionType": "git"
            },
            {
              "lessThan": "594c11d0e1d445f580898a2b8c850f2e3f099368",
              "status": "affected",
              "version": "9cf93a8fa9513c6d3cc65bdd50e05c1355cef322",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/char/ipmi/ipmi_msghandler.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.18"
            },
            {
              "lessThan": "6.18",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.17",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.19.*",
              "status": "unaffected",
              "version": "6.19.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.0",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.17",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.19.7",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0",
                  "versionStartIncluding": "6.18",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nipmi: Fix use-after-free and list corruption on sender error\n\nThe analysis from Breno:\n\nWhen the SMI sender returns an error, smi_work() delivers an error\nresponse but then jumps back to restart without cleaning up properly:\n\n1. intf-\u003ecurr_msg is not cleared, so no new message is pulled\n2. newmsg still points to the message, causing sender() to be called\n   again with the same message\n3. If sender() fails again, deliver_err_response() is called with\n   the same recv_msg that was already queued for delivery\n\nThis causes list_add corruption (\"list_add double add\") because the\nrecv_msg is added to the user_msgs list twice. Subsequently, the\ncorrupted list leads to use-after-free when the memory is freed and\nreused, and eventually a NULL pointer dereference when accessing\nrecv_msg-\u003edone.\n\nThe buggy sequence:\n\n  sender() fails\n    -\u003e deliver_err_response(recv_msg)  // recv_msg queued for delivery\n    -\u003e goto restart                    // curr_msg not cleared!\n  sender() fails again (same message!)\n    -\u003e deliver_err_response(recv_msg)  // tries to queue same recv_msg\n    -\u003e LIST CORRUPTION\n\nFix this by freeing the message and setting it to NULL on a send error.\nAlso, always free the newmsg on a send error, otherwise it will leak."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-04-13T06:04:37.508Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/c08ec55617cb9674a060a3392ea08391ab2a4f74"
        },
        {
          "url": "https://git.kernel.org/stable/c/65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53"
        },
        {
          "url": "https://git.kernel.org/stable/c/594c11d0e1d445f580898a2b8c850f2e3f099368"
        }
      ],
      "title": "ipmi: Fix use-after-free and list corruption on sender error",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-23322",
    "datePublished": "2026-03-25T10:27:15.954Z",
    "dateReserved": "2026-01-13T15:37:45.996Z",
    "dateUpdated": "2026-04-13T06:04:37.508Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-23322",
      "date": "2026-04-24",
      "epss": "0.00013",
      "percentile": "0.02195"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2026-23322\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2026-03-25T11:16:29.107\",\"lastModified\":\"2026-04-23T21:05:22.450\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nipmi: Fix use-after-free and list corruption on sender error\\n\\nThe analysis from Breno:\\n\\nWhen the SMI sender returns an error, smi_work() delivers an error\\nresponse but then jumps back to restart without cleaning up properly:\\n\\n1. intf-\u003ecurr_msg is not cleared, so no new message is pulled\\n2. newmsg still points to the message, causing sender() to be called\\n   again with the same message\\n3. If sender() fails again, deliver_err_response() is called with\\n   the same recv_msg that was already queued for delivery\\n\\nThis causes list_add corruption (\\\"list_add double add\\\") because the\\nrecv_msg is added to the user_msgs list twice. Subsequently, the\\ncorrupted list leads to use-after-free when the memory is freed and\\nreused, and eventually a NULL pointer dereference when accessing\\nrecv_msg-\u003edone.\\n\\nThe buggy sequence:\\n\\n  sender() fails\\n    -\u003e deliver_err_response(recv_msg)  // recv_msg queued for delivery\\n    -\u003e goto restart                    // curr_msg not cleared!\\n  sender() fails again (same message!)\\n    -\u003e deliver_err_response(recv_msg)  // tries to queue same recv_msg\\n    -\u003e LIST CORRUPTION\\n\\nFix this by freeing the message and setting it to NULL on a send error.\\nAlso, always free the newmsg on a send error, otherwise it will leak.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\\n\\nipmi: Soluciona el uso despu\u00e9s de liberaci\u00f3n y la corrupci\u00f3n de lista en error del remitente\\n\\nEl an\u00e1lisis de Breno:\\n\\nCuando el remitente SMI devuelve un error, smi_work() entrega una respuesta de error pero luego salta de nuevo para reiniciar sin limpiar correctamente:\\n\\n1. intf-\u0026gt;curr_msg no se borra, por lo que no se extrae ning\u00fan mensaje nuevo\\n2. newmsg todav\u00eda apunta al mensaje, haciendo que sender() sea llamado de nuevo con el mismo mensaje\\n3. Si sender() falla de nuevo, deliver_err_response() es llamado con el mismo recv_msg que ya estaba en cola para entrega\\n\\nEsto causa corrupci\u00f3n de list_add (\u0027list_add doble adici\u00f3n\u0027) porque el recv_msg es a\u00f1adido a la lista user_msgs dos veces. Posteriormente, la lista corrupta lleva a un uso despu\u00e9s de liberaci\u00f3n cuando la memoria es liberada y reutilizada, y eventualmente a una desreferencia de puntero NULL al acceder a recv_msg-\u0026gt;done.\\n\\nLa secuencia defectuosa:\\n\\n  sender() falla\\n    -\u0026gt; deliver_err_response(recv_msg) // recv_msg en cola para entrega\\n    -\u0026gt; goto restart // \u00a1curr_msg no borrado!\\n  sender() falla de nuevo (\u00a1mismo mensaje!)\\n    -\u0026gt; deliver_err_response(recv_msg) // intenta poner en cola el mismo recv_msg\\n    -\u0026gt; CORRUPCI\u00d3N DE LISTA\\n\\nSoluciona esto liberando el mensaje y estableci\u00e9ndolo a NULL en un error de env\u00edo. Adem\u00e1s, siempre libera el newmsg en un error de env\u00edo, de lo contrario, se producir\u00e1 una fuga.\"}],\"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:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-416\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.18.1\",\"versionEndExcluding\":\"6.18.17\",\"matchCriteriaId\":\"07E9D8CD-82F0-4CC6-8038-BF71758D583C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.19\",\"versionEndExcluding\":\"6.19.7\",\"matchCriteriaId\":\"69245D10-0B71-485E-80C3-A64F077004D3\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*\",\"matchCriteriaId\":\"DCE57113-2223-4308-A0F2-5E6ECFBB3C23\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"F253B622-8837-4245-BCE5-A7BF8FC76A16\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"4AE85AD8-4641-4E7C-A2F4-305E2CD9EE64\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"F666C8D8-6538-46D4-B318-87610DE64C34\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"02259FDA-961B-47BC-AE7F-93D7EC6E90C2\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"58A9FEFF-C040-420D-8F0A-BFDAAA1DF258\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"1D2315C0-D46F-4F85-9754-F9E5E11374A6\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*\",\"matchCriteriaId\":\"512EE3A8-A590-4501-9A94-5D4B268D6138\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/594c11d0e1d445f580898a2b8c850f2e3f099368\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/c08ec55617cb9674a060a3392ea08391ab2a4f74\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


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 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.