Linux · SUSE Linux Enterprise · Security advisory · July 8, 2025
SUSE-SU-2025:02254-1: Security update for 3 packages
SUSE-SU-2025:02254-1, released July 8, 2025, fixes 251 CVEs across 3 products. None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
251
None rated Critical
Exploited
0
None reported
Highest CVSS
8.0
Base score, 0 to 10
Highest EPSS
0.0079
56th percentile
Priority of the 251 CVEs
Patch now 0
Urgent 0
High 112
Routine 139
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| kernel-azure | sles 15.7 | 6.4.0-150700.20.6.1 |
| kernel-source-azure | sles 15.7 | 6.4.0-150700.20.6.1 |
| kernel-syms-azure | sles 15.7 | 6.4.0-150700.20.6.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2025-37928 | dm-bufio: don't schedule in atomic context | 7.8 | 0.0074 | None reported |
| High | CVE-2025-37917 | kernel-64kb: net: ethernet: mtk-star-emac: fix spinlock recursion issues on rx/tx poll (bsc#1243475). | 7.0 | 0.0056 | None reported |
| High | CVE-2025-38001 | net_sched: hfsc: Address reentrant enqueue adding class to eltree twice | 7.8 | 0.0056 | None reported |
| High | CVE-2024-50106 | kernel-64kb: Security update for the Linux Kernel | 7.0 | 0.0050 | None reported |
| High | CVE-2025-38018 | kernel-64kb: net/tls: fix kernel panic when alloc_page failed (bsc#1244999). | 7.0 | 0.0048 | None reported |
| High | CVE-2025-37954 | smb: client: Avoid race in open_cached_dir with lease breaks | 7.0 | 0.0037 | None reported |
| High | CVE-2024-57995 | kernel-rt-64k-devel: kernel: wifi: ath12k: fix read pointer after free in ath12k_mac_assign_vif_to_vdev() | 7.8 | 0.0036 | None reported |
| High | CVE-2025-37839 | jbd2: remove wrong sb->s_sequence check | 7.8 | 0.0033 | None reported |
| High | CVE-2024-58099 | kernel-64kb: Security update for the Linux Kernel | 7.0 | 0.0033 | None reported |
| High | CVE-2025-37840 | mtd: rawnand: brcmnand: fix PM resume warning | 7.8 | 0.0033 | None reported |
| High | CVE-2025-37861 | scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue | 7.8 | 0.0033 | None reported |
| High | CVE-2025-37858 | fs/jfs: Prevent integer overflow in AG size calculation | 7.8 | 0.0031 | None reported |
| High | CVE-2025-22035 | kernel-64kb: tracing: Fix use-after-free in print_graph_function_flags during tracer switching (bsc#1241544). | 7.8 | 0.0031 | None reported |
| High | CVE-2025-37752 | kernel-64kb: net_sched: sch_sfq: move the limit validation (bsc#1242504). | 7.8 | 0.0030 | None reported |
| High | CVE-2025-38003 | can: bcm: add missing rcu read protection for procfs content | 7.0 | 0.0030 | None reported |
| High | CVE-2025-39735 | kernel-64kb: Security update for the Linux Kernel | 7.1 | 0.0030 | None reported |
| High | CVE-2025-37927 | iommu/amd: Fix potential buffer overflow in parse_ivrs_acpihid | 7.8 | 0.0030 | None reported |
| High | CVE-2025-37869 | kernel-uek: ELSA-2025-20480: Unbreakable Enterprise kernel security update (IMPORTANT) | 7.8 | 0.0028 | None reported |
| High | CVE-2025-38004 | can: bcm: add locking for bcm_op runtime updates | 7.8 | 0.0028 | None reported |
| High | CVE-2025-37849 | KVM: arm64: Tear down vGIC on failed vCPU creation | 7.8 | 0.0027 | None reported |
| High | CVE-2025-37854 | drm/amdkfd: Fix mode1 reset crash issue | 7.8 | 0.0027 | None reported |
| High | CVE-2025-37943 | wifi: ath12k: Fix invalid data access in ath12k_dp_rx_h_undecap_nwifi | 8.0 | 0.0026 | None reported |
| High | CVE-2025-22113 | ext4: avoid journaling sb update on error if journal is destroying | 7.8 | 0.0026 | None reported |
| High | CVE-2025-37944 | wifi: ath12k: Fix invalid entry fetch in ath12k_dp_mon_srng_process | 7.8 | 0.0026 | None reported |
| High | CVE-2024-57982 | xfrm: state: fix out-of-bounds read during lookup | 7.1 | 0.0025 | None reported |
Showing 1 to 25 of 251
1Next
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.