CVE-2026-23322
published 2026-03-25CVE-2026-23322: 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…
PriorityP338high7.8CVSS 3.1
AVLACLPRLUINSUCHIHAH
EPSS
0.12%
2.5th percentile
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.
Affected
12 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.19.8-1 (forky) | linux 6.19.8-1 (forky) |
| linux | linux | — | — |
| linux | linux | >= 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 < c08ec55617cb9674a060a3392ea08391ab2a4f74 | c08ec55617cb9674a060a3392ea08391ab2a4f74 |
| linux | linux | >= 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 < 65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53 | 65ff5d1e4410df05edfbeb7bf2d62f7681ce1d53 |
| linux | linux | >= 9cf93a8fa9513c6d3cc65bdd50e05c1355cef322 < 594c11d0e1d445f580898a2b8c850f2e3f099368 | 594c11d0e1d445f580898a2b8c850f2e3f099368 |
| linux | linux_kernel | — | — |
| linux | linux_kernel | — | — |
| linux | linux_kernel | >= 0 < 6.19.8-1 | 6.19.8-1 |
| linux | linux_kernel | >= 6.18.0 < 6.18.17 | 6.18.17 |
| linux | linux_kernel | >= 6.18.1 < 6.18.17 | 6.18.17 |
| linux | linux_kernel | >= 6.19 < 6.19.7 | 6.19.7 |
| linux | linux_kernel | >= 6.19.0 < 6.19.7 | 6.19.7 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
Linux Kernel up to 6.18.16/6.19.6/7.0-rc1 ipmi smi_work null pointer dereference (Nessus ID 304068 / WID-SEC-2026-0861)
vuldb·2026-06-17·CVSS 7.8
CVE-2026-23322 [HIGH] Linux Kernel up to 6.18.16/6.19.6/7.0-rc1 ipmi smi_work null pointer dereference (Nessus ID 304068 / WID-SEC-2026-0861)
A vulnerability categorized as critical has been discovered in Linux Kernel up to 6.18.16/6.19.6/7.0-rc1. The impacted element is the function smi_work of the component ipmi. Executing a manipulation can lead to null pointer dereference.
The identification of this vulnerability is CVE-2026-23322. The attack needs to be done within the local network. There is no exploit available.
It is advisable to upgrade the affected component.
GHSA
GHSA-668m-q5h4-jfjc: In the Linux kernel, the following vulnerability has been resolved:
ipmi: Fix use-after-free and list corruption on sender error
The analysis from B
ghsa_unreviewed·2026-03-25
CVE-2026-23322 GHSA-668m-q5h4-jfjc: In the Linux kernel, the following vulnerability has been resolved:
ipmi: Fix use-after-free and list corruption on sender error
The analysis from B
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
OSV
ipmi: Fix use-after-free and list corruption on sender error
osv·2026-03-25
CVE-2026-23322 ipmi: Fix use-after-free and list corruption on sender error
ipmi: Fix use-after-free and list corruption on sender error
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-a
OSV
CVE-2026-23322: In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix use-after-free and list corruption on sender error The analysis from Bre
osv·2026-03-25
CVE-2026-23322 CVE-2026-23322: In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix use-after-free and list corruption on sender error The analysis from Bre
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 NUL
Red Hat
kernel: ipmi: Fix use-after-free and list corruption on sender error
vendor_redhat·2026-03-25
CVE-2026-23322 kernel: ipmi: Fix use-after-free and list corruption on sender error
kernel: ipmi: Fix use-after-free and list corruption on sender error
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 us
Debian
CVE-2026-23322: linux - In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix u...
vendor_debian·2026
CVE-2026-23322 [LOW] CVE-2026-23322: linux - In the Linux kernel, the following vulnerability has been resolved: ipmi: Fix u...
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 NUL
No detection rules found.
No public exploits indexed.
2026-03-25
Published