{"api_version":"1","generated_at":"2026-05-01T21:58:58+00:00","cve":"CVE-2026-23322","urls":{"html":"https://cve.report/CVE-2026-23322","api":"https://cve.report/api/cve/CVE-2026-23322.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-23322","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-23322"},"summary":{"title":"ipmi: Fix use-after-free and list corruption on sender error","description":"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->curr_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->done.\n\nThe buggy sequence:\n\n  sender() fails\n    -> deliver_err_response(recv_msg)  // recv_msg queued for delivery\n    -> goto restart                    // curr_msg not cleared!\n  sender() fails again (same message!)\n    -> deliver_err_response(recv_msg)  // tries to queue same recv_msg\n    -> 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.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-03-25 11:16:29","updated_at":"2026-04-23 21:05:22"},"problem_types":["CWE-416"],"metrics":[{"version":"3.1","source":"nvd@nist.gov","type":"Primary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"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"}}],"references":[{"url":"https://git.kernel.org/stable/c/594c11d0e1d445f580898a2b8c850f2e3f099368","name":"https://git.kernel.org/stable/c/594c11d0e1d445f580898a2b8c850f2e3f099368","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53","name":"https://git.kernel.org/stable/c/65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c08ec55617cb9674a060a3392ea08391ab2a4f74","name":"https://git.kernel.org/stable/c/c08ec55617cb9674a060a3392ea08391ab2a4f74","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":["Patch"],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23322","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23322","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 c08ec55617cb9674a060a3392ea08391ab2a4f74 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 594c11d0e1d445f580898a2b8c850f2e3f099368 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.17 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.19.7 6.19.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2026","cve_id":"23322","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"o","cpe4":"linux","cpe5":"linux_kernel","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"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->curr_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->done.\n\nThe buggy sequence:\n\n  sender() fails\n    -> deliver_err_response(recv_msg)  // recv_msg queued for delivery\n    -> goto restart                    // curr_msg not cleared!\n  sender() fails again (same message!)\n    -> deliver_err_response(recv_msg)  // tries to queue same recv_msg\n    -> 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"},"nvd":{"publishedDate":"2026-03-25 11:16:29","lastModifiedDate":"2026-04-23 21:05:22","problem_types":["CWE-416"],"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}]},"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"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"23322","Ordinal":"1","Title":"ipmi: Fix use-after-free and list corruption on sender error","CVE":"CVE-2026-23322","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"23322","Ordinal":"1","NoteData":"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->curr_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->done.\n\nThe buggy sequence:\n\n  sender() fails\n    -> deliver_err_response(recv_msg)  // recv_msg queued for delivery\n    -> goto restart                    // curr_msg not cleared!\n  sender() fails again (same message!)\n    -> deliver_err_response(recv_msg)  // tries to queue same recv_msg\n    -> 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.","Type":"Description","Title":"ipmi: Fix use-after-free and list corruption on sender error"}]}}}