In the Linux kernel, the following vulnerability has been resolved:
ipmi_si: fix a memleak in try_smi_init()
Kmemleak reported the following leak info in try_smi_init():
unreferenced object 0xffff00018ecf9400 (size 1024): comm "modprobe", pid 2707763, jiffies 4300851415 (age 773.308s) backtrace: [<000000004ca5b312>] __kmalloc+0x4b8/0x7b0 [<00000000953b1072>] try_smi_init+0x148/0x5dc [ipmi_si] [<000000006460d325>] 0xffff800081b10148 [<0000000039206ea5>] do_one_initcall+0x64/0x2a4 [<00000000601399ce>] do_init_module+0x50/0x300 [<000000003c12ba3c>] load_module+0x7a8/0x9e0 [<00000000c246fffe>] __se_sys_init_module+0x104/0x180 [<00000000eea99093>] __arm64_sys_init_module+0x24/0x30 [<0000000021b1ef87>] el0_svc_common.constprop.0+0x94/0x250 [<0000000070f4f8b7>] do_el0_svc+0x48/0xe0 [<000000005a05337f>] el0_svc+0x24/0x3c [<000000005eb248d6>] el0_sync_handler+0x160/0x164 [<0000000030a59039>] el0_sync+0x160/0x180
The problem was that when an error occurred before handlers registration and after allocating `new_smi->si_sm`, the variable wouldn't be freed in the error handling afterwards since `shutdown_smi()` hadn't been registered yet. Fix it by adding a `kfree()` in the error handling path in `try_smi_init()`.
CVSS Details
- CVSS 3.1 Base Score: 5.5
- CVSS 3.1 Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon Linux Ami 2 | — | Upgrade kernel-tools-develUpgrade kernelUpgrade kernel-debuginfo-common-aarch64Upgrade kernel-headersUpgrade kernel-develUpgrade perf-debuginfoUpgrade perfUpgrade bpftool-debuginfoUpgrade kernel-toolsUpgrade kernel-debuginfo-common-x86_64Upgrade kernel-livepatch-5.10.196-185.743Upgrade kernel-debuginfoUpgrade python-perfUpgrade kernel-tools-debuginfoUpgrade python-perf-debuginfoUpgrade bpftool | May 20, 2026 | May 20, 2026 |
| Debian | — | Upgrade linux | Oct 6, 2025 | Oct 6, 2025 |
| Huawei Euleros 2_0_sp13 | — | Upgrade bpftoolUpgrade kernel-tools-libsUpgrade kernel-abi-stablelistsUpgrade kernel-toolsUpgrade python3-perfUpgrade kernel | Dec 12, 2025 | Dec 11, 2025 |
| Redhat_linux | — | No solution existsUpgrade kernelUpgrade kernel-rt | Nov 14, 2025 | Oct 4, 2025 |
| Ubuntu | — | Upgrade linux-ibmUpgrade linux-gkeUpgrade linux-kvmUpgrade linux-nvidia-tegra-igxUpgrade linux-xilinx-zynqmpUpgrade linux-intel-iotgUpgrade linux-raspiUpgrade linux-gcp-5.15Upgrade linux-ibm-5.15Upgrade linux-azure-5.15Upgrade linux-realtimeUpgrade linux-nvidiaUpgrade linux-aws-5.4Upgrade linux-intel-iotg-5.15Upgrade linux-oracle-5.15Upgrade linux-nvidia-tegraUpgrade linux-hwe-5.4Upgrade linux-riscv-5.15Upgrade linux-fipsUpgrade linux-gkeopUpgrade linux-aws-fipsUpgrade linux-lowlatencyUpgrade linux-gcp-5.4Upgrade linux-azure-fipsUpgrade linux-oracleUpgrade linux-oracle-5.4Upgrade linux-ibm-5.4Upgrade linux-iotUpgrade linuxUpgrade linux-nvidia-tegra-5.15Upgrade linux-awsUpgrade linux-intel-iot-realtimeUpgrade linux-azure-5.4Upgrade linux-raspi-5.4Upgrade linux-lowlatency-hwe-5.15Upgrade linux-bluefieldUpgrade linux-azureUpgrade linux-hwe-5.15Upgrade linux-aws-5.15Upgrade linux-gcpUpgrade linux-gcp-fips | Oct 10, 2025 | Oct 4, 2025 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Oct 15, 2025 | Oct 4, 2025 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub