In the Linux kernel, the following vulnerability has been resolved:
vduse: check that offset is within bounds in get_config()
This condition checks "len" but it does not check "offset" and that could result in an out of bounds read if "offset > dev->config_size". The problem is that since both variables are unsigned the "dev->config_size - offset" subtraction would result in a very high unsigned value.
I think these checks might not be necessary because "len" and "offset" are supposed to already have been validated using the vhost_vdpa_config_validate() function. But I do not know the code perfectly, and I like to be safe.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade linux | Jul 30, 2024 | Jun 19, 2024 |
| Suse | — | Upgrade kernel-azure-optionalUpgrade kernel-azure-vdsoUpgrade cluster-md-kmp-azureUpgrade kernel-rt-livepatch-develUpgrade kernel-rt-optionalUpgrade kernel-azureUpgrade kernel-rt_debugUpgrade kernel-rt_debug-develUpgrade kernel-rt-vdsoUpgrade kernel-syms-rtUpgrade kselftests-kmp-azureUpgrade kernel-azure-livepatch-develUpgrade kernel-source-azureUpgrade kernel-rt_debug-vdsoUpgrade gfs2-kmp-azureUpgrade kernel-azure-develUpgrade kernel-source-rtUpgrade gfs2-kmp-rtUpgrade kernel-azure-extraUpgrade kselftests-kmp-rtUpgrade kernel-rt-extraUpgrade reiserfs-kmp-rtUpgrade kernel-rtUpgrade ocfs2-kmp-rtUpgrade dlm-kmp-azureUpgrade reiserfs-kmp-azureUpgrade cluster-md-kmp-rtUpgrade dlm-kmp-rtUpgrade kernel-devel-rtUpgrade kernel-syms-azureUpgrade kernel-rt_debug-livepatch-develUpgrade kernel-rt-livepatchUpgrade kernel-rt-develUpgrade kernel-devel-azureUpgrade ocfs2-kmp-azure | Aug 9, 2024 | Jun 19, 2024 |
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