In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()
There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of current smb2_ea_info. ksmbd need to validate buffer length Before accessing the next ea. ksmbd should check buffer length using buf_len, not next variable. next is the start offset of current ea that got from previous ea.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Aug 18, 2025 | Aug 18, 2025 |
| Ubuntu | — | Upgrade linux-intel-iotgUpgrade linux-aws-5.15Upgrade linux-intel-iot-realtimeUpgrade linux-gkeopUpgrade linux-oracle-5.15Upgrade linux-azure-5.15Upgrade linux-nvidiaUpgrade linux-nvidia-tegraUpgrade linux-oracleUpgrade linux-riscv-5.15Upgrade linux-gcp-5.15Upgrade linux-raspiUpgrade linux-gkeUpgrade linux-realtimeUpgrade linux-kvmUpgrade linux-xilinx-zynqmpUpgrade linux-lowlatencyUpgrade linux-gcpUpgrade linux-ibm-5.15Upgrade linux-ibmUpgrade linux-intel-iotg-5.15Upgrade linux-hwe-5.15Upgrade linuxUpgrade linux-nvidia-tegra-5.15Upgrade linux-bluefieldUpgrade linux-awsUpgrade linux-nvidia-tegra-igxUpgrade linux-azureUpgrade linux-lowlatency-hwe-5.15Upgrade linux-azure-fde | Aug 19, 2025 | Aug 18, 2025 |
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