Linux · 
Ubuntu · Package update · February 18, 2025
Ubuntu · Package update · February 18, 2025u-boot-qcom 2022.01+dfsg-2ubuntu2.7: u-boot-qcom 2022.01+dfsg-2ubuntu2.7 for Ubuntu 22.04.1 LTS (jammy)
u-boot-qcom 2022.01+dfsg-2ubuntu2.7, released February 18, 2025, fixes 6 CVEs in u-boot-qcom. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
6
None rated Critical
Exploited
0
None reported
Highest CVSS
7.8
Base score, 0 to 10
Highest EPSS
0.0037
31st percentile
Priority of the 6 CVEs
Patch now 0
Urgent 0
High 1
Routine 5
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| u-boot-qcom | Ubuntu 22.04.1 LTS (jammy) | 2022.01+dfsg-2ubuntu2.7 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2024-57258 | u-boot: multiple integer overflows in U-Boot's memory allocator (bsc#1237287). | 7.8 | 0.0025 | None reported |
| Routine | CVE-2024-57256 | u-boot: integer overflow in U-Boot's ext4 symlink resolution function (bsc#1237284). | 6.8 | 0.0037 | None reported |
| Routine | CVE-2024-57254 | u-boot-tegra: An integer overflow in sqfs_inode_size in Das U-Boot before 2025.01-rc1 occurs in the symlink size calculation via a... | 6.8 | 0.0037 | None reported |
| Routine | CVE-2024-57255 | u-boot: An integer overflow in sqfs_resolve_symlink in Das U-Boot before 2025.01-rc1 occurs via a crafted squashfs filesystem... | 6.8 | 0.0037 | None reported |
| Routine | CVE-2024-57259 | u-boot: sqfs_search_dir in Das U-Boot before 2025.01-rc1 exhibits an off-by-one error and resultant heap memory corruption fo... | 6.8 | 0.0037 | None reported |
| Routine | CVE-2024-57257 | u-boot-sifive: A stack consumption issue in sqfs_size in Das U-Boot before 2025.01-rc1 occurs via a crafted squashfs filesystem with... | 2.4 | 0.0032 | None reported |
Showing 1 to 6 of 6
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.